https://bugzilla.novell.com/show_bug.cgi?id=727857
https://bugzilla.novell.com/show_bug.cgi?id=727857#c12
Neil Rickert changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nrickert@ameritech.net
--- Comment #12 from Neil Rickert 2012-05-27 15:54:01 UTC ---
I bumped into this problem in December, and again one week ago. Both times
were while traveling (to the same place). I have not seen this problem at all
on my home network.
Here's what is going on at the network where I had the problem:
1: The network is badly setup. There seem to be two different devices on the
network that use 192.168.1.1 as their IP address. They are probably two
different routers, only one of which works. Connecting with Windows, I see the
router that works. Connecting with linux, I first see the router that doesn't
work, but after a few minutes it switches over to seeing the router that works.
I have my NetworkManager connection set as a system connection, and to
auto-connect. Most of the time this works. However, if I have first booted
Windows, and then boot to 12.1, I get the "waiting for authorization" problem.
This seems to be because Windows doesn't disconnect from the WiFi network on
shutdown, so the attempted connect from 12.1 is seen by the AP as a refresh of
an existing connection.
Note that at home, on a properly configured network, I do not have the same
problem when first booting Windows, then 12.1.
If the problem only occurs with badly configured networks, then I'm not sure
that it should really be considered a bug. However, what I have seen may be
different from what others see.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.