Re: [SLE] sshd can't bind to port 22

19 Feb 2002


      You're right, that is it.  Still don't know why sshd is trying to start 
twice, but I can try to track it down.  At least I have one going - that was 
my big worry.  Guess I could have seen that I had one running if I had done a 
"ps ax", but after the boot scripts reported failure, I didn't even bother to 
look.  Guess I shouldn't believe everything I read!

Thanks,
Sean

On Monday 18 February 2002 18:01, Jeffrey Taylor wrote:
...
Somehow, sshd is being started twice.  The helpful displays are
"netstat -A inet -an" (shows open ports) and "lsof -i :22" (connects
to/from port 22).
HTH,
  Jeffrey
Quoting Theo.Sean Schulze :
...
Hello,
While trying to fix my monitor's invalid scan problem, I rebooted the
machine.  When it came back up, sshd failed to start.  A glance in
/var/log/messages shows:
Feb 18 17:42:11 dragoon sshd[16878]: error: Bind to port 22 on 0.0.0.0
failed: Address already in use.
Feb 18 17:42:11 dragoon sshd[16878]: fatal: Cannot bind any address.
When I do a netstat -rn, I get this:
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface 192.168.1.99    0.0.0.0         255.255.255.255 UH       40 0      
   0 ippp0 217.5.98.42     0.0.0.0         255.255.255.255 UH       40 0 
        0 ppp0 192.168.1.100   0.0.0.0         255.255.255.255 UH      
40 0          0 eth1 192.168.1.0     0.0.0.0         255.255.255.0   U   
    40 0          0 eth0 192.168.1.0     0.0.0.0         255.255.255.0  
U        40 0          0 eth0 192.168.1.0     0.0.0.0        
255.255.255.0   U        40 0          0 eth1 0.0.0.0        
xxx.xxx.xxx.xxx 0.0.0.0         UG       40 0          0 ppp0
/etc/route.conf looks like this:
192.168.1.0             0.0.0.0                 255.255.255.0          
eth0 192.168.1.100		0.0.0.0			255.255.255.255		eth1
192.168.1.99            0.0.0.0                 255.255.255.255        
ippp0 default			192.168.1.100		0.0.0.0			eth1
I am wondering if I should change the gateways for the different
interfaces. For example, 192.168.1.0 is my local network address and the
NIC that the local traffic passes through (eth0) has the IP 192.168.1.3. 
Should 192.168.1.3 be eth0's gateway?  Since eth1 is the NIC attached to
my DSL connection, should it have its own IP as the gateway?  Same for
ippp0 my ISDN card?  Everything else would get the default (eth1)?
TIA,
Sean
-- 
Theo. Sean Schulze                                               
tschulze@nuthole.de

"[T]he key to maintaining leadership in the economy and the technology that
are about to emerge is likely to be the social position of knowledge 
professionals and social acceptance of their values." -- Peter Drucker