Its because the code responds to things, imagine an arp for 0.0.0.0 getting
a reply, or a multicast to 224.0.0.1 getting icmp replies from 0.0.0.0 - thats
the sort of stuff to worry about.
> > implemented in Linux. But it seems a rather drastic change when a much
> > simpler and cleaner short-term fix is available at least for the 2.0.x
> > kernels.
> Thats what has been deamed to be the correct way to handle things..
It is a drastic change, and 2.0.x has no nice kernel side filtering like
2.1.x for doing it that way. Its a case of "not adding the change for 2.0.x
in general because most people dont need it and 2.0.x stability is vital"
not because its a) wrong code or b) an invalid point. If we were on 1.3.8x
I'd have agreed about fixing 2.0.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu