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 <[email protected]> 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 > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
