[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #43028] IP_MULTICAST_TTL affects unicast datagrams
|
From: |
Joel Cunningham |
|
Subject: |
[lwip-devel] [bug #43028] IP_MULTICAST_TTL affects unicast datagrams |
|
Date: |
Tue, 26 Aug 2014 18:50:49 +0000 |
|
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.143 Safari/537.36 |
Follow-up Comment #2, bug #43028 (project lwip):
I'm not all that familiar with how often new members get added to the pcb, but
is it out of the question to add another u8_t for mcast_ttl guarded by #if
LWIP_IGMP. Then when sending datagrams, use the appropriate TTL depending on
unicast or multicast destination address
If the bug isn't addressed, then applications are just going to end up having
to create a second socket, possibly with SO_REUSEADDR (_PORT) depending on use
case, to have unicast and multicast senders with different TTLs. This seems
like it will consume more resources for that use case than u8_t
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?43028>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/