[opensuse] name resolution
I feel that name resolution is getting more and more complicated, to what end I'm not sure. But it's got to the point I no longer understand it, so I'm hoping somebody can explain. $ ping emonpi PING emonpi.fritz.box (192.168.1.24) 56(84) bytes of data. 64 bytes from emonpi.fritz.box (192.168.1.24): icmp_seq=1 ttl=64 time=0.859 ms 64 bytes from emonpi.fritz.box (192.168.1.24): icmp_seq=2 ttl=64 time=0.663 ms ^C $ ssh pi@emonpi ssh: connect to host emonpi port 22: No route to host $ ssh pi@192.168.1.24 pi@192.168.1.24's password: Linux emonpi 4.14.71-v7+ #1145 SMP Fri Sep 21 15:38:35 BST 2018 armv7l How come I can ping a named host but not connect to it using ssh? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-02-15 04:56 PM, Dave Howorth wrote:
I feel that name resolution is getting more and more complicated, to what end I'm not sure. But it's got to the point I no longer understand it, so I'm hoping somebody can explain.
$ ping emonpi PING emonpi.fritz.box (192.168.1.24) 56(84) bytes of data. 64 bytes from emonpi.fritz.box (192.168.1.24): icmp_seq=1 ttl=64 time=0.859 ms 64 bytes from emonpi.fritz.box (192.168.1.24): icmp_seq=2 ttl=64 time=0.663 ms ^C $ ssh pi@emonpi ssh: connect to host emonpi port 22: No route to host $ ssh pi@192.168.1.24 pi@192.168.1.24's password: Linux emonpi 4.14.71-v7+ #1145 SMP Fri Sep 21 15:38:35 BST 2018 armv7l
How come I can ping a named host but not connect to it using ssh?
Fire up Wireshark and see what's happening. Specifically, look at the destination MAC of the ssh packets, to ensure it matches the device you're trying to reach. If it's the MAC for your router, then for some reason your computer thinks it's off net. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-02-15 22:56, Dave Howorth wrote:
How come I can ping a named host but not connect to it using ssh?
First ssh -v pi@emonpi ssh -v pi@192.168.1.24 And see if there's something in ~/.ssh/config or /etc/ssh/ssh_config for emonpi. Next. Check if firewall/router is interfering. sudo traceroute -T emonpi 22 sudo traceroute -T 192.168.1.24 22 -- /bengan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Bengt Gördén <bengan@bag.org> [02-15-20 18:22]:
On 2020-02-15 22:56, Dave Howorth wrote:
How come I can ping a named host but not connect to it using ssh?
First
ssh -v pi@emonpi ssh -v pi@192.168.1.24
And see if there's something in ~/.ssh/config or /etc/ssh/ssh_config for emonpi.
Next. Check if firewall/router is interfering. sudo traceroute -T emonpi 22 sudo traceroute -T 192.168.1.24 22
or make the attempted ssh connect more vocal, ssh -vvv pi@emonpi ... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Bengt Gördén -
Dave Howorth -
James Knott -
Patrick Shanahan