Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • Thank you for the very elaborate reply, however entering the second half, I experience a bit of a hiccough. the output of ip addr show dev tun0 reads 10: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1412 qdisc pfifo_fast state UNKNOWN group default qlen 500 link/none inet 192.168.128.193/24 brd 192.168.128.255 scope global tun0 valid_lft forever preferred_lft forever, with no peer address to be observed. In addition, the routing table I posted earlier had not been modified by me at all- it was generated entirely by the vpn client.
    – deftfyodor
    Commented Aug 10, 2014 at 18:05
  • @deftfyodor Please see my edit. Commented Aug 11, 2014 at 6:49
  • Using the tcpdump command, I was indeed able to discern the gateway, and route default traffic to it. Unfortunately, it still only works for the specifically provisioned IP ranges. I'm certainly inclined to believe that there is some additional security measure in place- however I have no problem at all routing arbitrary traffic over the same VPN in MS Windows using the AnyConnect client- so there must surely be more to the story.
    – deftfyodor
    Commented Aug 11, 2014 at 19:39
  • @deftfyodor Can you check whether your routing table in Windos is different from that in Linux? Commented Aug 11, 2014 at 19:53
  • It is generally similar, though there are some elements which differ- in particular, 0.0.0.0 is set to route via my network router as the gateway, holding the VPN gateway as the interface. I've edited the question to show the Windows routing table.
    – deftfyodor
    Commented Aug 11, 2014 at 20:02