Bug#312095: netspeed: "Always monitor a connected device, if possible" - but not lo or dummy0

[Hans Ulrich Niedermann]

Lo=C3=AFc Minier <lool@dooz.org> writes:

>         Hi,
>
> On Sun, Jun 05, 2005, Hans Ulrich Niedermann wrote:
>> However, the same reasoning applies to the "dummy+" interfaces, so
>> dummy0 should never be chosen automatically, and the "dummy+"
>> interfaces should probably added to the same exception list where "lo"
>> already is.
>
>  I wrote the attached patch, I tested it quicly, and it seems ok with
>  a dummy0 device.  This only works when netspeed search for the next
>  interface because it has been brought down, it won't work on startup I
>  think.

Thanks for the patch. I have tested 0.12.1-1, and it looks fine.

If I have set eth0 as the device to be monitored, and if there is no
eth0 when netspeed is started up, netspeed shows a disconnected eth0.

When either eth0 or wlan0 is brought up, it switches over to that
device.

It may be desirable to be able to set "non-lo and non-dummy" while
only "lo" and "dummy0" are up, though.

Uli