Laptop is connected to wireless router and surfing without problem.
Out of curiosity, I plugged the laptop to the wireless router using an ethernet cable. NetworkManager detected the wired connection without problem. Unplugged the ethernet cable and the wireless connection is reported as connected. However, I am not connected to the internet. After several reboot, and fiddling with Yast, NetworkManager always shows the it is connected to the wireless router but yet firefox gets no internet connection.
Q1. Anyone come across this behaviour and able to share the experience in case it comes back again in future.
Spend the entire day googling/fiddling and eventually managed to connect to the internet manually (after configuring the file wpa_supplicant.conf) using the following command in konsole as root:
however, the konsole terminal needs to stay open because the connection will break once konsole is closed.
Q2. Any advise how to get the connection manually without using root?
Note: In the process of trying to get the answers above, I’ve done too many things (within this 24 hours) to the system and out of frustration, I tried NetworkManager again and it works again… >:)
When you connected with ethernet, it setup routing via the ethernet connection. So the wireless connected, but without a default route via the wireless connection. Then, when you disconnected the ethernet, it apparently did not provide a default route for wireless.
The “route” command could have been used to fix it. However, what I would have tried is:
Disable wireless (with the NetworkManager applet).
Wait a minute or two.
Enable wireless again.
On 03/26/2012 06:26 AM, nrickert wrote:
>
> Here’s what I think happened:
>
> When you connected with ethernet, it setup routing via the ethernet
> connection. So the wireless connected, but without a default route via
> the wireless connection. Then, when you disconnected the ethernet, it
> apparently did not provide a default route for wireless.
>
> The “route” command could have been used to fix it. However, what I
> would have tried is:
> Disable wireless (with the NetworkManager applet).
> Wait a minute or two.
> Enable wireless again.
This bug is reported at https://bugzilla.novell.com/show_bug.cgi?id=732378, but
not yet fixed. I have to use ‘sudo /sbin/route add default gw xxx.xxx.xxx.xxx’
to fix. I do not think the above workaround will help.
sounds to me this problem could be the very common mistake and <not a bug>,
OP:
Are you <sure> you have <only one> active network connection at a time?
So, for example if you’re connecting using WiFi, have you <physically disconnected> your wired cable?
Or, if you’re connecting by wired cable, have you turned off your WiFi radio?
If you have multiple active network connections at once, unless you’re specially configured as a cluster or bonded network interfaces your network connectivity will be hit and miss, perhaps even dropping out periodically… The reason why is that TCP/IP is a two-way communication protocol and requires you to normally have a <single unique address> on the network. If you have multiple active network connections at once, your machine will be known on the network with a single name but multiple addresses and every time a packet is sent to the “wrong” address the packet is likely going to be dropped somewhere.
On 03/26/2012 02:56 PM, tsu2 wrote:
>
> sounds to me this problem could be the very common mistake and<not a
> bug>,
I am NOT a network noob, and it IS a bug. When one plugs in the wire with
wireless active, NM has always switched the routing to the wire. It does not in
12.2. AFAIK, that is a bug.
Not suggesting you may be a noob and maybe what you say may be true but from what I’ve seen NM doesn’t likely switch to wireless intentionally… IMO it’s more likely that the system and network will arbitrarily resolve the system’s identity based on numerous variables which won’t be consistent from one situation to another. IMO the only way you can verify what is happpening is to collect ARP packets
In any case the whole possibility can be avoided by doing what I described, just make sure only one physical connection is active at a time.
IMO
TS
Just ran into to the same problem. I changed Internet provider and router and could just connect to the router but not internet. After some try and error I looked in to /etc/resolv.conf and saw that there where a lot of random resolv.conf created. In the ordinary resolv.conf the nameserver was incorrect, but in a new file called resolv.network.conf the nameserver was correct. So I just renamed the file to resolv.conf and voila! You can always use a Live-CD of some Linux-system and try if it works. If not. It´s probably something wrong in the router.
This seems to be a bug in opensuse networkmanager. I use 12.1
its seems to bve having a problem with your network connection while you are using the wireless router.About how you write and describe your problem here, that takes a very few of your intention.first you are running with your Laptop
1, Your Laptop were connected with the wirless router, that is setting has been enabled with Lan connection ( LAN )
2, You are going to attached with ethernet cable, that settings are different then the wifi
3, Now You have to go to the Control Panel ( network and sharing center ) youo have to choose your connection that has been showing the option disabled
4, Once you will change the setting of your modem to the Ethernet Cable, that all you can go on connected with router with cable…
If that will helps you to get in with your problem…Please rate my Answer post…