Hi,

First SO_REUSEADDR is not currently supported by CVS HEAD (Christiian started 
something, but he has disable the code from memory). "Broadcasting" to 
239.255.225.250 is not the "best" expression, it's more "multicasting". But, to 
send to 239.255.255.250:1900 (uPNP I suppose), you don't have to bind to 
239.255.255.250: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 239.255.255.250". 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...
  ----- Original Message ----- 
  From: Julian Gardner [RSD] 
  To: Mailing list for lwIP users 
  Sent: Saturday, September 01, 2007 8:10 PM
  Subject: [lwip-users] SO_REUSEADDR


  Just put in the new cvs code and after removing some useless code I started 
trying to find out why some of my code is not being called.

   

  This is the problem, I am broadcasting on 239.255.255.250:1900 and that's ok 
but I also need to listen to the same address and port so I can hear the other 
devices announcing that they are available, I get the raw packets but its lost 
on its way up the chain?

   

  Is this a known problem? Is there any way around it?

   

  Joolz

   



------------------------------------------------------------------------------


  _______________________________________________
  lwip-users mailing list
  [email protected]
  http://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users

Reply via email to