Re: FW: Filtering multiple networks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday 31 May 2004 19:23, Frank Gruellich wrote:
> * David Cannings <lists@xxxxxxxxx> 31. May 04:
> > On Monday 31 May 2004 10:45, Frank Gruellich wrote:
> > Can you please explain how a TCP RST or ICMP message is supposed to
> > get back to a spoofed RFC 1918 (or otherwise reserved) address?
> What makes you think the address is spoofed?  I assumed somebody just
> configured its external interface wrong.  Some antique idea, that not
> all people are bad guys.

Nowadays many core routers will drop packets that appear to come from 
addresses that either haven't been allocated or shouldn't be seen on the 
wider Internet, therefore if packets have got as far as you something is 
awry.  RFC 1918 and RFC 3330 are both good references, then 
http://www.iana.org/ipaddress/ip-addresses.htm.

> > Sending replies of any sort out of a WAN interface onto the Internet
> > to a reserved or private address is very bad practice.
> Yes, okay, you are right.  Sorry, a reflex, when I see -j DROP.

Personally I don't know what to think on the REJECT vs DROP debate, so I 
sit on the fence.  Like everything else, each has advantages and 
disadvantages.

> > Some would even argue that sending to unallocated space is bad.
> What do you mean with unallocated space?

IP blocks that have not been allocated by IANA or one of the regional 
authorities (RIRs).  This conversation is likely to go way off topic for 
this list so instead I'll provide the following URL: 
http://www.cymru.com/Bogons/

David


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux