fails to autodetect network interface

Bug #817412 reported by Matthias Kretz
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Gupnp
New
Undecided
Unassigned
UPnP Router Control
Won't Fix
Undecided
Unassigned

Bug Description

upnp-control-daemon doesn't work unless I specify -i eth0. Here's the available interfaces to choose from. Shouldn't be that hard to find the right one...

eth0 Link encap:Ethernet HWaddr 58:b0:35:fc:8d:c9
          inet addr:192.168.2.10 Bcast:192.168.2.255 Mask:255.255.255.0
lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
virbr0 Link encap:Ethernet HWaddr 7e:83:25:54:d0:16
          inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0

--debug doesn't report anything about the autodetection process.

Revision history for this message
Daniele Napolitano (dnax88) wrote :

The interface autodetection is made by gupnp library.

Changed in upnp-router-control:
status: New → Won't Fix
Revision history for this message
Dylan McCall (dylanmccall) wrote :

Similar problem with the interface added by lxc. Here's my ifconfig:

eth0 Link encap:Ethernet HWaddr 1c:6f:65:d5:37:c3
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:47 Base address:0x2000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:67332 errors:0 dropped:0 overruns:0 frame:0
          TX packets:67332 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6898398 (6.8 MB) TX bytes:6898398 (6.8 MB)

lxcbr0 Link encap:Ethernet HWaddr 16:3b:9d:55:f5:8b
          inet addr:10.0.3.1 Bcast:10.0.3.255 Mask:255.255.255.0
          inet6 addr: fe80::143b:9dff:fe55:f58b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:199 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:31201 (31.2 KB)

wlan0 Link encap:Ethernet HWaddr 5c:d9:98:4b:dd:ec
          inet addr:192.168.1.121 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::5ed9:98ff:fe4b:ddec/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:4651246 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5416944 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3202101275 (3.2 GB) TX bytes:2229328153 (2.2 GB)

The lxcbr0 interface is created by the lxc-net service, and as soon as it exists gupnp auto-detects that one instead of wlan0.

Revision history for this message
Jens Georg (yg-jensge) wrote :

GUPnP is detecting a network interface that is capable of multicast and usable with IPv4. most of the time this ends up being the last one configured. It's not GUPnP's job to find a network interface that leads to a router.

Probably should switch to use a GUPnPContextManager which reports all network interfaces.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.