On Thu, 2005-10-11 at 01:03 +0100, Thomas Graf wrote:
> > > Index: linux-2.6/net/ipv4/fib_frontend.c
> > Is the opposite case missing? i.e what happens when a link goes down
> > then up? i.e parrot what NETDEV_UP does?
>
> Yes, I haven't figured out how to uniquely identify a carrier up event
> without adding additional fields to netdevice.
from inspection: Whats wrong with what netif_carrier_ok() tells you?
i.e to extrapolate what you have (it seems to be out
fib_netdev_event())- something along:
case NETDEV_CHANGE:
rt_cache_flush(0);
if (!netif_carrier_ok(dev)) {
printk("%s:link went down\n",dev->name);
fib_disable_ip(dev, 0);
}
if (netif_carrier_ok(dev)) {
printk("%s:link went up\n",dev->name);
call the code NETDEV_UP uses;
}
cheers,
jamal
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
