[opensuse] No Internet access after processor upgrade
Opensuse list, I'm using openSUSE 12.1 (64 bit); KDE 4.7.2 I just upgraded the motherboard and processor to: ASUS Sabertooth 990FX R2.0 - motherboard AMD FX -8120 Processor Nvidia GeForce GT 610 Graphics card The system boots fine. Its connected via the ethernet to a local cisco router that has internet access. I can log into the router at 192.168.1.1 and access all of the router functions, so it would seem the network card, drivers, etc. are all functioning. For some reason, web browsers will connect to all the LAN devices (router, printer, scanner) but will not connect to WAN. I disabled the firewall. I checked the etc/resolv.conf file and it seems to be correctly writing 192.168.1.1 as the nameserver and 209.18.47.61 and 62 as the DNS entries. any ideas are appreciated, thanks, Regis -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
rm@crescentconstruction.com wrote:
Opensuse list,
I'm using openSUSE 12.1 (64 bit); KDE 4.7.2
I just upgraded the motherboard and processor to: ASUS Sabertooth 990FX R2.0 - motherboard AMD FX -8120 Processor Nvidia GeForce GT 610 Graphics card
The system boots fine.
Its connected via the ethernet to a local cisco router that has internet access.
I can log into the router at 192.168.1.1 and access all of the router functions, so it would seem the network card, drivers, etc. are all functioning.
For some reason, web browsers will connect to all the LAN devices (router, printer, scanner) but will not connect to WAN.
I disabled the firewall.
I checked the etc/resolv.conf file and it seems to be correctly writing 192.168.1.1 as the nameserver and 209.18.47.61 and 62 as the DNS entries.
any ideas are appreciated,
Can you connect to web sites using just the IP address? If not, it may be a routing issue. Have you configured the default route? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
rm@crescentconstruction.com wrote:
Opensuse list,
I'm using openSUSE 12.1 (64 bit); KDE 4.7.2
I just upgraded the motherboard and processor to: ASUS Sabertooth 990FX R2.0 - motherboard AMD FX -8120 Processor Nvidia GeForce GT 610 Graphics card
The system boots fine.
Its connected via the ethernet to a local cisco router that has internet access.
I can log into the router at 192.168.1.1 and access all of the router functions, so it would seem the network card, drivers, etc. are all functioning.
For some reason, web browsers will connect to all the LAN devices (router, printer, scanner) but will not connect to WAN.
I disabled the firewall.
I checked the etc/resolv.conf file and it seems to be correctly writing 192.168.1.1 as the nameserver and 209.18.47.61 and 62 as the DNS entries.
any ideas are appreciated,
Can you connect to web sites using just the IP address? If not, it may be a routing issue. Have you configured the default route?
--
I can't connect using the IP address. I've not configured a "default route". I've gone into YAST and set the network interface card to DHCP, but nothing else. thanks, Regis -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
rm@crescentconstruction.com wrote:
I can't connect using the IP address.
I've not configured a "default route". I've gone into YAST and set the network interface card to DHCP, but nothing else.
Do you have a DHCP server on the network? Is it properly configured? What happens if you manually configure the default route? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
rm@crescentconstruction.com wrote:
I've not configured a "default route". I've gone into YAST and set the network interface card to DHCP, but nothing else.
What does the command "ip route" show? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
rm@crescentconstruction.com wrote:
I've not configured a "default route". I've gone into YAST and set the network interface card to DHCP, but nothing else.
What does the command "ip route" show? --
The results of ip route are: #ip route 127.0.0.0/8 dev lo scope link 169.254.0.0/16 dev etho scope link 192.168.1.0/24 dev etho proto kernel scope link src 192.168.1.143 and there is a dhcp server in the cisco router. several other devices are connected. thanks, Regis -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
rm@crescentconstruction.com wrote:
127.0.0.0/8 dev lo scope link 169.254.0.0/16 dev etho scope link 192.168.1.0/24 dev etho proto kernel scope link src 192.168.1.143
and there is a dhcp server in the cisco router. several other devices are connected.
You do not have a default route, which means you cannot get to the Internet. You should have a line similar to this, but with the appropriate address: default via 172.16.1.1 dev eth0 I don't know why you're not getting the correct info from the Cisco router. Without looking at the traffic, I couldn't even guess. You may have to use manual configuration until you get this problem resolved. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
rm@crescentconstruction.com wrote:
127.0.0.0/8 dev lo scope link 169.254.0.0/16 dev etho scope link 192.168.1.0/24 dev etho proto kernel scope link src 192.168.1.143
and there is a dhcp server in the cisco router. several other devices are connected.
You do not have a default route, which means you cannot get to the Internet. You should have a line similar to this, but with the appropriate address: default via 172.16.1.1 dev eth0
I don't know why you're not getting the correct info from the Cisco router. Without looking at the traffic, I couldn't even guess.
You may have to use manual configuration until you get this problem resolved.
Thanks for pointing me in the right direction. I thought the routing looked odd, but I'm far from a network expert. I changed the default route by doing: # route add default gw 192.168.1.1 and now it connects just fine. I probably could have changed the default gateway via YAST also - but the command line worked fine. thanks to both of you, Regis
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 18/08/13 15:54, rm@crescentconstruction.com escribió:
rm@crescentconstruction.com wrote:
I've not configured a "default route". I've gone into YAST and set the network interface card to DHCP, but nothing else.
What does the command "ip route" show? --
The results of ip route are:
#ip route 127.0.0.0/8 dev lo scope link 169.254.0.0/16 dev etho scope link 192.168.1.0/24 dev etho proto kernel scope link src 192.168.1.143
and there is a dhcp server in the cisco router. several other devices are connected.
You do not have a default route, you have a misconfigured network card. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
You do not have a default route, you have a misconfigured network card.
If DHCP is used, then the default route should be provided. For some reason it's not. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/18/2013 04:06 PM, James Knott pecked at the keyboard and wrote:
Cristian Rodríguez wrote:
You do not have a default route, you have a misconfigured network card.
If DHCP is used, then the default route should be provided. For some reason it's not.
You need to get this resolved because the next time you boot you will be right back to having no default route. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 2013-08-18 at 19:20 -0400, Ken Schneider - openSUSE wrote:
On 08/18/2013 04:06 PM, James Knott pecked at the keyboard and wrote:
Cristian Rodríguez wrote:
You do not have a default route, you have a misconfigured network card.
If DHCP is used, then the default route should be provided. For some reason it's not.
Hi Guess: it's knocked out NetworkManager? Yast > Network Devices > Network Settings > Global options > Change Default Route via DHCP -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
lynn wrote:
Hi Guess: it's knocked out NetworkManager? Yast > Network Devices > Network Settings > Global options > Change Default Route via DHCP
I don't know if he's using NetworkManager, but if configuring DHCP in Yast, that is an option he should check. IIRC, if NetworkManager is used, the Yast settings are not used. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 18 Aug 2013 13:59:40 -0500 rm@crescentconstruction.com wrote:
I just upgraded the motherboard and processor to: ASUS Sabertooth 990FX R2.0 - motherboard AMD FX -8120 Processor Nvidia GeForce GT 610 Graphics card
I just went through a similar experience. I think there's a bug here, but I did not report because (a) I won't be able to test a fix, and (b) it is an unsupported configuration, so would probably be closed with WONTFIX. Let me describe what happened. 1: My desktop died - seems to be a power supply failure, but the box was a lemon anyway. 2: I took the hard drive out, and installed in another computer (intended as a replacement). The system booted up fine to opensuse. However, I could not get Internet. I could connect to the local router, but could not get out. Does that sound familiar? Manually adding a route with the "route" command fixed it. But apparently, that would be needed at each boot (I could automate if needed). The system was configured to use "ifup" settings. I went through the settings, and made sure that the ethernet card (device p5p1) was set to be used, and all other devices were set to never be used. I went into the Yast network device route settings, and made sure that the route was added for the working ethernet device. The only thing that ever worked was my manual "route add" command. The standard network setup wanted to always run the default route through the "eth0" device, which no longer existed. So, again in Yast network settings, I told it to delete "eth0". And that completely solved the problem. That also deleted the default route that I had configured through device p5p1, which was fine since the DHCP configured route was working. It seems that the Yast "ifup" settings are confused by a non-existent device. I hope this helps. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2013-08-18 at 19:03 -0500, Neil Rickert wrote:
So, again in Yast network settings, I told it to delete "eth0". And that completely solved the problem. That also deleted the default route that I had configured through device p5p1, which was fine since the DHCP configured route was working. It seems that the Yast "ifup" settings are confused by a non-existent device.
Similar problem in my laptop. Eth is configured "on cable connect", but in fact it is active after booting. This confuses things, because packages that should be routed via wlan0 are not. I have to run "rcnetwork stop eth0" after every boot, and then things work. I can not report bug because it is running 11.4 Evergreen. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlIRYn8ACgkQtTMYHG2NR9VmugCeK58+96oBRs3pDK2kAUOkCR9f 9UcAoIvLERlM3wk+X9uLS335s71Zq9ho =9P6d -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Carlos E. R. -
Cristian Rodríguez -
James Knott -
Ken Schneider - openSUSE -
lynn -
Neil Rickert -
rm＠crescentconstruction.com