Package: l2tpns
Version: 2.1.21-1
Severity: important
l2tpns does not appear to route packets from/to ranges not within that
which is allocated to the tunnels themselves.
Consider for example
[E:192.168.0.0/24]--[LAC:10.0.0.2]---[LNS:10.0.0.1]--[E:192.168.1.0/24]
It seems l2tpns will only
Jonathan McDowell wrote:
l2tpns will only route traffic over the tun interface if it knows about
the appropriate IPs. How do you expect it to know which end point to
route to otherwise? You don't supply any details of your RADIUS config
but at a guess you haven't got a Framed-Route entry for the
Colin Alston wrote:
I don't have a Frame-Route, no. From RADIUS documentation that attribute
suggests it is a route to pass along to the LAC. I'm guessing l2tpns
does not document its treatment of that attribute, or I'm blind.
Apparently I am blind, and stupid. I do need a Framed-Route
On Wed, Jun 04, 2008 at 11:03:48AM +0200, Colin Alston wrote:
Package: l2tpns
Version: 2.1.21-1
Severity: important
l2tpns does not appear to route packets from/to ranges not within that
which is allocated to the tunnels themselves.
Consider for example
severity wishlist
retitle documentation could do with much improvement
thanks
On Wed, Jun 04, 2008 at 12:01:08PM +0200, Colin Alston wrote:
Colin Alston wrote:
I don't have a Frame-Route, no. From RADIUS documentation that attribute
suggests it is a route to pass along to the LAC. I'm
5 matches
Mail list logo
