Quantcast
Channel: EdgeRouter topics
Viewing all articles
Browse latest Browse all 20028

Issues after switching WAN to dynamic IP

$
0
0

I just switched over from a static IP to a dynamic IP on why WAN interface.  Since then I've had a couple of issues I can't resolve.

 

1) SSH no longer listens on the WAN interface.  It works fine on the private interface.  netstat -a proves this out:

 

@ERL01# netstat -a | grep 8192

tcp        0      0 172.16.2.1:8192         *:*                     LISTEN     

 

my config shows

    ssh {                      

        listen-address 172.16.2.1

        listen-address 0.0.0.0

        port 8192           

        protocol-version v2     

    }                 

 

So why does it no longer listen on the dynamic IP?  I'm guessing the SSH service probably needs some kind of hook to restart SSH when it gets a new IP, which isn't happening.

 

2) My DNS is now...iffy.

 

I have named running on an internal linux box.  I have forwarding enabled on the internal/private interface. /etc/resolv.conf shows the IP of the internal name server, as it is configured in the System screen.  

 

However, there is now an /etc/resolv.conf and a /etc/resolv.conf.dhclient-new-eth0 with the IPs of my ISP's nameservers.

 

Resolving on my internal hosts sometimes resolves the name correctly, and sometimes returns a not found.  So it seems like sometimes the ER is forwarding to the internal name server as it should, and sometimes it's using the ISPs nameserver, which of course does not have my internal names.

 

What's going on here?  All this worked great when I had a static WAN IP for several years.

     


Viewing all articles
Browse latest Browse all 20028

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>