Ubuntu
network-manager-openvpn package

network-manager-openvpn fails to connect with specific config

Bug #528382 reported by Jan Nekvasil
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
network-manager-openvpn (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: network-manager-openvpn

NetworkManager 0.8, Lucid. I'm using three distinct openvpn configs, each one to connect to different network. Two of them (using TCP) works flawlessly with network-manager-openvpn, the third one, using the following config, has troubles to connect:

#==============
dev tap98
port 5099
remote foobar.baz
tls-remote node0
client
persist-tun
proto udp
fragment 1300
ca /foo/my-ca.crt
cert /foo/my.crt
key /foo/my.key
key-method 2
comp-lzo
ping 15
ping-restart 60
mssfix
verb 4
mute 1
#==============

When started, the connection seems to be established, but addresses within VPN remains unreachable. After a while the connection is dropped. From command line everything works without any problems.

I'm attaching corresponding excerpt from syslog. Last line states "Bad LZO decompression header byte: 0", maybe that's the problem.

Revision history for this message
Jan Nekvasil (jan-nekvasil) wrote :
Revision history for this message
bojo42 (bojo42) wrote :

are you sure your server supports comp-lzo, as i got this error lately when i disabled LZO Compression on my server and forgot to do the same at client side. just try to turn it off at your client.

Revision history for this message
u-foka (ufooka) wrote : maybe simlar problem

Hy!

I have something simlar... but for me:
#1: udp connection over a local wifi network to access the internal lan
(works)
#2: tcp connection over the internet to reach the same internal lan (not
work)

but #2 works too when I connect directly with openvpn
and I imported the same configs into network manager as on karmic, where
that worked

Revision history for this message
u-foka (ufooka) wrote :

Hy!

This bug was reported two months before lucid release, it's a potential regression, since I used the same config with karmic smoothly! Can anyone please look at it? Now it seems that there is no hope that it can be fixed for lucid, what really annoying :S

Revision history for this message
bojo42 (bojo42) wrote :

@u-foka: your issue doesn't seem to be related to the original complaint as that was about something with the LZO compression: "Bad LZO decompression header byte: 0". Therefore please fill a new bug or find a matching one about problems with TCP connections.

@Jan: i'm setting the report to invalid assuming you have found the right configuration for LZO compression by now, if i am wrong please reopen.

Changed in network-manager-openvpn (Ubuntu):
status: New → Invalid
Jan Nekvasil (jan-nekvasil)
Changed in network-manager-openvpn (Ubuntu):
status: Invalid → New
Revision history for this message
Jan Nekvasil (jan-nekvasil) wrote :

Reopening, both server and client settings are set properly. Using ifup/down or openvpn --config works without any problems with the same config.

From syslog, using network-manager-openvpn:

WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1574', remote='link-mtu 1578'
WARNING: 'mtu-dynamic' is present in remote config but missing in local config, remote='mtu-dynamic'

Can be this the source of problem?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager-openvpn (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.