On Wed, 2013-12-18 at 01:04 +0100, Tore Anderson wrote:
* Tore Anderson
I'm working on setting up a test VPN server where I can reproduce it and
generate a backtrace to share (I don't dare to do that towards my
employer's VPN server).
Ok, so now I have a dual-stacked OpenVPN test
* Dan Williams
I poked at this today, using this config and your openvpn-2.4.0 RPMs:
[...]
but got no response from the server. Is it still up and configured?
I've at least verified that the NM-openvpn IPv6 changes don't cause
problems for my existing openvpn configurations, so that's
Hello,
I've been quite busy last week so it took me some time to update my Network
Manager setup to the latest git revision, reproduce the bug, investigate,
and change the patches. Tonight I've added 3 comments to
https://bugzilla.gnome.org/show_bug.cgi?id=682620: the coredump backtrace
of the
* Nicolas Iooss
A few weeks ago I ran into a bug in NetworkManager: even though OpenVPN
now supports IPv6 in tunnels, the OpenVPN plugin of NetworkManager
doesn't support it. I found bug 682620
(https://bugzilla.gnome.org/show_bug.cgi?id=682620) and I've implemented
some of the missing
On Tue, 2013-12-17 at 11:57 +0100, Tore Anderson wrote:
* Nicolas Iooss
A few weeks ago I ran into a bug in NetworkManager: even though OpenVPN
now supports IPv6 in tunnels, the OpenVPN plugin of NetworkManager
doesn't support it. I found bug 682620
* Dan Williams
ERROR:platform/nm-linux-platform.c:2212:build_rtnl_addr: assertion failed:
(!nle)
Is that with NM git master, and if so, what date? The reason I ask is
because we broke PtP addresses until 2013-12-02, fixed in commit
f099a04132241790c8f88a651ece49f5c2783d12. The error
* Tore Anderson
I'm working on setting up a test VPN server where I can reproduce it and
generate a backtrace to share (I don't dare to do that towards my
employer's VPN server).
Ok, so now I have a dual-stacked OpenVPN test server running and I've
reproduced the problem there. It's all F20
Hello,
A few weeks ago I ran into a bug in NetworkManager: even though OpenVPN now
supports IPv6 in tunnels, the OpenVPN plugin of NetworkManager doesn't
support it. I found bug 682620 (
https://bugzilla.gnome.org/show_bug.cgi?id=682620) and I've implemented
some of the missing features with the
On Thu, 2013-08-22 at 21:39 +0200, Nicolas Iooss wrote:
2013/8/21 Dan Winship
On 08/19/2013 12:47 PM, Nicolas Iooss wrote:
The patches are working well in my testing environment with
NetworkManager 0.9.8 but with the development revision I've got few
issues such as
* Dan Williams
On Thu, 2013-08-22 at 21:39 +0200, Nicolas Iooss wrote:
Your patch fixed the segmentation fault but now NetworkManager sets up a
default route via the VPN even if the OpenVPN server has not pushed any.
Unfortunately we cannot rely on administrators always pushing a default
On Mon, 2013-08-26 at 19:01 +0200, Tore Anderson wrote:
* Dan Williams
On Thu, 2013-08-22 at 21:39 +0200, Nicolas Iooss wrote:
Your patch fixed the segmentation fault but now NetworkManager sets up a
default route via the VPN even if the OpenVPN server has not pushed any.
On Mon, 2013-08-26 at 19:01 +0200, Tore Anderson wrote:
* Dan Williams
On Thu, 2013-08-22 at 21:39 +0200, Nicolas Iooss wrote:
Your patch fixed the segmentation fault but now NetworkManager sets up a
default route via the VPN even if the OpenVPN server has not pushed any.
* Dan Williams
The assumption here is on the side of security, that it's better to send
all traffic to the VPN and fail, than it is to send your traffic over
un-encrypted links when a VPN is supposed to be active and you think
things are encrypted.
That's a pretty good argument for merging
* Dan Williams
Did the issue with --proto you mentioned in the bug (eg
http://thread.gmane.org/gmane.network.openvpn.devel/7160/focus=7165 )
get fixed as well? Then it would be a lot simpler to enable IPv6
support because we wouldn't need any UI changes to make the user
indicate that they
* Nicolas Iooss
As I understand things after reading
https://community.openvpn.net/openvpn/wiki/Openvpn23ManPage:
(a) With IPv4, OpenVPN server issues an push redirect-gateway def1
command which tells the client to configure a default route via what is
in the route-gateway option. This
* Nicolas Iooss
A few weeks ago I ran into a bug in NetworkManager: even though OpenVPN
now supports IPv6 in tunnels, the OpenVPN plugin of NetworkManager
doesn't support it. I found bug 682620
(https://bugzilla.gnome.org/show_bug.cgi?id=682620) and I've implemented
some of the missing
2013/8/21 Dan Winship
On 08/19/2013 12:47 PM, Nicolas Iooss wrote:
The patches are working well in my testing environment with
NetworkManager 0.9.8 but with the development revision I've got few
issues such as https://bugzilla.gnome.org/show_bug.cgi?id=706286. Now NM
crashes on a
Thanks for testing my patches!
I noticed that the default route also gets redirected to the tunnel
device even though the server does not push this route. So internet
connectivity is broken unless I explicitly enable the use this
connection for resources on its network setting. However I
On 08/19/2013 12:47 PM, Nicolas Iooss wrote:
The patches are working well in my testing environment with
NetworkManager 0.9.8 but with the development revision I've got few
issues such as https://bugzilla.gnome.org/show_bug.cgi?id=706286. Now NM
crashes on a segmentation fault
at
Hello,
A few weeks ago I ran into a bug in NetworkManager: even though OpenVPN now
supports IPv6 in tunnels, the OpenVPN plugin of NetworkManager doesn't
support it. I found bug 682620 (
https://bugzilla.gnome.org/show_bug.cgi?id=682620) and I've implemented
some of the missing features with the
20 matches
Mail list logo
