Mailinglist Archive: opensuse (878 mails)

< Previous Next >
[opensuse] 13.1 - Cannot Connect to Wireless AP w/o Killing Network Manager, resolve.conf not updating on return???
All,

Spent the last week on a "family trip" (not vacation), and had to connect to a wireless access point. No matter what I did, network manager could not connect to this access point. My phone had no issue connecting, but 13.1 could not connect.

Using my phone I found:

https://en.opensuse.org/SDB:WiFi

and

https://en.opensuse.org/SDB:Tracking_down_wireless_problems

Which includes at the beginning:

<quote>
openSUSE may occasionally encounter issues with wireless. In most cases, it will work fine with networks or WEP/WPA-secured wireless networks. However, for public wireless networks, specifically one's that are set up in coffee shops and airports, NetworkManager would suddenly ignore any attempts to connect to a network or refuse to get an IP address.
</quote>

This is exactly what was happening. I could see and list all available AP's with iwlist. I could manually associate the AP with my wireless connection with iwconfig, but could not actually connect to the AP. As soon as I killed network manager with rcnetwork stop, and brought wpa_supplicant back up, BINGO, the connection to the AP was automatic. Issuing the dhcpcd command obtained an address and the network was up.

Apparently this has been a know issue since the 12.X days. Other than documenting the issue, has there been an progress on a consistent work-around that will allow NetwokManager to work when this problem is encountered?

Upon return from the trip, a nasty side effect of the manual connection and issuance of the dhcpcd command was discovered when I connected to my AP, but had no domain information and no name service. Checking, resolv.conf was left in the state it was autoconfigured to with the vacation AP. For some reason when re-connecting to my home AP, resolv.conf was not updated. The same was true for the domain information. While those are easily resolved by setting them again, I am used to the domain information automatically updating.

Is there anything specific anyone can think of in this situation that would result in the normal resolve.conf and domain information to fail to update?

All thoughts and ideas are appreciated.

--
David C. Rankin, J.D.,P.E.
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups