Package: l2tpns Version: 2.1.21-1 Severity: normal
The bind_address option in l2tpns has the effect of setting the address bound for l2tp connection listening AND the address which is set on the tunnel interface created by l2tpns. man startup-config gives bind_address When the tun interface is created, it is assigned the address specified here. If no address is given, 1.1.1.1 is used. Packets containing user traffic should be routed via this address if given, otherwise the primary address of the machine. This makes the documentation misleading as it is in fact impossible to configure the virtual tunnel interface independantly of the ip bound for connections. The IP assigned to tun0 created by l2tpns should actualy be more sensibly derived from 'peer_address', which is the gateway given out to connecting clients, or be have it's own configuration which is independent from the behavior of where l2tp connections are accepted (the bind_address). -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core) Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages l2tpns depends on: ii libc6 2.3.6.ds1-13etch2 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]
