On 05/17/2018 12:42 PM, Daniel Bauer wrote:
On 17.05.2018 20:47, John Andersen wrote:
Are your /etc/resolv.conf set up reasonably when you use the wifi as opposed to your phone's hotspot? (maybe temporarily code your first nameserver as 8.8.8.8 to avoid dodgy router supplied name servers).
Wow! As nameserver there was the IP of the router. I put 8.8.8.8 there and - puff, it works perfect.
But: when I restart, I guess that nameserver will be overwritten again. How can I make that fix for this wifi?
Nameservers in /etc/resolv.conf are usually provided by the dhcp server (in the wifi router) and accepted (or not) by the dhcp client (laptop). Usually when you make a wifi connection you get to specify those things. Always having your own eliminates a lot of hotel-wifi filtering. Warning: 8.8.8.8 is Google's free DNS service. Some people find the idea of it abhorrent, but I've never seen any indication of "evil" using this, and its is fast. There are others, both free and not-free that you can use. I suspect your lanlord was using a bogus upstream DNS server in his router, and or his DNS daemon in the router was somehow defective. Why it worked for everyone else but not for you is a question. Two DNS servers are usually provided. But no system that I am aware of uses the SECOND one till the first one fails (times-out). So having more won't help much if the first one is problematic. If you want to encode your own DNS for any any/every wifi connection you can do it, and it will be preserved. Its usually done in what ever software is managing wifi connection on your computer. I've attached a small screen shot showing how this is done in my Leap 15 machine using kde and Network Manager, but yours might be different. The image is small, but still might get stripped by the email server, so I'm sending direct as well as to the list. Please don't jump my bones about two copies. -- After all is said and done, more is said than done.
