[l2tpns-users] Is there a patch to teach l2tpns to honor metric in Framed-Route statements?

[Johannes J. <jj...@gl...>]

Hi List,

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 1.2.3.4 100

Is there any patch to add this feature to l2tpns?



Background:

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 1.2.3.4/30, the quagga instance on the LNS then adds a route to 
1.2.3.4/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 1.2.3.4/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 ;)


Best regards,

    John