SSH on LOCAL network not working

[klangfeld]

Hi Community, 

I have to computers connected via WIFI to my HUB 4 with IPs 192.168.0.44 and 192.168.0.210. I want to login (or file transfer) into one machine from the other: 

e.g. on 192.168.0.44: ssh 192.168.0.210

Occasionally, this worked, but lately the connection always times out. 

Any help would be greatly appreciated. 

Thanks! 

[sophist]

erm. 

if they're both connected to the network, can you ping pc_b (192.168.0.210) from pc_a (192.168.0.44)? if ping times out, can you see the pc_b in the arp table?

there's not really much to go wrong here.. if they can see each other on the network, then check firewall settings on the device running ssh and make sure it's allowing connections through on port 22 - it's also worth double-checking that the ssh server is actually started... 

[klangfeld]

Thank you, Sophist, for your quick reply. 

I can ping both machines when I login to hub 4 and use ping under "tools", e.g., 

PING 192.168.0.44: 64 data bytes
--- 192.168.0.44 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 3.000/22.000/43.000 ms

PING 192.168.0.210: 64 data bytes
--- 192.168.0.210 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 3.000/24.000/58.000 ms

However, if I use    from 192.168.0.44: ping 192.168.0.210, I get 100% packet loss. 

The strange thing is that SSH from one machine to the other did work in the past now and then (which means that the SSH and firewall settings on both computers are correct). It seems that some port blocking is going on when a local machine tries to connect to another local machine via the hub. 

Thanks again. 

[sophist]

that is odd. 

on computer 192.168.0.44, after you've tried to ping .210, can you then run the command "arp -a" in the command line and paste the output back here..?

[klangfeld]

Thanks again. 

from 192.168.0.44: ping 192.168.0.210 times out: 

PING 192.168.0.210 (192.168.0.210): 56 data bytes

Request timeout for icmp_seq 0

ping: sendto: No route to host

Request timeout for icmp_seq 1

ping: sendto: Host is down

Request timeout for icmp_seq 2

^C

--- 192.168.0.210 ping statistics ---

4 packets transmitted, 0 packets received, 100.0% packet loss

There is no route to host. For the arp common, I get: 

arp -a

? (192.168.0.1) at **:**:**:**:**:** on en1 ifscope [ethernet]

? (192.168.0.255) at **:**:**:**:**:** on en1 ifscope [ethernet]

? (224.0.0.251) at 1:0:5e:0:0:fb on en1 ifscope permanent [ethernet]

broadcasthost (255.255.255.255) at **:**:**:**:**:** on en1 ifscope [ethernet]

[sophist]

it's almost like the hub is enforcing some sort of guest network policy that doesn't allow endpoints to communicate with each other, only the hub itself..

the devices are in the same IP broadcast domain, it's a flat network..  

are you able to connect both devices to the hub over ethernet and see if that works? (just for testing purposes)

all i can suggest really is that you factory reset the hub4 and see if that kicks it back into life.. 

[klangfeld]

yes, I can connect to the HUB 4 from both machines. Both machines appear in the device list. All looks normal. 

I need wifi 8-10 hours a day for work from home. I am wary to do a factory reset with perhaps unforeseen consequences. 

Thanks for your help anyhow. 

Kurt 

[sophist]

worth testing over a wired connection if you can - see if you get the same behaviour.. 

if you have a switch to add into the mix, all the better, since it won't touch the hub at all then.. 

[legacy1]

Hubs in router mode like to block SSH so likely a bug even if its not to the hub.

[klangfeld]

Thanks again. 

I still had a wifi extender, and connected this to the Hub 4 via wifi, and configured the extender as different access points. Once I connect both machines to the extender, I can ssh between the computers. 

Indeed, it seems that the Hub suppresses communications between the connected devices (which is sort of unacceptable; I also have a wifi connected printer). 

Is this considered a feature or a bug? 

Thanks, Legacy1, for your comment. I tend to agree that this is a bug. 

What is the best option? 

1. would a nerve racking factory rest fix the issue (bug?) ? 

2. contact virgin for help to reconfigure the Hub

3. buy a mesh with about 4 LAN ports (for the Virgin phone and TV) and have the Hub in modem mode

Thanks again.