On 14/04/16 01:13, sdm wrote:
What I found is that if I switch Wicked to DHCP, I can unplug the router all day long, plugging it back in and it's fine. If I setup a static route, no dice. I also noticed that YaST2 networking settings didn't write a nameserver to /etc/resolv.conf, that I either have to enter manually or NetworkManager will auto generate one. Is the user supposed to know to add their nameserver to /etc/resolv.conf or is there something in the YaST2 Network Settings Wicked setup that writes the name server to that file? When I entered the Name Server on the Hostname/DNS tab, nothing ever gets written to /etc/resolv.conf, so I did some tests and tried to get YaST2 to write to /etc/resolv.conf after clearing out the entire file (cleared all characters) and it doesn't. So if I specify the Name Server on the Hostname/DNS tab, I can't properly access web pages.
This all touches on what I mentioned in my own recent post to which you contributed. I did a fresh install of Leap 42.1 on a brand new machine, simply choosing the KDE desktop and accepting all defaults other than my own preferred partioning and formatting. Being a wired connection it was detected during installation and I went with the default Wicked setup. I forget whether I changed to a static IP during or after installation, I assume after. The setup I was left with seemed somewhat broken, but it took me so much fiddling over so many days to get a grasp on where the problem might lie, and not being over familiar until then with network configuration files I didn't have the knowledge or info to file a bug report. Now your report seems to confirm something is amiss, although I wonder if, with all the updates to Leap, a new install + updates now would generate the same issue. The resolv.conf file didn't contain the right details and entering them in YaST fails to insert them, even though I'd added name servers and the default IPv4 gateway within the Network Settings dialogs. No routes file is generated in /etc/sysconfig/network. I supposed at the time that Wicked used some other configuration and these details weren't necessary. Following the install and basic setup, I found accessing websites was unusually slow with a delay of sometimes many seconds loading each page. For a brand new quad core machine with 8GB or RAM, no other apps running, root on an NVMe drive, etc. this was clearly not right, and the old decommissioned P4 machine along with my ageing laptop going via the same router's wifi were experiencing no such delays. The problem persisted until my most recent visit. It remains to be seen after the recent fiasco and replacement of the router, and reconfiguration of the network settings, whether the delay issue is resolved. I'm not there to test in person. gumb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org