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. 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. l2tpd claims to do gratuitous arp, but I don't see any such thing happening and the documentation fails to explain how it treats routing information. Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-686 Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8) Versions of packages l2tpns depends on: ii libc6 2.3.6.ds1-13etch5 GNU C Library: Shared libraries ii libcli1 1.8.6-1 emulates a cisco style telnet comm l2tpns recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
