Clayton Fiske wrote:
No, you just block incoming traffic by default and use state to allow valid return traffic.On Thu, Jan 23, 2003 at 08:55:28AM +0100, Remco Post wrote:On Wed, 22 Jan 2003 16:31:48 -0800 Clayton Fiske <[EMAIL PROTECTED]> wrote:Unauthorized inbound traffic would have a -source- of 10.x.x.x coming in, whereas valid traffic would have a -destination- of 10.x.x.x.after NAT this is correct, before NAT, one would maybe like to block all traffic with a destination of 10.0.0.0/8, sice that cannot excist on that network. This sort of sounds like a shortcoming of ipfilter....Think about it from a routing perspective. How would a packet with a destination address of 10.x.x.x (pre-NAT) reach your firewall? Does some external host or router have a default route pointing at its outside interface? Logically, there is no reason packets with an invalid pre-NAT destination address should ever reach you in the first place. 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.
You *cannot* assume that you will not receive traffic for RFC1918 addresses. They may get routed to you a number of ways, depending on your network configuration. If you make assumptions about how you're upstream behaves, you aren't defining your perimeter -- you're trusting someone else to do it for you.
--
Jefferson Ogata <[EMAIL PROTECTED]>
NOAA Computer Incident Response Team (N-CIRT) <[EMAIL PROTECTED]>
