LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   openSUSE cannot connect to the internet (https://www.linuxquestions.org/questions/linux-wireless-networking-41/opensuse-cannot-connect-to-the-internet-4175449675/)

Leijssen 02-11-2013 10:06 AM
openSUSE cannot connect to the internet
 
Hello,

My laptop running openSUSE 12.2 i586 cannot load webpages, nor can it ping to google with wireless connection. However NetworkManager is up and configured, and before these connection problems occured, every webpage loaded fine.

I tested this using my home network and two public ones. Networkmanager tells I am connected to the internet, but it can't load any webpage

My ifconfig:
Code:
#at public library
THINKPAD:~ # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:0A:E4:C5:67:C7 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000                                                                                                                                     
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)                                                                                                                           
          Interrupt:16                                                                                                                                                     
                                                                                                                                                                           
eth1      Link encap:Ethernet  HWaddr 00:13:CE:FC:F8:E2                                                                                                                   
          inet addr:10.11.131.105  Bcast:10.11.131.255  Mask:255.255.255.0                                                                                                 
          inet6 addr: fe80::213:ceff:fefc:f8e2/64 Scope:Link                                                                                                               
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1                                                                                                               
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0                                                                                                               
          TX packets:67 errors:0 dropped:0 overruns:0 carrier:0                                                                                                           
          collisions:0 txqueuelen:1000                                                                                                                                     
          RX bytes:644 (644.0 b)  TX bytes:13217 (12.9 Kb)                                                                                                                 
          Interrupt:21 Base address:0xe000 Memory:b4001000-b4001fff                                                                                                       
                                                                                                                                                                           
irda0    Link encap:IrLAP  HWaddr 00:00:00:00                                                                                                                             
          NOARP  MTU:2048  Metric:1                                                                                                                                       
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0                                                                                                               
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0                                                                                                             
          collisions:0 txqueuelen:8                                                                                                                                       
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)                                                                                                                           
                                                                                                                                                                           
lo        Link encap:Local Loopback                                                                                                                                       
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:68 errors:0 dropped:0 overruns:0 frame:0
          TX packets:68 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3960 (3.8 Kb)  TX bytes:3960 (
(My first post, me noobsta)

salasi 02-11-2013 10:45 AM
You mention wireless, although there is no wireless listed (eg, wlan0), so what are you expecting to connect you to the internet, wireless or wired?

Additionally, of the two wired connections that are listed, eth1 looks to be closer to connected than eth0 (it has an ipv4 address assigned); given that it is conventional to use eth0 before eth1, just check that you aren't making incorrect assumptions about which is which somewhere. And eth1 has an ipv6 address listed; probably best to switch this off, unless you know that you can go all ipv6, as having both often leads to confusion (and by confusion, I mean something like failure to look up DNS and/or poor performance doing so, due to waiting for timeouts). I believe somewhere in Yast there is a 'turn ipv6 off' setting.

Quote:
Networkmanager tells I am connected to the internet...
Really, it doesn't. NM only knows whether you are connected to some other IP device and whether that has handed out a network address, and not whether that device has any connection to the internet. If the other device has handed out sensible looking addresses you won't be any the wiser until you try to use that remote device to connect, and then there are several errors that can occur.

When you say:

Quote:
...nor can it ping to google with wireless connection...
I don't know what you did. Did you

Code:
ping www.google.com
or something more like

Code:
ping 173.194.67.147
The second could work even if DNS is not working, and the first couldn't (dig for more information).

Leijssen 02-11-2013 11:39 AM
Quote:
Originally Posted by salasi (Post 4889197)
You mention wireless, although there is no wireless listed (eg, wlan0), so what are you expectingto connect you to the internet, wireless or wired?
Interface eth0 is wired for me, and eth1 wireless.
Quote:
I don't know what you did. Did you

Code:
ping www.google.com
or something more like

Code:
ping 173.194.67.147
The second could work even if DNS is not working, and the first couldn't (dig for more information).
I pinged google by IP adress.

Some more detail: this problem occurred since I replaced the hard drive to one with Arch on it to recover some files. After that I placed back the system recognized one. I didn't made any changed to the system configuration.


All times are GMT -5. The time now is 01:48 AM.