From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: netfilter@lists.netfilter.org
Subject: Re: ICMP rule for stateful firewall
Date: Mon, 09 May 2005 09:47:46 -0500 [thread overview]
Message-ID: <427F7812.3010500@riverviewtech.net> (raw)
In-Reply-To: <9927912d05050903154ad4c3f6@mail.gmail.com>
> I wanted to ask if such a rule was possible:
>
> iptables -A FORWARD -i eth0 -o eth0 -s 192.168.10.0/24 -d
> 192.168.10.0/24 -m state --state NEW,ESTABLISHED,RELATED -p icmp
> --icmp-type echo request -j ACCEPT
Yes, such a rule seems valid as in there are no syntax errors. However I think this type of rule is a bit odd to see. The fact that you are coming in and doing out the same interface does not bother me, but the fact that your source and destination are on the same subnet perplexes me. Normally this sort of operation would be reserved for a single physical LAN subnet. I have seen such traffic before, namely when I used a DNAT to redirect web traffic from a LAN back in to a proxy on the same LAN. (This was used to thwart people that tried to bypass the proxy on the LAN.) I find it a little odd that you would need ICMP traffic from the local LAN destined to the local LAN to pass through your router, but hey, I'm not saying that it would never happen. Based on your rule ICMP traffic from someone on your local LAN on eth0 with a source IP in the 192.168.10.0/24 subnet destined to your
local LAN on eth0 with a destination IP in the 192.168.10.0 subnet *SHOULD* work just fin
d.
Grant. . . .
next prev parent reply other threads:[~2005-05-09 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 10:15 ICMP rule for stateful firewall Visham Ramsurrun
2005-05-09 14:47 ` Taylor, Grant [this message]
2005-05-09 15:16 ` Jason Opperisano
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=427F7812.3010500@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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 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.