Clayton Fiske wrote:
On Thu, Jan 23, 2003 at 12:30:37PM -0500, Jefferson Ogata wrote:

Clayton Fiske wrote:

If you are really worried about this, set up a rdr rule that takes
inbound traffic addressed to 10.x.x.x and rdr's it to some bogus
address for which you have filter rules.
No, you just block incoming traffic by default and use state to allow valid return traffic.

So when I want to rdr mail traffic to a 10.x.x.x IP, how would this
help? I can't differentiate natively-addressed traffic from rdr'd
traffic in my filter rules.

Obviously any traffic you don't want should be blocked by filter rules.
That takes care of the cablemodem/outside LAN issue mentioned as well.
I agree with you that there's inherent ambiguity in doing the rdr NAT before state. In fact, I objected to it on the list when Darren first announced the change (it used to be the other way).

But I guess I don't understand in what scenario this is actually a problem for you. If you're rdr-ing to a 10 address, and you're allowing inbound to that address, does it actually matter whether the rdr is invoked?

Possibly a nice enhancement to IP Filter would be to allow rules to be tagged as only applying where NAT has also occurred. Then your inbound 10 rule could be limited to cases where that destination address is the result of a rdr. In general, I think making filtering and NAT more integrated would benefit in a number of areas.

--
Jefferson Ogata <[EMAIL PROTECTED]>
NOAA Computer Incident Response Team (N-CIRT) <[EMAIL PROTECTED]>

Reply via email to