On 2020-07-16 20:21, Ed Greshko wrote:
Yes. I had been assigning addresses but found letting the router dhcp server do it is much more convenient. I can change them if I want and make them static so they match the mac addresses for filtering, and whatever ... Nothing is set in concrete, I can do it differently if not the best way.
No, no need to change it.
It explains why "ping smb" was able to get an IP address.
I'm pretty sure that you have the IP address of the router in your /etc/resolv.conf.
So, the DNS server your using is the same as the DHCP server. In this case, when the DHCP server supplies a lease it also adds a DNS record.
That didn't dawn on me since all of my servers use static IPv4 and IPv6 addresses and use a different DNS server than the router.
° I use hosts for convenience, as you can see it is not up to date: [bobg@WS1 ~]$ cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.50.57 WS1 ws1 192.168.2.179 ws2 WS2 192.168.50.32 nfs NFS 192.168.50.149 smb SMB
And 192.168.50.1 [bobg@WS1 ~]$ cat /etc/resolv.conf # Generated by NetworkManager
192.168.50.1 is the router, as you observed earlier I just went with the '.50' to differentiate between the system, Dish Network also added a 10.1.something a while back ... There are two Ethernet ports on the Viasat modem and I cold use a third one, I have the Dish Network router turned off, have had no complaints yet. I guess it might work to add another switch between the modem and a router, I have not tried that yet? Presently the other routers turned off so they are not contributing uncertainties.