On Thu, Apr 20, 2017 at 12:32:41AM -0700, Kenneth Porter wrote:> --On Thursday, April 20, 2017 12:34 AM -0400 Fred Smith > <fredex at fcshome.stoneham.ma.us> wrote: > > >works fine. until I fire up a vpn. having done that, looking in > >/etc/resolv.conf (while the vpn is connected) it has reverted to > >192.168.2.1. > > > >after shutting down the vpn, 192.168.2.1 remains in resolv.conf > > Which VPN? It's not uncommon for VPN software to change the resolver > setting to point to your VPN peer's DNS, so that all traffic goes > through the VPN, including your DNS traffic.I use OpenConnect VPN for this pareticular task. and yes I know the vpn changes it, then should put it back when one disconnects. problem is, where is it getting the old address from? It isn't in the resolv.conf before the vpn is started, and it is not in the NM setups, anywhere, and it isn't in any of the files in /etc/sysconfig/network*, so where is it coming from? And that particular system is NOT using DHCP. Beats me! Fred -- ---- Fred Smith -- fredex at fcshome.stoneham.ma.us ----------------------------- God made him who had no sin to be sin for us, so that in him we might become the righteousness of God." --------------------------- Corinthians 5:21 ---------------------------------
--On Thursday, April 20, 2017 9:10 AM -0400 Fred Smith <fredex at fcshome.stoneham.ma.us> wrote:> problem is, where is it getting the old address from? It isn't in > the resolv.conf before the vpn is started, and it is not in the NM > setups, anywhere, and it isn't in any of the files in > /etc/sysconfig/network*, so where is it coming from? And that particular > system is NOT using DHCP. Beats me!Good question. Could systemd be involved? I found this bug: <https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317> --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
On Fri, Apr 21, 2017 at 08:34:29AM -0700, Kenneth Porter wrote:> --On Thursday, April 20, 2017 9:10 AM -0400 Fred Smith > <fredex at fcshome.stoneham.ma.us> wrote: > > >problem is, where is it getting the old address from? It isn't in > >the resolv.conf before the vpn is started, and it is not in the NM > >setups, anywhere, and it isn't in any of the files in > >/etc/sysconfig/network*, so where is it coming from? And that particular > >system is NOT using DHCP. Beats me! > > Good question. Could systemd be involved? I found this bug: > > <https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317>I'll take a look at that, thanks. I also have more info... My router is stupid. apparently it sends to the dhcp clients the nameserver address you enter into the dhcp configs, but it appends its own LAN address to it so the clients get both: https://www.snbforums.com/threads/dns-problems-with-dhcp.23132/#post-319233 that is a discussion of a similar router from the same mfg as mine, and it behaves the same way. You can see this directly if you have a windows system, run "ipconfig /renew" then "ipconfig /all" and you'll see both addresses listed as DNS. Now, does that have anything to do with my Centos box which is manually configured? I can't see how, but it makes me wonder. -- ---- Fred Smith -- fredex at fcshome.stoneham.ma.us ----------------------------- "For the word of God is living and active. Sharper than any double-edged sword, it penetrates even to dividing soul and spirit, joints and marrow; it judges the thoughts and attitudes of the heart." ---------------------------- Hebrews 4:12 (niv) ------------------------------