Bug 565926
| Summary: | [enh] New automatic wireless connections should default to "IPv6 Ignored" | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tom London <selinux> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | astavale, dcbw, jlaska |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-06-15 16:01:57 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Tom London
2010-02-16 17:50:20 UTC
I should add that it works just fine on my "home" WLAN (uses WPA/WPA2), no PEAP, MSCHAP, etc. For completeness, when I "disconnect" (by clicking on tray icon and selecting "disconnect"), I see this in /var/log/messages: Feb 16 09:50:45 tlondon NetworkManager: <info> (wlan0): device state change: 7 -> 3 (reason 39) Feb 16 09:50:45 tlondon NetworkManager: <info> (wlan0): deactivating device (reason: 39). Feb 16 09:50:45 tlondon NetworkManager: (wlan0): canceled DHCP transaction, dhcp client pid 9638 Feb 16 09:50:45 tlondon kernel: mac80211-phy0: failed to remove key (0, 00:19:77:00:4f:f3) from hardware (-22) Feb 16 09:50:46 tlondon NetworkManager: <info> Policy set 'System eth0' (eth0) as default for routing and DNS. What is the IPv6 configuration "method" from the IPv6 tab of the editor window for your network in nm-connection-editor? Or right-click the applet icon, and choose "Edit connections...". Edit Connections->Wireless, then Edit this network, then IPv6 settings tab: Method says "Automatic" Hmmm... changing method to "Ignore" allows NM to complete...
wlan0 Link encap:Ethernet HWaddr 00:21:5D:AC:C6:92
inet addr:10.11.14.143 Bcast:10.11.14.255 Mask:255.255.255.0
inet6 addr: fe80::221:5dff:feac:c692/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1727 errors:0 dropped:0 overruns:0 frame:0
TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:198346 (193.6 KiB) TX bytes:8540 (8.3 KiB)
Automatic waits for IPv6 Router Advertisements, so it'll spin until either it times out, or gets a router advertisement. Is the network IPv6 enabled? Perhaps for now we should default new connections to IPv6=Ignore No, the WLAN is not IPv6 enabled. Checking with IT if it can be enabled. Works at home with my old Linksys..... Checking the setting for my "home" WLAN, it is already set at "Ignore". Is there something in the access point that negotiates this? No, it's completely in the configuration on your machine. But it may be that new connections (when you click on an AP from the menu) get IPv6 set to "automatic" by default, but your existing connections may have it set to Ignored already. I forget what the default behavior is. So, what's the bug here? Should we make this an enhancement request to set IPv6's method to "ignored" when a new automatic connection is created (like clicking in the menu)? Guessing that defaulting to "Ignored" will minimize the "surprise factor", certainly. Could certainly make this complicated by engaging in a dialog, I suppose, but that would probably cause even more confusion. I have my IT guy finding out how/if our APs can be IPv6 enabled, but our internal corporate LAN is IPv4 only. In any case, I'll follow your suggestion to change this to an enhancement request ..... [Sorry if I didn't do this right...] Wondering if this could become a "common issue" that would benefit from some release notice..... *** Bug 569192 has been marked as a duplicate of this bug. *** I believe this issue may also be affecting installs (both manual and kickstart). See bug#567978. This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This should be long-fixed. New connections have IPv6 'ignored' by default, but even if they weren't, IPv6 is (by default) allowed to fail and you'll still be connected if IPv4 is successful. |