Hi,
The first symptom was that when I logged in that the second request for a ssh pass phrase took much longer, sometimes so long as to time out.
The other problem I get is lots of error messages that look like:
A curl of this on my local Mac returns in about 1 second.
the same on David
Both the entries in /etc/resolv.conf are not reachable.
bruceoneel@david:~/tmp$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 69.20.0.164
nameserver 69.20.0.196
bruceoneel@david:~/tmp$ ping 69.20.0.164
PING 69.20.0.164 (69.20.0.164) 56(84) bytes of data.
From 23.253.149.127 icmp_seq=1 Destination Host Unreachable
From 23.253.149.127 icmp_seq=2 Destination Host Unreachable
From 23.253.149.127 icmp_seq=3 Destination Host Unreachable
^C
--- 69.20.0.164 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4022ms
pipe 3
bruceoneel@david:~/tmp$ ping 69.20.0.196
PING 69.20.0.196 (69.20.0.196) 56(84) bytes of data.
From 23.253.149.127 icmp_seq=1 Destination Host Unreachable
From 23.253.149.127 icmp_seq=2 Destination Host Unreachable
From 23.253.149.127 icmp_seq=3 Destination Host Unreachable
^C
--- 69.20.0.196 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3013ms
pipe 3
bruceoneel@david:~/tmp$
If I add 1.1.1.1 to the name server list in /etc/resolv.conf it doesn't help.
After Tobias talked to backspace, it turns out that a reboot solved the problem. Maybe it was a routing problem? OTOH packets over port 22 did make it in and out so I don't know...
cheers
bruce