hi!
i beleive this patch is a quite valuable enhancement.
apart from the obvious benefits (aka necessity) of being able to use routing
metrics, i also found no reasonable way to make sure pppd will add its
defaultroute without messing the rest of the routing up.
example:
ppp0 persistent ppp connection, meant as a fallback i.e. with low priority.
eth0 sometimes connected, probably with a defaultroute. this is to be
preferred if available.
now if eth0 is already up and has a defaultroute when pppd (configured with
defaultroute) is coming up, no default route will be generated by pppd. if eth0
goes down, the fallback won't work. if pppd is configured with
replacedefaultroute, it will replace eth0's default route, which is not
intended and even breaks routing when ppp0 goes down.
handling routing via ip-up will fail in case of a pppd reconnect (e.g. on every
suspend/resume cycle), in which case the ip-up simply isn't called when ip
comes up, and therefore the routes (which vanished from the routing table when
the interface vanished) will not reappear.
the above patch also seems to be a solution for this.
and while we're at it: as there's no reasonable hook for routing changes (i.e.
also working on a pppd reconnect), having an option to configure static routes
which are inserted together with the default route could be vital to use pppd
for reasonable networking in some cases.
regards,
Chris
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
