desktop-packages team mailing list archive

[Mathieu Trudel-Lapierre <mathieu.tl@xxxxxxxxx>]

I'm not sure I follow. Isn't that exactly what the "X.X.X.X 192.168.0.1
255.255.255.255 UGH 0 0 0 eth1" route in route -n output you pasted all
about already? (see fourth from the top).

Reaching a computer connected to a VPN via a public IP connected to the
local net is on purpose not allowed, unless you're checking "Use this
connection only for the resources on its network" checkbox, under Routes
in the VPN's configuration dialog on your system.

Am I missing something?

** Changed in: network-manager (Ubuntu)
       Status: New => Incomplete

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Importance: Low => Wishlist

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/916062

Title:
  network-manager should ad route to external ip when using vpn (w.
  solution)

Status in “network-manager” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu: oineric 11.10
  network-manager: 0.9.1.90-0ubuntu5.1

  The problem is when using any VPN client from network-manager and
  consists of not being able to connect from the external net through
  port forwarding.

  Internal IP->local computer (works)
  VPN IP->local computer (works)
  Local computer->internal network (works)
  Local computer->vpn->internet (works)
  Ext IP->[port forwarding]->local computer (does not work)

  
  When using openvpn I get the following routing table (VPN adresses hidden):

  $ route -n
  Kernel IP routing table
  Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
  0.0.0.0         X.X.X.X         0.0.0.0         UG    0      0        0 tap0
  169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 eth1
  X.X.X.X         0.0.0.0         255.255.255.0   U     0      0        0 tap0
  X.X.X.X         192.168.0.1     255.255.255.255 UGH   0      0        0 eth1
  192.168.0.0     0.0.0.0         255.255.255.0   U     1      0        0 eth1

  Solution (External IP Y.Y.Y.Y):

  $ route add -host Y.Y.Y.Y gw 192.168.0.1 dev eth1

  
  Now we can reach the computer on both Y.Y.Y.Y and the vpn ip.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/916062/+subscriptions