On 04/14/2016 12:27 AM, Knurpht - Gertjan Lettink wrote:
Op woensdag 13 april 2016 16:35:39 CEST schreef sdm:
On 04/13/2016 04:29 PM, gumb wrote:
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. This is Tumbleweed, latest snapshot, just for the record. If I entered a name server in YaST2 Network Settings on the Hostname/DNS tab and it wrote that somewhere else, DNS won't work properly until I add the name server to /etc/resolv.conf. So either I'm doing something wrong and missing something or its an issue with Yast2 and/or Wicked. Did you read the lines about editing /etc/resolv.conf, they're in the file. Years ago I missed reading those lines which threw me in a situation like you describe. If I suspect /etc/resolv.conf not to be correct, I remove it, restart the networkservice so that it will be regenerated.
I ended up changing the configuration of the client bridge router into a WDS Station, and the main router to a WDS AP. Now, with a static IP setup through YaST the WDS Station can lose power and as soon as it's back up I can access all webpages and DNS works perfectly. If I were using those same YaST Network settings with the same router in client bridge mode and with the wireless mode on the main router as "AP", once the router lost power I would have no DNS once the client bridge router came back up. All the static settings in YaST must be right if I am having no issues now with WDS. For whatever reason, client bridge mode with DD-WRT didn't like my static IP setup once the power came back up as I would have no DNS until switching to DHCP and then back to static. It may have also worked if I changed the IP to something else and then back to the original private address, but I don't think I had tried that. I have a spare identical unit, so I can put that in client bridge mode and the router back in AP mode to try to nail this one down, but as it stands now I am stumped. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org