https://bugzilla.redhat.com/show_bug.cgi?id=876431
Bug ID: 876431
QA Contact: extras-qa(a)fedoraproject.org
Severity: high
Version: 17
Priority: unspecified
CC: jonathan(a)jonmasters.org,
kmod-maint(a)lists.fedoraproject.org, msivak(a)redhat.com
Assignee: kmod-maint(a)lists.fedoraproject.org
Summary: Booting up older kernels break VPN
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: alice_knoll_drouin(a)yahoo.com
Type: Bug
Documentation: ---
Hardware: x86_64
Mount Type: ---
Status: NEW
Component: kmod
Product: Fedora
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.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.