On Wed, 2005-09-07 at 11:15 -0700, Stephen Hemminger wrote:
> This how I think ifplugd should work, it should not poll it
> should just use libnetlink and read for the next message.
Incidentally, this is what netplugd already does, for people using
Fedora, Red Hat or Mandriva systems.
htt
On Wed, 07.09.05 11:15, Stephen Hemminger ([EMAIL PROTECTED]) wrote:
>
> This how I think ifplugd should work, it should not poll it
> should just use libnetlink and read for the next message.
>
> The RUNNING flag works for wireless and non-wireless devices.
> If there is a driver it doesn't wor
This how I think ifplugd should work, it should not poll it
should just use libnetlink and read for the next message.
The RUNNING flag works for wireless and non-wireless devices.
If there is a driver it doesn't work on than that is a bug in
the device driver and should be fixed ASAP, not worked a
On Fri, 02.09.05 10:34, Jean Tourrilhes ([EMAIL PROTECTED]) wrote:
>
> Lennart Poettering wrote :
> >
> > It is simply not true that all current
> > network drivers set IFF_RUNNING correctly. ifplugd does the best it
> > can to detect the carrier, but is still incompatible out of the box
> > wit
On Fri, Sep 02, 2005 at 10:34:03AM -0700, Jean Tourrilhes wrote:
> Another part of the problem is that the notion of carrier
> detection only apply to some technology (mostly Ethernet). With
> Wireless, there is no notion of carrier. You can somewhat *emulate* it
> using the association, but
Lennart Poettering wrote :
>
> It is simply not true that all current
> network drivers set IFF_RUNNING correctly. ifplugd does the best it
> can to detect the carrier, but is still incompatible out of the box
> with some drivers. To write carrier detection code that works reliably
> on most drive
On Fri, 02.09.05 11:40, Jiri Benc ([EMAIL PROTECTED]) wrote:
> On Thu, 1 Sep 2005 10:04:22 -0700, Stephen Hemminger wrote:
> > By the way, last time I looked at the ifplugd source it was using
> > outdated and incorrect ways to detect carrier. It should just
> > open a netlink socket and wait for
On Thu, 1 Sep 2005 10:04:22 -0700, Stephen Hemminger wrote:
> By the way, last time I looked at the ifplugd source it was using
> outdated and incorrect ways to detect carrier. It should just
> open a netlink socket and wait for carrier event. Instead it seems
> to muck around looking at MII, wirel
