On Thu, 23 Jan 2003 18:19:10 +0100 Guido van Rooij <[EMAIL PROTECTED]> wrote:
> On Thu, Jan 23, 2003 at 08:55:28AM +0100, Remco Post wrote: > > > > 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.... > > Indeed, I've had this discussion before. > > NAT is not a security instrument. NAT rewrites, or it doesn't. It will > not block packets. That should be done by the filtering rules. > True. But _if_ the nat would happen before filtering, so: interface-->filter(in)-->nat(rdr)-->routing-->nat(map)-->filter(out)-->interface as is more customairy with firewalls IIRC, it would be possible to build stricter filters than is the case currently with ipfilter. It may have other implications, but it would make things more logical, IMHO. > The best way to protect oneself is to always use keep state for > outgoing connections and just block all incoming packets. > > -Guido Which is entiry possible if one uses map type nat's only... -- Remco
