On 2016-04-14 03:26, sdm wrote:
On 04/13/2016 05:44 PM, Carlos E. R. wrote:
With static settings, unplug the router, reconnect, then do: ... After replugging router with static IP:
# ip addr 2: enp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 8c:89:a5:6f:52:b3 brd ff:ff:ff:ff:ff:ff inet 192.168.1.4/24 brd 192.168.1.255 scope global enp7s0 valid_lft forever preferred_lft forever inet6 fe80::8e89:a5ff:fe6f:52b3/64 scope link valid_lft forever preferred_lft forever
# ip route default via 192.168.1.1 dev enp7s0 192.168.1.0/24 dev enp7s0 proto kernel scope link src 192.168.1.4
# cat /etc/resolv.conf | egrep -v "^[[:space:]]*$|^#" nameserver 192.168.1.1
# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. From 192.168.1.3 icmp_seq=13 Destination Host Unreachable From 192.168.1.3 icmp_seq=19 Destination Host Unreachable
# ping google.com PING google.com (216.58.218.110) 56(84) bytes of data. ^C --- google.com ping statistics --- 26 packets transmitted, 0 received, 100% packet loss, time 25158ms
So that's the problem, DNS fails. Connectivity is working.
----------Now, I have switched to DHCP and back to static:----------
# ip addr
2: enp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 8c:89:a5:6f:52:b3 brd ff:ff:ff:ff:ff:ff inet 192.168.1.4/24 brd 192.168.1.255 scope global enp7s0 valid_lft forever preferred_lft forever inet6 fe80::8e89:a5ff:fe6f:52b3/64 scope link valid_lft forever preferred_lft forever
# ip route default via 192.168.1.1 dev enp7s0 192.168.1.0/24 dev enp7s0 proto kernel scope link src 192.168.1.4
# cat /etc/resolv.conf | egrep -v "^[[:space:]]*$|^#" nameserver 192.168.1.1
# ping google.com PING google.com (216.58.194.142) 56(84) bytes of data. 64 bytes from dfw06s49-in-f14.1e100.net (216.58.194.142): icmp_seq=1 ttl=51 time=72.1 ms 64 bytes from dfw06s49-in-f14.1e100.net (216.58.194.142): icmp_seq=2 ttl=51 time=70.7 ms 64 bytes from dfw06s49-in-f14.1e100.net (216.58.194.142): icmp_seq=3 ttl=51 time=71.1 ms ^C --- google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 70.715/71.334/72.102/0.653 ms
And now DNS works. I don't understand it, unless you are running dnsmasq, and it captured another DNS server in the interval that dhcp was active. you could try: host google.com 192.168.1.1 host google.com 8.8.8.8
I will plug a Windows laptop with a static IP assigned into the client bridge router later to see what happens. Once again, I have a DD-WRT client bridge router with DHCP shut off that I plug the ethernet cable into. That router talks wirelessly to my main router which is thr DHCP server and which is connected to the cable modem. But if that were part of this whole problem, I don't see why Wicked and DHCP work fine and static addressing doesn't, unless this is some odd bug. Maybe someone can set a static IP and test, unplug the router and plug it back in and see if they still have DNS?
I doubt that it is related. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)