From: Johannes Jakob <jj@gl...> - 2009-12-11 14:06:47
When using Framed-Route statemens in Radius like 10.0.0.0/24 it works
just fine, but l2tpns doesn't honor gateway or metric specifications in
the form of
Framed-Route += 10.0.0.0/24 126.96.36.199 100
Is there any patch to add this feature to l2tpns?
Assume a dial-in router that is running quagga and talks BGP to another
quagga running on the LNS. The router tells the LNS it has a route to
subnet 188.8.131.52/30, the quagga instance on the LNS then adds a route to
184.108.40.206/0 to dev tun0. But now the l2tpns process does not know how, or
to which session it has to route the packets destined for 220.127.116.11/0
because the link IP/NET <-> Session does not exist.
Is there any way to achieve this? I can't use the integrated bgpd,
because it doesn't provide the options we need (prefix filter, route
maps... you name it), but how can I tell l2tpns there are routes it
hasn't set itself?
So my solution was to avoid talking bgp at all and trying to set these
routes via radius. This option currently fails, because I have to set
this route on two LNS (primary and backup), which are both connected at
the same time, so I have to distribute the routes with different costs
and tried to achieve this by using metrics... which aren't honored by
l2tpns at all....
Do you have any ideas about this scenario? Metrics would be great,
because they would solve the 3minutes timeout issue introduced by bgp,
when the primary connection fails....
Well, looking forward to any help and hoping, that this list somehow is
still alive ;)