> Yep, thanks. I've made the changes, and another change that followed > from our discussion on broadcast handling. Basically, what we agreed > upon was: because broadcast are locally looped back, we should be able > to see them on output. My code previously restricted the observability > to input only unless DL_PROMISC_PHYS was enabled. The additional change > I made is related to multicast, in that there is equivalent looping back > of multicast within IP for applications that want to receive multicast > packets sent by other applications in the local stack. > > The result is: > > http://zhadum.east.sun.com/ws/seb/seb-ipobs/webrev.accept-2/
So with the change for multicast, what does IPNETALLMULTI mean? Also, seems like the difference between IPNETADDR_MCAST and IPNETADDR_BCAST is no longer important. Nit: s/traffix/traffic/ -- meem
