From: sverre <sverre@gmx.net>
To: netfilter-devel@lists.samba.org
Subject: Re: bug in 2.4.18 netfilter ?
Date: Fri, 5 Jul 2002 13:58:01 +0200 [thread overview]
Message-ID: <20020705115800.GA192@gmx.net> (raw)
In-Reply-To: <20020705000210.GA2038@gmx.net>
gonna try to reply to myself before anyone else does ;)
the "bug" was indeed in the firewall script (surprise!) - the nat table
was not flushed between the two ppp connestions. During the second
connection all the outgoing packets had the source IP address I was
assigned in the previous ppp connection, so no wonder I didnt get any
response.
Sorry for questioning the netfilter bugfreeness and wasting your
bandwidth with needless mails ;)
best regards,
--
sverre <sverreQgmx.net>
prev parent reply other threads:[~2002-07-05 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-05 0:02 bug in 2.4.18 netfilter ? sverre
2002-07-05 11:58 ` sverre [this message]
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=20020705115800.GA192@gmx.net \
--to=sverre@gmx.net \
--cc=netfilter-devel@lists.samba.org \
/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.