On Thu, Oct 27, 2016 at 08:15:20PM +0200, Vicente Herrera Cobo wrote:
> Regards to all,
>
> by adding a specified ovpn file from my provider get the following
> error: "Error: configuration error: unsupported blob/xml element (line
> 104)."
>
> Line 104: ""
Hi,
at the moment the openvpn plugin
Regards to all,
by adding a specified ovpn file from my provider get the following
error: "Error: configuration error: unsupported blob/xml element (line
104)."
Line 104: ""
Attachment screenshot and ovpn file.
Thanks for your attention.
client
dev tun
resolv-retry infinite
nobind
persist-key
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
what's better between
removing code in every VPN plugin (like I did) or patching NetworkManager
to ignore this option which is not supported by libnl.
Regards,
Nicolas
PS: my patches are also available on GitHub,
https://github.com/fishilico/network-manager-openvpn/commits/master
2013/12/18 Tore
* 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
When a socket is closed, poll(2) will always return readable
immediately, read(2) will return 0 (EOF), thus we need to remove it
from the watched channels, or else the cpu get spinning to 100%.
Signed-off-by: Bao Haojun baohao...@gmail.com
---
src/nm-openvpn-service.c | 10 +-
1 file
Hi, all
I'm using debian testing, and the version is
network-manager-openvpn-0.9.4.0.
I can connect to my openvpn server successfully, but after a while, my
CPU usage got high:
PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
11039 root 20 0 74032 3576
!
Bao Haojun hj...@marvell.com writes:
Hi, all
I'm using debian testing, and the version is
network-manager-openvpn-0.9.4.0.
I can connect to my openvpn server successfully, but after a while, my
CPU usage got high:
PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
Hello !
Using natty with backports and natty-bleed-ppa repositories enabled.
When somebody try to load a custom openvpn config file, unwanted options
are set (eg: redirect-gateway def1), then we could suppose other ones
are maybe discarded (since the opposite is true)..
When somebody import
On Tue, 2009-12-15 at 11:08 -0500, Matt Wilks wrote:
On 09-12-14 06:09 PM, Dan Williams wrote:
On Mon, 2009-12-14 at 09:24 -0500, Matt Wilks wrote:
This must have been discussed before on this list, but I'm curious the
reasoning behind making network-manager-openvpn have its own GUI
On Wed, 2009-12-16 at 12:43 PM, Dan Williams wrote:
On Tue, 2009-12-15 at 11:08 -0500, Matt Wilks wrote:
What prompted my initial query was the lack of support forca,cert
andkey directives (supported in OpenVPN since 2.1-beta7, Nov
2005). They allow you to specify the key files directly in the
On 09-12-14 06:09 PM, Dan Williams wrote:
On Mon, 2009-12-14 at 09:24 -0500, Matt Wilks wrote:
This must have been discussed before on this list, but I'm curious the
reasoning behind making network-manager-openvpn have its own GUI for
configuration in the first place. Why not offer
%, especially when it makes things nearly unusable for
the other 90.
This must have been discussed before on this list, but I'm curious the
reasoning behind making network-manager-openvpn have its own GUI for
configuration in the first place. Why not offer functionality similar
to the Windows/Mac
% of use-cases, but I don't think we should be designing
for that last 5%, especially when it makes things nearly unusable for
the other 90.
This must have been discussed before on this list, but I'm curious the
reasoning behind making network-manager-openvpn have its own GUI
that config so we can see what's going on with it?
My config was attached :) But someone may need to use other parameters
as well.
* Options not modifiable actually by network-manager-openvpn should also
be gathered and displayed, eg: in a dynamic listbox like for the routes,
with an add
.
What specific configuration were you having problems with? Can you
attach that config so we can see what's going on with it?
My config was attached :) But someone may need to use other parameters
as well.
* Options not modifiable actually by network-manager-openvpn should also
to make it work like everybody at first glance
will expect it should, ie: allowing to import any valid openvpn
configuration file.
Let me just send you, instead of a patch, a more serious analysis of
what could make network-manager-openvpn less annoying:
1. It should be possible to activate
by network-manager-openvpn should also
be gathered and displayed, eg: in a dynamic listbox like for the routes,
with an add button. There could be a pop-up in the first column to set
or change the option name, an editable field in the second column to set
or change its value.
0.7 already provides
:) But someone may need to use other parameters
as well.
* Options not modifiable actually by network-manager-openvpn should also
be gathered and displayed, eg: in a dynamic listbox like for the routes,
with an add button. There could be a pop-up in the first column to set
or change the option name
)
that if you do this, modifying the vpn connection settings through the
network manager openvpn configuration dialog afterwards will overwrite
the settings.
First configure everything else for your vpn connection through network
manager. Then fire up the gconf configuration editor
(Applications
certificate is deprecated so the CA I
use (CAcert) doesn't use this flag any more. At the moment I can't use
Network Manager to connect to my VPN because of this, but instead I have run
openvpn through my CLI.
It would be nice to have this feature in the Network Manager OpenVPN addon.
Regards,
Alexander
be nice to have this feature in the Network Manager OpenVPN
addon.
Please put feature requests like this in bugzilla. I don't get emailed,
but tend to check pet projects I work on pretty religously. This makes
it easier for me to post patches and have NM developers review them for
inclusion.
Jon
On Fri, 2006-12-08 at 18:22 -0500, Jim Popovitch wrote:
Is there a way to specify a non-standard remote port to use with
network-manager-openvpn? I don't see anything on the vpn config gui,
nor could I find anything conclusive via Google.
Not yet; what's the config item and how is it used
On Mon, 2006-12-11 at 17:48 -0500, Dan Williams wrote:
On Fri, 2006-12-08 at 18:22 -0500, Jim Popovitch wrote:
Is there a way to specify a non-standard remote port to use with
network-manager-openvpn? I don't see anything on the vpn config gui,
nor could I find anything conclusive via
Is there a way to specify a non-standard remote port to use with
network-manager-openvpn? I don't see anything on the vpn config gui,
nor could I find anything conclusive via Google.
Tia,
-Jim P.
___
NetworkManager-list mailing list
NetworkManager
42 matches
Mail list logo
