Op woensdag 13 april 2016 16:13:37 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.
In YaST when configuring a static address for an interface you have to provide the static address, the netmask, the IP address of the default route and the IP address of the DNS. The first two end up in the file ifcfg..., the default route in the file route and the IP address of the DNS in the file config. When starting the network the system enters the DNS value in resolv.conf. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org