Sounds good to me :)
At the very least, this would improve the performance of the
mDNSResponder. mDNSResponder has some additional code to get the
interface the packet was received on so it can filter out the packet if
it wasn't received on the interface that socket is bound to/associated
with
This is "by design". When you perform IP_ADD_MEMBERSHIP, it assures you
that the interface you've selected will receive packets destined for
the multicast address you specify. It will deal with any IGMP traffic
necessary for joining the group.
When a packet is received on any interface, the pac
On Friday, December 6, 2002, at 04:15 PM, Jason Hunt wrote:
Other platforms out there will handle broadcast on the loopback
interface. Is it desirable to make changes to the FreeBSD stack to get
this behavior?
Any examples? I cannot think of a practical case where this would be
required. I w
Thank you for the reply Dan!
I am aware of the issues with broadcast, and I strongly urge people to
use multicast instead of broadcast for a variety of reasons. All the
same, I've been asked to address this issue and I wanted to understand
why FreeBSD doesn't allow broadcast on the loopback in
Is there a reason that the broadcast flag is not set on the loopback
interface? It seems like it might be useful to allow applications that
use broadcast to continue to work even when loopback is the only
interface.
-josh
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freeb
