No - fix your own received from lines bud
> ordinarily takes an IP address and returns IS_BROADCAST, IS_MYADDR or
> 0. But when an interface (any interface) is configured to IP address
> 0.0.0.0 (as it is during DHCP resolution), this function returns
> IS_MYADDR instead of 0 for any arbitrary non-broadcast address. This
Its a known flaw.
> any destination address in an incoming packet as being directed to us
> whenever the IP address configured for the receiving interface is
> 0.0.0.0:
We may then start doing stuff like ICMP on this
> This is arguably the right thing to do. This code treats an interface
> IP address of 0.0.0.0 as "promiscuous" for the purposes of DHCP without
> affecting the operation of any other interface on the machine.
The right thing to do is done in 2.1.x - use lower level stuff for DHCP
keep it out of the kernel fast paths and allow interfaces that are physically
up but not running IP
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu