Peter Memishian wrote: > > > To address this problem, an IP_BROADCAST_TTL socket option is proposed. > > > This option will be identical to the existing stable IP_MULTICAST_TTL > > > socket option, but will apply to broadcast traffic. > > > > is there some reason we can't simply extend IP_MULTICAST_TTL to also > > cover broadcast traffic? > >As per the manpage, it only applies to multicast datagrams on the socket. >Having it also apply to broadcast traffic would break that promise. >
FWIW, I agree with your comments here... But I can't help but wonder, with seeing this case and the code changes required in ip_input, if the change to DHCP's architecture that requires this was actually a good one. Darren
