Op woensdag 13 april 2016 16:13:37 CEST schreef sdm:
On 04/13/2016 03:57 PM, James Knott wrote:
On 04/13/2016 06:31 PM, Freek de Kruijf wrote:
This is the culprit. You have to provide an IP address for the DNS also. With DHCP, you get also the value for the DNS. With a static address you do not get this address, so you have to provide that address with the other static values.
DNS only maps a name to an IP address. You don't even need it, if you just use IP addresses. So, it shouldn't cause an interface to lose a configured static address.
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.
For a static IP address, proper networking + internet connection NEED DNS('s) and a gateway ( to the external network behind the router ). When using Networkmanager one has some intermediate options ( static IP, DNS's obtained from the router ), but not so using wicked. A thing I've seen a couple of times now, is routers that are able to hand out fixed IP's for certain MAC addresses, in some occasions advertised in the interface as "static configuration", which IMHO is at least confusing if not completely wrong. On two occasions the owner had the impression the configuration needed to be done on both local machine and the router, doing so wanted to make sure he did not miss any configuration, so applied a static IP on the local machine. Somehow the router would not accept the connection as if it was failing to hand out an IP that was already in use, yet to the same machine. Removing the fixed IP entry from the router solved it. Another thing I've seen is machines with static IP that borked an entire network because they used an IP in de DHCP range. My personal policy here is to reserve the first 50 IP addresses for static usage, and DHCP starting from at x.x.x.51, use Google's DNS's 8.8.8.8 and 8.8.4.4 ( or an "own" DNS ). Just tested: Setting wicked to use a static IP address, whilst at the same time entering Google's DNS's, the router's IP address as the gateway, does write these to /etc/resolv.conf. Both on Leap and TW. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org