GNOME Bugzilla – Bug 682005
"virtual devices" in GUPnPLinuxContextManager
Last modified: 2012-08-19 14:09:38 UTC
It seems that the GUPnPLinuxContextManager has a bug in handling "virtual devices" (one physical interface with many ip address assignments). Example: # ip addr show eth1 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:13:3b:04:02:ae brd ff:ff:ff:ff:ff:ff inet 169.254.5.4/16 brd 169.254.255.255 scope link eth1:avahi inet 172.29.23.8/24 brd 172.29.23.255 scope global eth1 In my understanding for each ip assignment there should be an own GUPnPContext. Assuming eth1 is up, and eth1:avahi is down in the above example there is one context pointing to 172.29.23.8. If eth1:avahi is coming up i'd expect a "context-available" signal pointing to a new GUPnPContext where gupnp_context_get_host_ip returns 169.254.5.4. But instead i got a "context-unavailable" for 172.29.23.8, followed by a new "context-available" for 172.29.23.8 too.
oh. Think I missed that use-case.
Is there a chance to get that fixed in the near future?
I'll be trying to fix this before monday.
the add->remove->add might be easy to fix, but the same address thing needs changing in GSSDP as well.