Marco Radzinschi wrote:
On Thu, 23 Jan 2003, Guido van Rooij wrote:
On Thu, Jan 23, 2003 at 09:09:23AM -0800, Clayton Fiske wrote:

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
If you have e.g. a cable modem, there is a LAN on the outside....
(provided no PPPoE is used).

-Guido
Precisely why you need to block those private IP ranges. You don't want
anything form the cable modem network to come in.  In my case, I
block in everything coming in from non routable addresses, and everything
leaving to non routable addresses.
It should be eminently clear from this discussion that there is no such thing as a "non routable address". I suggest using the term "RFC1918 address" to avoid perpetuating the popular misconception that some addresses magically cannot reach your machine.

Cable modem uses DHCP, but the initial address fetch uses ethernet
broadcasts, so IPF never touches the packets.  Once I have an address, I
have the DHCP client run a script that adds a stateful filter rule that
allows UDP packets from my address port 68 to the DHCP server address port
67.
The whole system is still a broadcast medium. You're perfectly free to route any traffic you like to your peers, which are all the other customers in your broadcast domain. This may be thousands of other systems.

I also allow the ICMP echos from the DHCP server, so that it does not give
out my IP address to someone else.
That's specific to your particular system. Some systems don't use any ICMP; they just perform straight DHCP -- if the lease expires and the client doesn't renew it, someone else gets it.

Back on topic - I think Guido was trying to say that packets from internal
non routable addresses will never reach the external interface.
Guido is saying that a peer on your cable modem network can transmit a packet to you with any source and destination address he likes, including RFC1918, directed broadcast, network broadcast, 1.2.3.4, etc. It's up to you, and nobody else, to block it at your perimeter if it has an address you don't like.

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

Reply via email to