From: Ben <bench@silentmedia.com>
To: lartc@vger.kernel.org
Subject: [LARTC] what's changed?
Date: Sat, 10 Nov 2001 21:42:10 +0000 [thread overview]
Message-ID: <marc-lartc-100543755008226@msgid-missing> (raw)
I recently upgraded our firewall from an older 2.4.2 kernel to the most
recent 2.4.14, and the iptables binaries from 1.2.1a to 1.2.4. Or rather,
I *tried* to upgrade; something have very muched changed and my old
firewall rules don't seem to work anymore.
One symptom I've noticed seems to be that packets which match an ACCEPT
rule in the OUTPUT chain are still being tested against the POSTROUTING
chain in the nat table. I thought that once something was accepted, it was
good to go? That's certainly how it works with my older 2.4.2 kernel
setup.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
reply other threads:[~2001-11-10 21:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-lartc-100543755008226@msgid-missing \
--to=bench@silentmedia.com \
--cc=lartc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox