From: Grant Adamson <gadamson@shaw.ca>
To: netfilter@lists.netfilter.org
Subject: All interface specifications being replaced by ANYWHERE
Date: Fri, 09 Dec 2005 15:17:11 -0800 [thread overview]
Message-ID: <001c01c5fd16$af0deb40$0201a8c0@shodan> (raw)
Hi All,
I recently redid my home gateway/NAT box with debian 3.1, and everything
looked to be working fine until I did a quick scan on it from outside to
test the firewall. All the services running appeared to be exposed. Checking
my rules with iptables -L, I found that for some reason, everywhere I had
specified a physical interface, it had been replaced by ANYWHERE.
For example, the following rule:
iptables -A INPUT -m state --state NEW -i ! $EXTIF -j ACCEPT
Ends up appearing in the iptables -L list as:
target prot opt source destination
ACCEPT all -- anywhere anywhere state NEW
Needless to say, this doesn't make for a very good situation. Has anyone
ever seen a problem like this before? Any suggestions would be greatly
appreciated.
Thanks,
Grant
next reply other threads:[~2005-12-09 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 23:17 Grant Adamson [this message]
2005-12-12 13:50 ` All interface specifications being replaced by ANYWHERE myhapwcforever
2005-12-12 14:31 ` Leonardo Rodrigues Magalhães
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='001c01c5fd16$af0deb40$0201a8c0@shodan' \
--to=gadamson@shaw.ca \
--cc=netfilter@lists.netfilter.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