[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-03 Thread Peter Meier
I can confirm that the problem with the routes not (or false) being propagated still exists on gutsy. I get for example the following route propagated: 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 tap0 instead of: 0.0.0.0 192.168.1.1 0.0.0.0 UG

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-19 Thread Stephan Wüthrich
Same Problem to me. There are no pulls for routes and also my resolv.conf is empty after connection to a VPN Server. Would be great, if this will be fixed, because the Network Manager Plugin is a cool tool. -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-20 Thread ginger22
I'm register now and this is my first post. Does any moves this network-manager? A really need working OpenVPN with this plugin... -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-23 Thread Kevin Eilers
Hi! For me this is also a must-have feature. It would really simplify the process of securely surfing in public WLANs. Thanks Kevin -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, whic

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-25 Thread Darren Albers
When I use the following in my server.conf push "redirect-gateway def1" I am able route all but my local subnet down the tunnel. I know this doesn't solve the problem for those that want to route just a specific subnet but for those who want to use the openvpn plugin to protect their traffic when

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-12-09 Thread David Futcher
** Tags added: network-manager ** Tags removed: networkmanager -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-04-09 Thread seenxu
It won't work for me, too. with native command, the route table looks like this [EMAIL PROTECTED]:~$ route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 129.69.244.1129.69.245.137 255.255.255.255 UGH 0 00 tun0 129.69.245.

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-04-09 Thread seenxu
sorry forget to name my spec. xubuntu 7.10 amd64 and check out the native openvpn connection log, it lacks of the part of adding new route definitions. Wed Apr 9 10:30:12 2008 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-03-15 Thread falstaff
This Problem is still not fixed for me: Using OpenVPN over NetworkManager $ route Kernel-IP-Routentabelle ZielRouter Genmask Flags Metric RefUse Iface 3-063.dsl.cyber 192.168.0.1 255.255.255.255 UGH 0 00 wlan0 192.168.2.0 * 255.2

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-06-16 Thread Kuartzer
Hi there... Just a BUMP I can confirm that this bug is still present on Ubuntu 8.04 (hardy), running nm-applet 0.6.6. Does anyone know if there are any prediction on resolving this issue? Is there a workaround, or do you recommend other client? As for now I'm running openvpn in the cli. I

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-03-15 Thread falstaff
This Problem is still not fixed for me: Using OpenVPN over NetworkManager $ route Kernel-IP-Routentabelle ZielRouter Genmask Flags Metric RefUse Iface 3-063.dsl.cyber 192.168.0.1 255.255.255.255 UGH 0 00 wlan0 192.168.2.0 * 255.2

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-04-09 Thread seenxu
It won't work for me, too. with native command, the route table looks like this [EMAIL PROTECTED]:~$ route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 129.69.244.1129.69.245.137 255.255.255.255 UGH 0 00 tun0 129.69.245.

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-04-09 Thread seenxu
sorry forget to name my spec. xubuntu 7.10 amd64 and check out the native openvpn connection log, it lacks of the part of adding new route definitions. Wed Apr 9 10:30:12 2008 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-19 Thread Stephan Wüthrich
Same Problem to me. There are no pulls for routes and also my resolv.conf is empty after connection to a VPN Server. Would be great, if this will be fixed, because the Network Manager Plugin is a cool tool. -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-20 Thread ginger22
I'm register now and this is my first post. Does any moves this network-manager? A really need working OpenVPN with this plugin... -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-23 Thread Kevin Eilers
Hi! For me this is also a must-have feature. It would really simplify the process of securely surfing in public WLANs. Thanks Kevin -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, whic

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-25 Thread Darren Albers
When I use the following in my server.conf push "redirect-gateway def1" I am able route all but my local subnet down the tunnel. I know this doesn't solve the problem for those that want to route just a specific subnet but for those who want to use the openvpn plugin to protect their traffic when

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-12-09 Thread David Futcher
** Tags added: network-manager ** Tags removed: networkmanager -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-03 Thread Peter Meier
I can confirm that the problem with the routes not (or false) being propagated still exists on gutsy. I get for example the following route propagated: 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 tap0 instead of: 0.0.0.0 192.168.1.1 0.0.0.0 UG

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-06-16 Thread Kuartzer
Hi there... Just a BUMP I can confirm that this bug is still present on Ubuntu 8.04 (hardy), running nm-applet 0.6.6. Does anyone know if there are any prediction on resolving this issue? Is there a workaround, or do you recommend other client? As for now I'm running openvpn in the cli. I

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-12-09 Thread David Futcher
** Tags added: network-manager ** Tags removed: networkmanager -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-04-09 Thread seenxu
It won't work for me, too. with native command, the route table looks like this [EMAIL PROTECTED]:~$ route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 129.69.244.1129.69.245.137 255.255.255.255 UGH 0 00 tun0 129.69.245.

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-04-09 Thread seenxu
sorry forget to name my spec. xubuntu 7.10 amd64 and check out the native openvpn connection log, it lacks of the part of adding new route definitions. Wed Apr 9 10:30:12 2008 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-03-15 Thread falstaff
This Problem is still not fixed for me: Using OpenVPN over NetworkManager $ route Kernel-IP-Routentabelle ZielRouter Genmask Flags Metric RefUse Iface 3-063.dsl.cyber 192.168.0.1 255.255.255.255 UGH 0 00 wlan0 192.168.2.0 * 255.2

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-19 Thread Stephan Wüthrich
Same Problem to me. There are no pulls for routes and also my resolv.conf is empty after connection to a VPN Server. Would be great, if this will be fixed, because the Network Manager Plugin is a cool tool. -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-20 Thread ginger22
I'm register now and this is my first post. Does any moves this network-manager? A really need working OpenVPN with this plugin... -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-23 Thread Kevin Eilers
Hi! For me this is also a must-have feature. It would really simplify the process of securely surfing in public WLANs. Thanks Kevin -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, whic

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-25 Thread Darren Albers
When I use the following in my server.conf push "redirect-gateway def1" I am able route all but my local subnet down the tunnel. I know this doesn't solve the problem for those that want to route just a specific subnet but for those who want to use the openvpn plugin to protect their traffic when

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-03 Thread Peter Meier
I can confirm that the problem with the routes not (or false) being propagated still exists on gutsy. I get for example the following route propagated: 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 tap0 instead of: 0.0.0.0 192.168.1.1 0.0.0.0 UG

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-06-16 Thread Kuartzer
Hi there... Just a BUMP I can confirm that this bug is still present on Ubuntu 8.04 (hardy), running nm-applet 0.6.6. Does anyone know if there are any prediction on resolving this issue? Is there a workaround, or do you recommend other client? As for now I'm running openvpn in the cli. I

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-04-09 Thread seenxu
It won't work for me, too. with native command, the route table looks like this [EMAIL PROTECTED]:~$ route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 129.69.244.1129.69.245.137 255.255.255.255 UGH 0 00 tun0 129.69.245.

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-04-09 Thread seenxu
sorry forget to name my spec. xubuntu 7.10 amd64 and check out the native openvpn connection log, it lacks of the part of adding new route definitions. Wed Apr 9 10:30:12 2008 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-03-15 Thread falstaff
This Problem is still not fixed for me: Using OpenVPN over NetworkManager $ route Kernel-IP-Routentabelle ZielRouter Genmask Flags Metric RefUse Iface 3-063.dsl.cyber 192.168.0.1 255.255.255.255 UGH 0 00 wlan0 192.168.2.0 * 255.2

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-12-09 Thread David Futcher
** Tags added: network-manager ** Tags removed: networkmanager -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-06-16 Thread Kuartzer
Hi there... Just a BUMP I can confirm that this bug is still present on Ubuntu 8.04 (hardy), running nm-applet 0.6.6. Does anyone know if there are any prediction on resolving this issue? Is there a workaround, or do you recommend other client? As for now I'm running openvpn in the cli. I

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-19 Thread Stephan Wüthrich
Same Problem to me. There are no pulls for routes and also my resolv.conf is empty after connection to a VPN Server. Would be great, if this will be fixed, because the Network Manager Plugin is a cool tool. -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-20 Thread ginger22
I'm register now and this is my first post. Does any moves this network-manager? A really need working OpenVPN with this plugin... -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-23 Thread Kevin Eilers
Hi! For me this is also a must-have feature. It would really simplify the process of securely surfing in public WLANs. Thanks Kevin -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, whic

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-25 Thread Darren Albers
When I use the following in my server.conf push "redirect-gateway def1" I am able route all but my local subnet down the tunnel. I know this doesn't solve the problem for those that want to route just a specific subnet but for those who want to use the openvpn plugin to protect their traffic when

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-03 Thread Peter Meier
I can confirm that the problem with the routes not (or false) being propagated still exists on gutsy. I get for example the following route propagated: 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 tap0 instead of: 0.0.0.0 192.168.1.1 0.0.0.0 UG

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-12-09 Thread David Futcher
** Tags added: network-manager ** Tags removed: networkmanager -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-19 Thread Stephan Wüthrich
Same Problem to me. There are no pulls for routes and also my resolv.conf is empty after connection to a VPN Server. Would be great, if this will be fixed, because the Network Manager Plugin is a cool tool. -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-20 Thread ginger22
I'm register now and this is my first post. Does any moves this network-manager? A really need working OpenVPN with this plugin... -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-23 Thread Kevin Eilers
Hi! For me this is also a must-have feature. It would really simplify the process of securely surfing in public WLANs. Thanks Kevin -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, whic

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-25 Thread Darren Albers
When I use the following in my server.conf push "redirect-gateway def1" I am able route all but my local subnet down the tunnel. I know this doesn't solve the problem for those that want to route just a specific subnet but for those who want to use the openvpn plugin to protect their traffic when

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-03 Thread Peter Meier
I can confirm that the problem with the routes not (or false) being propagated still exists on gutsy. I get for example the following route propagated: 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 tap0 instead of: 0.0.0.0 192.168.1.1 0.0.0.0 UG

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-06-16 Thread Kuartzer
Hi there... Just a BUMP I can confirm that this bug is still present on Ubuntu 8.04 (hardy), running nm-applet 0.6.6. Does anyone know if there are any prediction on resolving this issue? Is there a workaround, or do you recommend other client? As for now I'm running openvpn in the cli. I

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-04-09 Thread seenxu
It won't work for me, too. with native command, the route table looks like this [EMAIL PROTECTED]:~$ route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 129.69.244.1129.69.245.137 255.255.255.255 UGH 0 00 tun0 129.69.245.

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-04-09 Thread seenxu
sorry forget to name my spec. xubuntu 7.10 amd64 and check out the native openvpn connection log, it lacks of the part of adding new route definitions. Wed Apr 9 10:30:12 2008 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-12-09 Thread David Futcher
** Tags added: network-manager ** Tags removed: networkmanager -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-04-09 Thread seenxu
It won't work for me, too. with native command, the route table looks like this [EMAIL PROTECTED]:~$ route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 129.69.244.1129.69.245.137 255.255.255.255 UGH 0 00 tun0 129.69.245.

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-04-09 Thread seenxu
sorry forget to name my spec. xubuntu 7.10 amd64 and check out the native openvpn connection log, it lacks of the part of adding new route definitions. Wed Apr 9 10:30:12 2008 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-03-15 Thread falstaff
This Problem is still not fixed for me: Using OpenVPN over NetworkManager $ route Kernel-IP-Routentabelle ZielRouter Genmask Flags Metric RefUse Iface 3-063.dsl.cyber 192.168.0.1 255.255.255.255 UGH 0 00 wlan0 192.168.2.0 * 255.2

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-06-16 Thread Kuartzer
Hi there... Just a BUMP I can confirm that this bug is still present on Ubuntu 8.04 (hardy), running nm-applet 0.6.6. Does anyone know if there are any prediction on resolving this issue? Is there a workaround, or do you recommend other client? As for now I'm running openvpn in the cli. I

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-19 Thread Stephan Wüthrich
Same Problem to me. There are no pulls for routes and also my resolv.conf is empty after connection to a VPN Server. Would be great, if this will be fixed, because the Network Manager Plugin is a cool tool. -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-20 Thread ginger22
I'm register now and this is my first post. Does any moves this network-manager? A really need working OpenVPN with this plugin... -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-23 Thread Kevin Eilers
Hi! For me this is also a must-have feature. It would really simplify the process of securely surfing in public WLANs. Thanks Kevin -- [Feisty] n-m-openvpn fails to pull routes https://bugs.launchpad.net/bugs/88069 You received this bug notification because you are a member of Ubuntu Bugs, whic

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-25 Thread Darren Albers
When I use the following in my server.conf push "redirect-gateway def1" I am able route all but my local subnet down the tunnel. I know this doesn't solve the problem for those that want to route just a specific subnet but for those who want to use the openvpn plugin to protect their traffic when

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2007-11-03 Thread Peter Meier
I can confirm that the problem with the routes not (or false) being propagated still exists on gutsy. I get for example the following route propagated: 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 tap0 instead of: 0.0.0.0 192.168.1.1 0.0.0.0 UG

[Bug 88069] Re: [Feisty] n-m-openvpn fails to pull routes

2008-03-15 Thread falstaff
This Problem is still not fixed for me: Using OpenVPN over NetworkManager $ route Kernel-IP-Routentabelle ZielRouter Genmask Flags Metric RefUse Iface 3-063.dsl.cyber 192.168.0.1 255.255.255.255 UGH 0 00 wlan0 192.168.2.0 * 255.2