|
FreeBSD 7.4, sshd stopped responding after I got a new IPv4 address
![[se]](/s/countries/se.gif) Shadow Hawkins on Monday, 02 May 2011 17:33:51
For some reason my ISP decided that I needed a new IPv4 address this morning.
After changing a few config files and restarting a few daemons (including restarting sshd, of course) I was back up and running again (and sixxs-aiccu was also restarted during this little run).
Everything seems to be working again but like I have experienced several times before, sshd has magically stopped accepting IPv6 connections. Other daemons still accept IPv6 connections just fine but sshd is now only responding on IPv4 connections.
Has anyone experienced anything like this before? Is there a solution beyond basically rebooting/re-initing the whole system?
FreeBSD 7.4, sshd stopped responding after I got a new IPv4 address
Shadow Hawkins on Monday, 02 May 2011 17:43:05
Ok, I just noticed something funny. The same machine is having trouble with outbound SSH connections over IPv6 as well now.
Curiouser and curiouser. Time to just reboot this server before this drives me mad (and I wish there were logs of this but there is nothing in the logs, it's like sshd and the ssh client are both pretending that IPv6 doesn't exist).
FreeBSD 7.4, sshd stopped responding after I got a new IPv4 address
Shadow Hawkins on Monday, 02 May 2011 18:18:23
I just discovered the cause of the issue. The machine in question is running the reverse DNS resolver for my IPv6 subnet and wasn't responding to reverse lookup requests because of the changed IPv4 address.
Of course, when looking at the sshd logs and the output of "ssh -vvv" it looked more like the problem was key-based (that's where it would freeze up completely for several minutes).
|
Posting is only allowed when you are