Not to cause confusion - just adding/rephrasing to what was already stated.
WAP is really just like ethernet socket in the wall - you connect to it trough it using your Wi-Fi adapter as if by ethernet cable to your LAN. On your LAN (assuming that there is a router between your network and the internet) you typically have DHCP server which assign your computer IP address, default route, network mask and DNS server. It could also assign NTP server and bunch of other info, depending on your DHCP configuration. These days, the network configuration of your client device (desktop/laptop) is done by "greatly simplified client front-ends" (such as Network manager) to myriad of different networking workarounds such as updating /etc/resolv.conf. This is to pretend that the special network client is classic network setup. For that reason there is quite a few things, beside resolv.conf, which can influence your client DNS config. There are config databases, systemd services, /etc/config file, etc. Unless you know exactly what your client is doing - which I doubt is possible for non enterprise-simplified-system setup. I would stay away from messing up with DNS config on your laptop/desktop. Instead - I recommend focusing on what/why is your DHCP server sending at the time of your client config. <Disclaimer> Of course if the network is IPv6 it can be simpler - autoconfig without DHCP - or messier with autoconfig AND DHCPv6 + DHCPv4. Also - if dual stack IPv4/IPv6 your working/broken DNS can be IPv6 one. I do not remember, honestly - there is/was someone who seems to hate DHCP address assignemt/config for IPv4 in favor of managing everything by hand with static configs. If this is that particular case - please disregard this entire post because it has no value to you. If it is your case - trying to have fully static config - attempting to ignore DHCP from your router/LAN you will probably have make sure to: a) kill that DHCP server somehow b) uninstall/disable all packages which can act like DHCP client - which maybe not possible due to dependency chain of vorious other packages you need. c) Stress that static nature of your network in your emails - it is important to know. </Disclaimer> Hope this post adds value, Tomas On Mon, 2019-05-27 at 07:09 -0700, Ben Koenig wrote: > rc.local only gets run at boot. > If wicd reconnects the network at any point after then it will not > re-run your workaround, so you will need to reboot the computer to fix > your DNS. What you did is called a "work-around" and is not even close > to qualifying as a solution. > > > In your first post you said that your resolv.conf was "overwritten by > the belkin WAP". This is incorrect, so here's a quick step-by-step for > what is actually happening > > 1) Your WAP boots and sets various parameters on it's end > 2) the laptop boots and launches wicd to configure a wireless interface > 3) wicd connects to the WAP and "requests" the DNS configuration. > 4) wicd merges the WAP DNS settings with user defined options (wicd > gives you the ability to set DNS on a per-network basis IIRC) > 5) resolv.conf is written. > > > For issues with bad DNS settings, your first 2 steps should always be thus: > 1) Verify the DNS servers set in your WAP/Router > 2) Verify the DNS settings used by your network management daemon (wicd) > > > Is your laptop setting the wrong IP, or is it being given the wrong IP? > The disparity should become obvious if you know where to look. > > On Mon, May 27, 2019 at 5:41 AM Rich Shepard <rshep...@appl-ecosys.com> wrote: > > > > On Sun, 26 May 2019, Ben Koenig wrote: > > > > > You keep saying you have a WAP and a router > > > - is this 2 devices? We should only care about 1. > > > > The Wireless Access Point (WAP) is the device to ... > > > - which of these devices does your laptop connect to? > > > > and, as the name suggests the laptop and WAP connect via radio, the first > > ... > > > - wifi or Ethernet connection? > > > - are you using networkmanager, wicd, or rc.inet1 to bring up the network? > > > > All portables here use wicd, every host has rc.inet1.conf properly > > configured. > > > > > Please describe your entire hardware/software setup. By adding a line to > > > rc.local you have literally doubled the number of times resolv.conf is > > > written during boot which will come back to haunt you. > > > > The router connects the LAN, including the WAP, to the outside world of the > > Internet. > > > > Some times having to re-load a utility provides a working solution. I've yet > > to have such a solution become a problem. > > > > Regards, > > > > Rich > > _______________________________________________ > > PLUG mailing list > > PLUG@pdxlinux.org > > http://lists.pdxlinux.org/mailman/listinfo/plug > > _______________________________________________ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
