On Fri, 11 Nov 2005, Thomas Graf wrote:
The state of an on-demand interface must be visible, typically an
on-demand interface is in dormant state and goes to up while it is
in use and back to dormant after some time of inactivity. Further,
if the interface knows that a demand cannot be met it must announce
this so an alternative can be selected, typically this would be the
carrier/link state.
Visible to whom exactly?
There's different points of view here I think. The casual observer
(applications, some routing daemon which is /not/ involved in
details of the on-demand dialling stuff) is not interested in the
details, just whether the interface is generally useable or not. The
answer for on-demand, generally, is "Yep, interface is good".
You could add heuristics to that obviously, so that if on-dial fails
a few times, you mark it down (and mark the connected route
inactive), but that's part of the internal detail work.
The PPP daemon, or some other on-demand management application
obviously /is/ interested in the details.
To drag this back to the original subject, if IFF_RUNNING is deserted
then so should the connected route (whether its removed or marked
inactive).
If it is not appropriate to remove/make-inactive the connected route,
because you still want that interface to 'attract' packets, then
similarly it is not appropriate for IFF_RUNNING not to be asserted.
There should be consistency between these two things.
regards,
--
Paul Jakma [EMAIL PROTECTED] [EMAIL PROTECTED] Key ID: 64A2FF6A
Fortune:
There is no substitute for good manners, except, perhaps, fast reflexes.
-
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
