|From:||Julian Gardner [RSD]|
|Subject:||RE: [lwip-users] SO_REUSEADDR|
|Date:||Sat, 1 Sep 2007 19:45:54 +0100|
Thanks for the explanation, yes it is for a UPnP stack that I am playing with until I can get the “commercial stack” we are going to use ported.
I have all the IGMP stuff working and the stack working and the device running but the problem is with the XBOX360, it seems to ignore my ssdp announcement! I have checked with other UPnP devices and it seems that the XBOX needs you to initiate the link by waiting on its ssdp announcement!
[mailto:address@hidden On Behalf Of Frédéric BERNON
First SO_REUSEADDR is not currently supported by CVS HEAD (Christiian started something, but he has disable the code from memory). "Broadcasting" to 220.127.116.11 is not the "best" _expression_, it's more "multicasting". But, to send to 18.104.22.168:1900 (uPNP I suppose), you don't have to bind to 22.214.171.124:1900, but to any:any. To hear the other devices, you should use a second socket for that, binded to any:1900. Is it the case? If yes, SO_REUSEADDR is not necessary to your project. But in all cases, to process incoming multicast packets, you should use IGMP to inform you network (switchs, routers...) to route to your target all packets "to 126.96.36.199". But once these packets reach your target, if LWIP_IGMP=0, I don't know if multicast packets are really processed.
There is a task open to include a support of SO_REUSEADDR option, but not yet started...
|[Prev in Thread]||Current Thread||[Next in Thread]|