On 03/04/2019 05.30, Patrick Shanahan wrote:
* Lew Wolfgang <> [04-02-19 23:11]:
...
Could the server's firewall, which apparently has multiple Ethernet ports, be forwarding traffic off-network? Maybe just return packets? Some kind of a loop? What does "ip addr" and "ip route" have to say?
# ip addr 1: lo:
mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 78:e3:b5:ad:f1:2f brd ff:ff:ff:ff:ff:ff inet 192.168.1.3/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 2600:1702:1031:3f90:7ae3:b5ff:fead:f12f/64 scope global mngtmpaddr dynamic valid_lft 3320sec preferred_lft 3320sec inet6 fe80::7ae3:b5ff:fead:f12f/64 scope link valid_lft forever preferred_lft forever 3: wlan0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 74:de:2b:df:0e:c9 brd ff:ff:ff:ff:ff:ff
You do have IPv6 addresses.
When all else fails, maybe it's time to break out tcpdump or wireshark to see exactly what's coming and going.
Carlos also has a point about the wahoo.no-ip.org name resolution. What does your /etc/resolv.conf look like? And /etc/hosts?
### /etc/resolv.conf file autogenerated by netconfig! # ... search attlocal.net wahoo.no-ip.org nameserver 156.154.70.1 nameserver 8.8.4.4 nameserver 64.94.33.33
...
108.246.209.12 wahoo.no-ip.org paka 192.168.1.3 wahoo.wahoo.no-ip.org wahoo 192.168.1.2 toshiba.wahoo.no-ip.org toshiba 192.168.1.100 Carolyn.wahoo.no-ip.org Carolyn 192.168.1.101 acer.wahoo.no-ip.org acer 192.168.1.5 dell.wahoo.no-ip.org dell 192.168.1.8 crash2.wahoo.no-ip.org crash2 192.168.1.10 Crash.wahoo.no-ip.org Crash
the current hosts/resolv.conf have work properly for years...
Yes, they work as intended, but... it doesn't look right to me. The thing is, you are using internally machine names with an "external" name. IMO, the correct thing would be something like: 192.168.1.3 wahoo.wahoo wahoo 192.168.1.2 toshiba.wahoo toshiba 192.168.1.100 Carolyn.wahoo Carolyn 192.168.1.101 acer.wahoo acer 192.168.1.5 dell.wahoo dell 192.168.1.8 crash2.wahoo crash2 192.168.1.10 Crash.wahoo Crash That is, the names *.wahoo.no-ip.org would resolve (or not) externally, while the names *.wahoo would resolve internally. The way you have it, it is possible that a query to wahoo.wahoo.no-ip.org or Crash.wahoo.no-ip.org would be asked at an external domain name server (with empty answer): cer@Telcontar:~/tmp/patrick> host wahoo.wahoo.no-ip.org cer@Telcontar:~/tmp/patrick> -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)