Hi Thomas,
On Wed, 9 Nov 2005, Thomas Graf wrote:
Now even if this is not acceptable and you really need a way to
favour routes added by userspace over auto/connected routes then we
should fix this in the routing itself and not with a new opertional
state interface state.
Yes, exactly.
The automatic kernel "connected" route should either be removed, or
ignored by the kernel until the interface is fully up (UP&RUNNING).
E.g:
A-B
| |
-----
|
C
B and A have a PtP link to each other and each have an interface to a
shared network, which has C on it. B's link to the subnet fails
(carrier is lost, IFF_RUNNING cleared), B now no longer can
communicate with C, even if it has a route to C via A (e.g. a default
route) because the kernel routing table still contains a valid
connected route for the shared subnet pointing out the ~IFF_RUNNING
interface.
That connected route of the kernel should be removed (or marked
invalid/unusable in some way) while the interface is ~IFF_RUNNING.
regards,
--
Paul Jakma [EMAIL PROTECTED] [EMAIL PROTECTED] Key ID: 64A2FF6A
Fortune:
Hackers are just a migratory lifeform with a tropism for computers.
-
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
