Results 1 to 3 of 3
Hi there wlan0 is connected to 192.168.0.0 eth0 is connected to 10.10.0.0 I can ping 10.10.0.10 I can't ssh to it pkirk ~ # route Kernel IP routing table Destination ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 01-13-2012 #1
- Join Date
- Oct 2008
wlan0 is connected to 192.168.0.0
eth0 is connected to 10.10.0.0
I can ping 10.10.0.10
I can't ssh to it
pkirk ~ # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
ddns001bri.loca * 255.255.255.255 UH 0 0 0 eth0
192.168.0.0 * 255.255.255.0 U 2 0 0 wlan0
10.10.0.0 * 255.255.0.0 U 1 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 wlan0
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
ddns001bri.loca = 10.10.0.10
pkirk ~ # ping 10.10.0.10
PING 10.10.0.10 (10.10.0.10) 56(84) bytes of data.
64 bytes from 10.10.0.10: icmp_req=1 ttl=64 time=1.27 ms
pkirklewski ~ # ssh 10.10.0.10 -p 3103
ssh: connect to host 10.10.0.10 port 3103: No route to host
What do I do to fix this please ?
- 01-15-2012 #2
The only thing I can think of is a firewall on destination host blocking port. Try disable firewal on 10.10.0.10 (or disable on both machines), if you didn't already.
- 01-15-2012 #3
- Join Date
- May 2011
Luis is probably right. but if that's not it, is there a cable modem/router sitting inb/t the two computers? I ask b/c of the weird SSH port you listed. If so, maybe the port-forwarding rules need to be set up on it (to forward incoming TCP requests on port 3103 to port 22 on the server behind the router. If it's not that, then I assume your SSH server is actually set up to run on that port?