On Mon, 2005-10-24 at 16:13, Kai Schaetzl wrote:
Scot L. Harris wrote on Mon, 24 Oct 2005 09:40:29 -0400:
Most of the times I have seen this it is caused due to having IPv6 enabled. ssh binds to the port on IPv4 address or IPv6 then tries to bind a second time to the same port.
This makes sense, thanks! I wonder, why it doesn't happen on Suse, though. ipv6 is also running there, but no such error message.
I don't know the answer to that. I ran Suse a while back for only a short period of time on a test box. Did not get to deep into that system.
Personally I usually disable IPv6 and the zero conf stuff on systems.
Add "alias net-pf-10 off" to modprobe.conf and reboot? Do I need to do anything else? What do you mean with "zero conf stuff"? That is obviously something I'm not aware of.
Actually you should be able to disable IPv6 in the /etc/sysconfig/network file:
networking_ipv6 = no
(that may be in all caps)
zeroconf is what puts the 169.254.0.0 route in your routing table. Look at netstat -rn to see it.
Suppose to allow you to turn on a system without setting up any networking and the system is suppose to find other systems and self configure themselves into a network. You can disable zeroconf by modifying /etc/sysconfig/network by setting the following:
nozeroconf = yes
(again that may be in all caps, check the file)
Have never seen this used for anything. And don't expect to see it used any time soon.
But don't count on that action. Backups are good to have of any configuration files you have changed.
Actually, I edit all my config files on my workstation and then transfer the file to the server machine it belongs to. I maintain a mirrored directory structure of all our machines with the most relevant config files and all changed files locally and also carry them around on my laptop. It's so much easier for comparing configuration and in case you need a fast backup, yes :-)
Good plan!