Package: vpnc Version: 0.3.3+SVN20050909-4 Severity: important With the latest few 0.3.3 svn snapshots of vpnc, the routing information no longer seems to be set up correctly. Also, there's an extra warning about RTNETLINK there wasn't there in the old (0.3.2-snapshot) version. vpnc 0.3.2+SVN20050326-2 works for me, newer versions doesn't.
vpnc 0.3.2+SVN20050326-2: smyslov:~# vpnc-connect <config> Enter password for <censored> vpnc version 0.3.2 IKE SA selected psk+xauth-3des-sha1 NAT status: this end behind NAT? YES -- remote end behind NAT? no got address 10.162.253.115 IPSEC SA selected 3des-sha1 VPNC started in background (pid: 9318)... smyslov:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface <censored> <censored> 255.255.255.255 UGH 0 0 0 eth0 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 default * 0.0.0.0 U 0 0 0 tun0 vpnc 0.3.3++SVN20050909-4: smyslov:~: vpnc-connect <config> Enter password for <censored> vpnc version 0.3.3 IKE SA selected psk+xauth-3des-sha1 NAT status: this end behind NAT? YES -- remote end behind NAT? no got address 10.162.252.184 IPSEC SA selected 3des-sha1 RTNETLINK answers: File exists VPNC started in background (pid: 9525)... smyslov:~/deb# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface <censored> <censored> 255.255.255.255 UGH 0 0 0 eth0 <censored> * 255.255.255.255 UH 0 0 0 tun0 <censored> * 255.255.255.255 UH 0 0 0 tun0 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 10.162.252.0 * 255.255.254.0 U 0 0 0 tun0 default <censored> 0.0.0.0 UG 0 0 0 eth0 disconnected: smyslov:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 default 128.1.168.192.i 0.0.0.0 UG 0 0 0 eth0 Clearly the new vpnc sets up several extra route entries compared to the old vpnc. The old vpnc works, the new one doesn't. Because of company security policy I've had to censor quite a lot of details, I hope there's enough left to give you a clue anyway. Justification for severity: makes the package useless at least with this particular setup. I cannot tell whether it's a generic problem or a specific problem, hence I'm not using Severity: grave. Regards: David Weinehall -- /) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\ // ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ // Diamond-white roses of fire // \) http://www.acc.umu.se/~tao/ (/ Beautiful hoar-frost (/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
