jamal <[EMAIL PROTECTED]> writes: > well, the kernel doesnt add default routes - some admin or daemon does. > So whatever solution it is should not delete such routes either.
Sure. Inactivate them instead and activate back on carrier (IFF_RUNNING, not the carrier alone) return. >> Seems inactive routes are really the way to go. But it should behave >> as active in every aspect except being ignored for actual routing >> (i.e., indistinguishable from userspace, normally added and removed). > > but what is this "inactive" thing? Not sure what do you ask. Inactive route, marked internally as such by the kernel when carrier goes down. -- Krzysztof Halasa - 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