On Sun, 11 Jan 2015 04:53, Carl Hartung
Hi All,
I installed 13.2 today on my laptop while the same wired network was plugged in that I use every day. The network wasn't properly detected, or at least it wasn't properly configured during installation, because adding the online repositories and downloading updates failed.
After booting the installed system, it still does not work properly. I can connect to the router (192.168.1.1) but not to the Internet.
The same holds true for the wireless connection if I enable it. The router passphrase prompt appears but the system can't connect to the Internet after I enter it.
For the record, this system has had Vista64, openSUSE 12.3 and Mint 17 installed in parallel up to today and this network connection in all three cases has always 'just worked.' This leads me to believe that the problem is unique to the 13.2 installer.
I realize I could probably go 'tinkering under the hood' to make it work, but I'd prefer that the system stays 'stock' as much as possible and to make it work using either the regular installation or desktop tools if I can. Towards that end, does anyone know of a way to access the network detection and configuration routines during installation to see what's going on and influence it?
All ideas and advice will be gratefully appreciated.
TIA & regards,
Carl
Hmm, it would not be the first time that most of the network is set up e.g. reachable router (same subnet) but no reach beyond that. In most cases the 'default route' is missing or wrong. The output of the command "ip route show" should be something like this: default via 192.168.1.1 dev eth0 127.0.0.0/8 dev lo scope link 169.254.0.0/16 dev eth0 scope link 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.100 The first line shows the 'default' route, on my box the ethernet connector has the name 'eth0', change that to what is shown on your box. My box was given the ip '192.168.1.100', change that to your config. The command to add a default route by hand as root would be: "ip route add default via 192.168.1.1 dev eth0" If you are using dhcp, check the file /etc/sysconfig/network/dhcp for the entry 'DHCLIENT_SET_DEFAULT_ROUTE="yes"', at least it should say "yes" for a fully functional router. IMHO, yast boinked at the default route setting, or dchp gave parameters that where not useable. To shed light into that, see "man 8 dhcpcd" and there should be a file "/var/lib/dhcpcd/dhcpcd-<interface>.info" which holds all the info the dhcp client gets from the router as shell variables. I hope this gives some help - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org