From: Patrick McHardy <kaber@trash.net>
To: oan@frozentux.net
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: --dport in uml crash
Date: Tue, 24 Oct 2006 01:17:00 +0200 [thread overview]
Message-ID: <453D4D6C.5050508@trash.net> (raw)
In-Reply-To: <1161644625.8705.16.camel@LAPTOP4.MSHOME>
Oskar Andreasson wrote:
> Using UML kernel 2.6.18 and iptables-1.3.6.
> Specifying iptables -A INPUT -p tcp --dport 23 -j ACCEPT generates a
> hard crash of the UML system.
> -j ACCEPT on it's own works flawless and -p tcp also works flawless, so
> i assume it's the --dport causing the crash for some reason.
It is reproducable?
> I've been unable to get a look at the error messages since the xterm
> closes down before I get a chance to read it (lots of something scrolls
> by before closing however), any suggestions on how to get the errors are
> welcome, or if anyone else can replicate them would also be welcome :).
>
> Let me know if there is any more information that might be needed, or if
> this is an UML related bug?
Based on my experience I would guess that its UML, but it works pretty
reliable in the past few month for me. I'm unable to reproduce the
problem, can you send me your config please?
You could also get the "umlgdb" script and run uml in debug mode,
gdb should be able to tell you more.
next prev parent reply other threads:[~2006-10-23 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 23:03 --dport in uml crash Oskar Andreasson
2006-10-23 23:09 ` Oskar Andreasson
2006-10-23 23:17 ` Patrick McHardy [this message]
2006-10-24 8:57 ` CLUSTERIP and UML crash, was [Re: --dport in uml crash] Oskar Andreasson
2006-10-24 14:24 ` Patrick McHardy
2006-10-24 15:33 ` Oskar Andreasson
2006-10-24 15:48 ` Patrick McHardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=453D4D6C.5050508@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=oan@frozentux.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.