Bug 465780 - LZO Compression
LZO Compression
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: NetworkManager-openvpn (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-06 08:21 EDT by Luke Sheldrick
Modified: 2009-05-20 16:25 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-05-20 16:24:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Luke Sheldrick 2008-10-06 08:21:00 EDT
Description of problem:
If I use the nm-applet to configure my openvpn settings, if I deselect use LZO compression, and click ok, the setting doesn't get changed in the conf. Going back into advanced options, will reveal it still to be selected. 

Also if I run nm-applet from the console, every time I go into the settings of the VPN, it verbose log's :

"** (nm-connection-editor:6306): WARNING **: Invalid setting VPN: ca"

a number of times. 

Version-Release number of selected component (if applicable):
NetworkManager.i386                      1:0.7.0-0.11.svn4022.4 installed       
NetworkManager-glib.i386                 1:0.7.0-0.11.svn4022.4 installed       
NetworkManager-gnome.i386                1:0.7.0-0.11.svn4022.4 installed       
NetworkManager-openvpn.i386              1:0.7.0-16.svn4027.fc9 installed       

How reproducible:
Install & Test.

Steps to Reproduce:
1. Install above versions
2. Setup an openvpn connection with LZO
3. Try to remove LZO
  
Actual results:
VPN trys to initiate with LZO, cannot communicate.

Expected results:
No LZO in conf

Additional info:
Comment 1 Luke Sheldrick 2009-05-20 16:24:51 EDT
Closing, no longer an issue
Comment 2 Luke Sheldrick 2009-05-20 16:25:21 EDT
Closing, no longer an issue

Note You need to log in before you can comment on or make changes to this bug.