All clients using tunnel hang/timeout after apparently successful VPN connect

Bug #314221 reported by Chris Metzler on 2009-01-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vpnc (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: vpnc

Recent install of Intrepid.
vpnc 0.5.1r275-1ubuntu1 and 0.5.1r275-1ubuntu1~ppa1 (see discussion)

Expected Behavior: After apparently successful authentication/receipt of connection banner, expected to be able to connect to remote machines in the private network.

What Actually Happens: All such attempts (e.g. to browse a Windows share, to ssh into a Solaris box, etc.) hang and timeout.

Further background:

The ubuntuforums thread, http://ubuntuforums.org/showthread.php?t=1031501 , has basically been me talking to myself about this issue, which I suspect is a misconfiguration of the routing tables by vpnc. Listed there are ifconfig and netstat -r outputs. I can reproduce them here if desired, but it seems easiest to just refer to them there.

Since then, I've also added to the relevant VPN ".conf" file a line with

Target networks (work.net.0.0)/16

where "(work.net.0.0)" is the network address at work. Doing this seemed to produce a more-sane routing table, without the double entries for default:

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
(work_nameserver_1) * 255.255.255.255 UH 0 0 0 tun0
(work_vpn_server) * 255.255.255.255 UH 1390 0 0 tun0
(work_nameserver_2) * 255.255.255.255 UH 0 0 0 tun0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
(work_subnet_small) * 255.255.248.0 U 0 0 0 tun0
link-local * 255.255.0.0 U 0 0 0 eth0
(work.net.0.0) * 255.255.0.0 U 0 0 0 tun0
default router 0.0.0.0 UG 0 0 0 eth0

. . .where "(work_subnet_small)" is a subnet of (work.net.0.0), with the last three bits of the third field not fixed. I'm not sure where that's coming from; but it seems redundant to the second to last line in the table, and thus harmless, anyway.

Please feel free to ask any questions or tell me any info you need.

This could conceivably be the same as Bug #268567; there's not enough information provided in that bug report to say.

Thanks very, very much.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers