Bug#461373: netspeed_applet: Monitors the wmaster0 interface when configured to monitor a connected device
Mike Hommey
mh at glandium.org
Mon Jan 21 19:18:57 UTC 2008
On Mon, Jan 21, 2008 at 10:28:59AM +0100, Josselin Mouette wrote:
> Hi,
>
> Le vendredi 18 janvier 2008 à 14:11 +0900, Mike Hommey a écrit :
> > Package: netspeed
> > Version: 0.14-1
> > Severity: normal
> > File: netspeed_applet
> >
> > Wireless devices drivers using the mac80211 stack have a wmaster%d
> > supplementary interface that is used internally. This interface doesn't
> > have RX/TX statistics (probably because it's unconfigured, which is
> > intended), so when netspeed monitors it, it fails to monitor bandwidth.
> >
> > It appears netspeed picks wmaster0 over wlan0 when configured to monitor
> > a connected device. It should prefer wlan0.
>
> Normally, Netspeed uses the default route to select the device. If the
> route method fails, it uses libgtop which should also say wmaster0 is
> unconfigured.
>
> Could you send the output of “route -n” and “ifconfig -a” on your
> system?
jigen:/home/mh# /sbin/ifconfig -a
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:17042 errors:0 dropped:0 overruns:0 frame:0
TX packets:17042 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5508087 (5.2 MiB) TX bytes:5508087 (5.2 MiB)
wlan0 Link encap:Ethernet HWaddr 00:1d:e0:26:0f:4b
inet addr:192.168.1.110 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21d:e0ff:fe26:f4b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6209019 errors:0 dropped:0 overruns:0 frame:0
TX packets:3561569 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8938473661 (8.3 GiB) TX bytes:351669936 (335.3 MiB)
wmaster0 Link encap:UNSPEC HWaddr 00-1D-E0-26-0F-4B-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING 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)
jigen:/home/mh# /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0
It seems that when enabling "Always monitor a connected device, if possible",
it doesn't care very much about routes. If I disable it, select "lo" and
enable it again, lo is monitorred (it's UP, after all). Likewise for
wmaster0 and wlan0. And once it's settled on wlan0, if you bring your
interfaces down (e.g, with the nm-applet by disabling networking, which
brings both wmaster0 and wlan0 down, but not lo), it switches to
wmaster0 and tells wmaster0 is down. Then, enabling networking again
brings up the interfaces again, but netspeed stays on wmaster0.
Mike
More information about the pkg-gnome-maintainers
mailing list