[opensuse] Internet inaccessible, both during and after a fresh 13.2 installation
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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-11 04:53, Carl Hartung wrote:
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.
Well, that points to to possible causes: routing or dns. If you can ping 8.8.8.8, but not "google.com", the problem is DNS. Otherwise, it is routing. Find out which, then we can try find out why and/or what to do. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. composed on 2015-01-11 05:35 (UTC+0100):
On 2015-01-11 04:53 -0500, Carl Hartung wrote:
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
Well, that points to to possible causes: routing or dns.
If you can ping 8.8.8.8, but not "google.com", the problem is DNS. Otherwise, it is routing.
Find out which, then we can try find out why and/or what to do.
All my own installations use fixed IP, so I don't know if this will be of any use if you use DHCP, but my most recent 13.2 installation has the route/gateway set in /etc/sysconfig/network/ifroute-eth0. Maybe creating it if you don't have it, or yours doesn't contain 192.168.1.1 will get you going: default 192.168.1.1 - eth0 Substitute whatever name ifconfig reports for your NIC if it or the filename is not ending with eth0. If yours is not eth0 and you want it to be eth0, add to your grub stanza: net.ifnames=0 That might not be enough (I'm not that familiar with Wicked), but it's a start. http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... provides more detail. For troubleshooting 13.2's Wicked, take a look at: https://en.opensuse.org/Portal:Wicked If it's not enough help, we need to get it improved. ('tis a Wiki) When trying a reinstall, you can preconfigure networking via the cmdline: https://en.opensuse.org/SDB:Linuxrc#Network_Config
...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?
During installation, basic cmdline networking tools can be used on tty2. The first I'd probably try because of your symptoms is 'route -n'. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Sat, 10 Jan 2015 22:53:43 -0500
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.
What show netstat -rn cat /etc/resolv.conf
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.
Ditto.
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 have no problem connecting to Internet using 13.2 (of course as long as provider functions correctly :p ) or installing it from Internet using NET image using wired interface. So whatever problem there is it does not look like universal one.
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
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/01/15 14:53, Carl Hartung wrote:
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. [pruned]
I have had no troubles with INSTALLING 13.2 on either the laptop (ThinkPad) or the desktop - and both were done using wired network. (Had some hassles with 13.2 AFTER installation but nothing to do with networking. #) After installing it on the laptop the wi-fi worked perfectly and the system was updated with all the latest using zypper. You state that you did a clean install of 13.2 but you don't mention what you used for this install: was it the DVD or the KDE Live disc (or an upgrade from 13.1)? (#) I have now installed/re-installed 13.2 on at least 4 occasions and have not had the networking hassle you mention. But I am installing from the "Gold" DVD release. BC -- Using openSUSE 13.2, KDE 4.14.3 & kernel 3.18.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 11 Jan 2015 18:02:05 +1100 Basil Chupin wrote: 8< - - - - - snipped - - - - - >8
You state that you did a clean install of 13.2 but you don't mention what you used for this install: was it the DVD or the KDE Live disc (or an upgrade from 13.1)?
8< - - - - - snipped - - - - - >8 Hi, Basil, Thank you and Happy New Year! I downloaded the final DVD image, verified it's md5sum and ran a media check before installing. regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
Thank you to everybody for your extremely helpful responses! I'm short on time this weekend so I backed up 13.2 and restored 12.3. I'll report back what I find when I continue next weekend. Just to clarify one thing: I only find it mysterious that this network connection is discovered and 'just works' in Vista64, openSUSE 12.3 and Mint 17 but emerges broken when installing and running 13.2. It isn't that I think 13.2 is completely broken in this regard, but clearly there's something unusual happening and I'd like to find out what it is. Thanks again! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 11/01/2015 10:52, Carl Hartung a écrit :
Just to clarify one thing: I only find it mysterious that this network connection is discovered and 'just works' in Vista64, openSUSE 12.3 and Mint 17 but emerges broken when installing and running 13.2. It isn't that I think 13.2 is completely broken in this regard, but clearly there's something unusual happening and I'd like to find out what it is.
the simpler is to test a 13.2 live cd jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 11 Jan 2015 10:54:24 +0100 jdd jdd wrote:
the simpler is to test a 13.2 live cd
That's a great suggestion, jdd. Thank you! And if it boots and the network 'just works' I can compare the configurations for clues. :-) Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Il 11/01/2015 08:03, Carl Hartung ha scritto:
On Sun, 11 Jan 2015 10:54:24 +0100 jdd jdd wrote:
the simpler is to test a 13.2 live cd
That's a great suggestion, jdd. Thank you! And if it boots and the network 'just works' I can compare the configurations for clues. :-)
Carl
I have had not any networking troubles upgrading from 13.1 to 13.2. I think a thing which could have changed and not upgraded accordingly into your box is the interface name. My former *eth0* changed "inexplicably" into *enp5s0* for example. Then all the suggested checks by other list-members have to be associated to the correct updated interface name: marco@linux-turion64:~> ip route show default via 192.168.1.1 dev enp5s0 proto static metric 1024 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.3 ifconfig -a enp5s0 Link encap:Ethernet HWaddr E8:9A:8F:32:F8:54 inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::ea9a:8fff:fe32:f854/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9542 errors:0 dropped:0 overruns:0 frame:0 TX packets:7526 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11840573 (11.2 Mb) TX bytes:703824 (687.3 Kb) Cheers, -- Marco Calistri opensuse 13.2 (Harlequin) 64 bit - Kernel 3.17.2-5.g5caf82d-default Gnome 3.14.1 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 11 Jan 2015 10:47:40 -0200 Marco Calistri wrote:
Il 11/01/2015 08:03, Carl Hartung ha scritto:
On Sun, 11 Jan 2015 10:54:24 +0100 jdd jdd wrote:
the simpler is to test a 13.2 live cd
That's a great suggestion, jdd. Thank you! And if it boots and the network 'just works' I can compare the configurations for clues. :-)
Carl
I have had not any networking troubles upgrading from 13.1 to 13.2.
I think a thing which could have changed and not upgraded accordingly into your box is the interface name.
My former *eth0* changed "inexplicably" into *enp5s0* for example.
Then all the suggested checks by other list-members have to be associated to the correct updated interface name:
marco@linux-turion64:~> ip route show
default via 192.168.1.1 dev enp5s0 proto static metric 1024 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.3
ifconfig -a
enp5s0 Link encap:Ethernet HWaddr E8:9A:8F:32:F8:54 inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::ea9a:8fff:fe32:f854/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9542 errors:0 dropped:0 overruns:0 frame:0 TX packets:7526 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11840573 (11.2 Mb) TX bytes:703824 (687.3 Kb)
Cheers,
Thanks Marco! I'd forgotten about the interface names being changed. It's a clean, 'from scratch' 13.2 installation, so it must be using them. I'll take that into account when I resume my debugging next weekend. (I've restored my 12.3 system in the interim.) regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/01/15 02:13, Carl Hartung wrote:
I'd forgotten about the interface names being changed. It's a clean, 'from scratch' 13.2 installation, so it must be using them. I'll take that into account when I resume my debugging next weekend. (I've restored my 12.3 system in the interim.)
I for one will be very interested in what you find out! I've done three fresh installations (not upgrades) of 13.2 here, all from full DVD - two on static-address machines in a small wired home LAN, and one on a gateway machine which has two NICs, one with a static address on the same internal LAN and the other pointing at a broadband modem using DHCP. In all three cases I had difficulties with setting up a working Internet connection. None of the machines would connect to the Internet during installation. Then, after installation, it took prolonged futzing around with "wicked" and "NetworkManager" to get an external connection working in each case, and at such a frustration level that I really have no idea what it was I actually did to turn the key. All I can say is that, highly subjectively, it seems to me that the implementation of "wicked" as a replacement for "ifup" has some way to go; and/or that "wicked" and "NetworkManager" seemed to get in each other's way. -- Robin K Wellington "Harbour City" New Zealand -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 12 Jan 2015 09:49:59 +1300 Robin Klitscher wrote:
On 12/01/15 02:13, Carl Hartung wrote:
I'd forgotten about the interface names being changed. It's a clean, 'from scratch' 13.2 installation, so it must be using them. I'll take that into account when I resume my debugging next weekend. (I've restored my 12.3 system in the interim.)
I for one will be very interested in what you find out!
I've done three fresh installations (not upgrades) of 13.2 here, all from full DVD - two on static-address machines in a small wired home LAN, and one on a gateway machine which has two NICs, one with a static address on the same internal LAN and the other pointing at a broadband modem using DHCP.
In all three cases I had difficulties with setting up a working Internet connection. None of the machines would connect to the Internet during installation. Then, after installation, it took prolonged futzing around with "wicked" and "NetworkManager" to get an external connection working in each case, and at such a frustration level that I really have no idea what it was I actually did to turn the key. All I can say is that, highly subjectively, it seems to me that the implementation of "wicked" as a replacement for "ifup" has some way to go; and/or that "wicked" and "NetworkManager" seemed to get in each other's way.
Hi Robin, I'm certainly not happy that you've experienced the same problem, but it helps to know this system isn't the only one being affected. I'll post back next weekend, when it's sorted out and if I find anything new and interesting to report. regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/10/2015 10:53 PM, Carl Hartung wrote:
I can connect to the router (192.168.1.1) but not to the Internet.
What do you mean by 'connect'? * You can ping that address from the device? * You can set up a HTML session to the router's management interface * you can set up a ssh/telnet session to the router's CLI management interface Well, fine, that means you don't have a local network problem. 1. Maybe your device doesn't know to _use_ the router as a gateway * use 'netstat' or 'route' to find out that. # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 enp0s25 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s25 The "G" in the Flags field indicates that this route is the gateway. 2. Maybe your router isn't connecting to the your ISP and hence the Internet. 3. Maybe your router has an ACL setting that is rejecting your device or your LAN
The router passphrase prompt appears but the system can't connect to the Internet after I enter it.
I must admit the wording there puzzles me. The only time I have to supply a password when connecting to my router is when I ad accessing it in admin mode to alter the configuration. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 11 Jan 2015 09:41:53 -0500 Anton Aylward wrote:
What do you mean by 'connect'?
Hi Anton, Thank you for your interest and feedback. I apologize if my language was ambiguous. I can sign into the router's web-based management portal but not browse the Internet. I have many leads and suggestions to follow when I get back to the problem next weekend. Thanks again! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/11/2015 11:50 AM, Carl Hartung wrote:
I can sign into the router's web-based management portal but not browse the Internet.
I presume from that you mean you cannot access the internet at large by any means, ping, traceroute, telnet, ssh, netcat, nmap - nothing! - from absolutely *ANY* device on your LAN, that is on the nearside of your router. "Browse" I would take to mean access, using first DNS resolution to get the IP address, using a "browser" such as Firefox. That's why an earlier post about the difference between trying to access a site by its name vs its IP address google-public-dns-a.google.com vs 8.8.8.8 for example is important. If all you can do is access the web based management port, if all those other protocol won't "let you out", then you do not have a problem with openSuse 13.2, you have a problem with your router. If that is the case, then really its an issue you have to resolve with your ISP. I rent my router from my cable provider and if anything goes wrong its their responsibility to fix it, and that includes replacing a failed router. You might start by power cycling the router; turn it of for long enough that any capacitors in the power circuits discharge, at least 30 seconds. Accessing the management port you should be able to see what kind of connection you have with your ISP, what your DNS settings there are, and of course what your local LAN is configured as, both its IP subnet and if local DHCP is uprating and what addresses it has assigned. Although I have my desktop and server using static addresses outside the router's DHCP block, all my wifi devices (and yes that include guests and visitors) make use of DHCP. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 11 Jan 2015 14:09:32 -0500 Anton Aylward wrote: 8< - - - - - snipped - - - - - >8
I presume from that you mean ... 8< - - - - - snipped - - - - - >8 "Browse" I would take to mean ... 8< - - - - - snipped - - - - - >8
You're making an important point, Anton, and I do appreciate it, but my language wasn't totally incomprehensible. :-) My first test is always to see if the browser can reach the Internet. This is because I take port 80 on this router being open to all connected* clients as a given, and it's an easy test. If that fails, the next test is to try reaching the router's management portal. If I can sign in, then I can confirm that the router is 'visible' and 'up' with a public IP address on the WAN side. I can also inspect and confirm the LAN settings and parameters. If both tests fail, then of course I switch to command line tools. (*) "Connected" means literally being attached through standard Ethernet cabling and hardware (in my case, through a switch.) In the wireless context, it means being prompted to supply the router's WPA2/PSK passphrase. Thanks again & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/11/2015 06:44 PM, Carl Hartung wrote:
You're making an important point, Anton, and I do appreciate it, but my language wasn't totally incomprehensible. :-)
My experience with phone and email debugging, and I think from what I've seen others here say, is that its quite easy to mis-interpret what people say. It helps to be reductionist in detailing technical matters and clarify we are both making the same assumptions.
From my DatabaseofDotSigQuotes:
“I know that you believe you understand what you think I said, but I'm not sure you realize that what you heard is not what I meant.” -- Robert McCloskey -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 11 Jan 2015 19:37:57 -0500 Anton Aylward wrote:
On 01/11/2015 06:44 PM, Carl Hartung wrote:
You're making an important point, Anton, and I do appreciate it, but my language wasn't totally incomprehensible. :-)
My experience with phone and email debugging, and I think from what I've seen others here say, is that its quite easy to mis-interpret what people say. It helps to be reductionist in detailing technical matters and clarify we are both making the same assumptions.
From my DatabaseofDotSigQuotes:
“I know that you believe you understand what you think I said, but I'm not sure you realize that what you heard is not what I meant.” -- Robert McCloskey
That's a great quote, Anton, and apropos. Again, I do greatly appreciate your feedback. As jdd suggested, next weekend, I'll boot a Live CD and see if the network 'just works.' If it does, I'll try replicating that configuration in the installed version. Thanks again! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carl Hartung composed on 2015-01-11 20:38 (UTC-0500):
As jdd suggested, next weekend, I'll boot a Live CD and see if the network 'just works.' If it does, I'll try replicating that configuration in the installed version.
As yamaban noted upthread, network configuration niggles depend on the method of configuration used. You've not mentioned that I recall whether you're using fixed IP or DHCP. Fixed IP seems not to have the niggles. AFAIK, live media defaults to DHCP. On a simple home LAN either is OK, but the virtues of DHCP on a home LAN are pretty much absent. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 11 Jan 2015 21:14:38 -0500 Felix Miata wrote:
Carl Hartung composed on 2015-01-11 20:38 (UTC-0500):
As jdd suggested, next weekend, I'll boot a Live CD and see if the network 'just works.' If it does, I'll try replicating that configuration in the installed version.
As yamaban noted upthread, network configuration niggles depend on the method of configuration used. You've not mentioned that I recall whether you're using fixed IP or DHCP. Fixed IP seems not to have the niggles. AFAIK, live media defaults to DHCP. On a simple home LAN either is OK, but the virtues of DHCP on a home LAN are pretty much absent.
Hi All, I apologize for the 'noise.' The only difference I found in the network configurations between 12.3, 13.2 and 13.2 KDE Live here was the addition in 12.3 of Google's public IPv4 nameservers in /etc/resolve.conf: nameserver 8.8.8.8 nameserver 8.8.4.4 As soon as I added these in 13.2 and restarted the network connection, the Internet became accessible. I vaguely recall adding these back when DNS lookups were getting slow and flaky and I didn't have time to find out if it was actually my ISP's nameservers or something in the router. Obviously, whatever it was has gotten much worse (meaning broken) since then, so it wasn't at all 13.2's fault, after all. Thanks to everyone again for their input. Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (11)
-
Andrei Borzenkov -
Anton Aylward -
Basil Chupin -
Carl Hartung -
Carlos E. R. -
Felix Miata -
James Knott -
jdd -
Marco Calistri -
Robin Klitscher -
Yamaban