On Wed, 2005-09-11 at 22:12 +0100, Thomas Graf wrote:
> * Jamal Hadi Salim <[EMAIL PROTECTED]> 2005-11-09 15:13
> > The link change notification should be handled by the fib code as if it
> > was an admin notification.
>
> Something like this should do the job, although it doesn't take care
> of taking things up again for now. Now all supporters of this should
> tell me how to implement any case of on demand interface after taking
> the routes down.
>
> Index: linux-2.6/net/ipv4/fib_frontend.c
> ===================================================================
> --- linux-2.6.orig/net/ipv4/fib_frontend.c
> +++ linux-2.6/net/ipv4/fib_frontend.c
> @@ -630,8 +630,13 @@ static int fib_netdev_event(struct notif
> case NETDEV_DOWN:
> fib_disable_ip(dev, 0);
> break;
> - case NETDEV_CHANGEMTU:
> case NETDEV_CHANGE:
> + if (!netif_carrier_ok(dev)) {
> + fib_disable_ip(dev, 0);
> + break;
> + }
> + /* fall through */
> + case NETDEV_CHANGEMTU:
> rt_cache_flush(0);
> break;
> }
>
> -
Nice;
Is the opposite case missing? i.e what happens when a link goes down
then up? i.e parrot what NETDEV_UP does?
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
