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 > > [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 route traffic over the tun interface if it is natted > (the source address is either the tunnel or the LNS IP) making it > fairly useless for most uses of L2TP.
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 network you want to route to the username in question? I have used l2tpns with non NATed routed subnets in the past without problems. > l2tp does not provide any useful debugging from my side, only that when > I do something like 'traceroute -s 192.168.0.1 10.0.0.1' the packets hit > the tun0 interface from tcpdump, but tcpdump on the other end does not > see anything. Have you tried altering the debug level (set debug <n>)? J. -- 101 things you can't have too much of : 43 - Penguins. This .sig brought to you by the letter A and the number 48 Product of the Republic of HuggieTag -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
