Bug 876431 - Booting up older kernels break VPN
Summary: Booting up older kernels break VPN
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kmod
Version: 17
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: kmod development team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-14 05:42 UTC by Alice K
Modified: 2012-11-14 12:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-14 12:50:21 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Alice K 2012-11-14 05:42:08 UTC 
Description of problem:
On booting up the newest kernel, currently   kernel-3.6.6-1.fc16.x86_64  , both the WiFi and VPN could connect successfully.

On booting older kernel, the VPN will not connect.  Thereafter, rebooting to the newest kernel will break the VPN.

The only way for both WiFi and VPN to connect successfully is to power down and then power up the Access Point and then reboot the newest kernel.




Version-Release number of selected component (if applicable):




How reproducible:
All the time.



Steps to Reproduce:
1.  Boot newest kernel.  Connect WiFi then connect VPN (success)
2.  Boot older kernel.  Connect WiFi then connect VPN (success)
3.  Boot newest kernel.  WiFi connect.  VPN fail.
4.  Power down Access Point.  Power up Access Point.  Always boot the newest kernel.  WiFi connect.  VPN connect.

  

Actual results:



Expected results:
Both WiFi and VPN should connect on booting any of its newest or older kernels.



Additional info:
The newest kernel of Fedora 16 that now automatically install, build and load kmod-wl has a similar bug.
Note You need to log in before you can comment on or make changes to this bug.