Hello, I have two Ubuntu PCs on my network. I can use ssh from one PC to the other one if they are connected by ethernet to the router. I can't if one of the two PCs is connected by wifi. I read here https://community.netgear.com/t5/Nighthawk-Pro-Gaming-Routers/ssh-problem-with-wifi-on-XR500-but-works-fine-via-ethernet/m-p/1709736/highlight/true#M8367 that someone had the same problem. This person enabled HT160 in the advanced settings of the wifi. The point is that I cannot enable HT160. I check HT160, I click "Appy" and nothing happens. The button does not work. I use Chrome. Should I try another navigator ? Could you help me thanks in advance

> Model: XR500|Nighthawk Pro Gaming Router Firmware version? > [...] I can use ssh from one PC to the other one if they are connected> by ethernet to the router. I can't if one of the two PCs is connected by> wifi. [...] Which kind of "can't"? Actual error message? > I read here [...] Note that that fellow found the appropriate forum for an XR500.

can't means that there is no error message. Even a ping does not work.I write "ssh <pc2>" in a bash shell from <pc1> and just nothing happens if one of the two PCs is connected to the router by wifi.

firmware V2.3.2.114I also have problems with my printer. Print jobs are stuck, and I have to retry and finally the page is printed... I start thinking that this router is just bugged and I'm going to return it if my intuition is correct...

> can't means that there is no error message. [...] Around here (Mac or VMS, usually), when ssh fails, I get an errormessage. I'd expect ssh on any GNU/Linux to do that, too. Unless it'shung waiting for a DNS server, or something like that. But "can't"provides almost exactly no useful information. > [...] Even a ping does not work. [...] Again, "not work" is not a useful problem description. It does notsay what you did. It does not say what happened when you did it. Asusual, showing actual actions (commands) with their actual results(error messages, LED indicators, ...) can be more helpful than vaguedescriptions or interpretations. Especially when using a command-lineprogram, copy+paste is your friend. "ping" from what to what? Some actual IP addresses might beinteresting, too. > I also have problems with my printer. [...] I know nothing about your printer, including how it's connected towhat.> I start thinking that this router is just bugged [...] Possible, but with only "can't" and "does not work", there's not muchI can do. I've suggested to a forum moderator that this thread belongs in thatother forum, but I don't know if or when it might get moved. If it doesnot get moved, then you might want to post again in that (moreappropriate) forum.

It's simple: I have <pc1> and <pc2> (it's 192.168.1.30 and 192.168.1.2 but what's the point ?).From a shell prompt in <pc1>, ssh <pc2> gives me access to pc2 if the two pc are connected by ethernet. If one of them is connected by wifi, nothing happens, it's just stuck and I don't know why. What else can I say ? The DNS is the same in both cases. More interesting and instructive, I managed to enable HT160 in the advanced settings of the wifi, as suggested in https://community.netgear.com/t5/Nighthawk-Pro-Gaming-Routers/ssh-problem-with-wifi-on-XR500-but-works-fine-via-ethernet/m-p/1709736/highlight/true#M8367. How did I proceed ? By booting in Windows 10 and using Microsoft Edge. It means that the user interface of the router is not compatible with Chrome or Firefox (I tried Firefox too). And by the way, that did not solve the problem either. Concerning the printer, a Brother printer which works with Windows 10, my ipad and linux, the printing jobs are stuck for unknown reason, my ipad for example tells me after a (long) while : Brother HL-L2375DW seriesUne erreur s'est produite lors del'impression du document"Annuler" "Réessayer" which in English can be translatedAn error occured whileprinting the document"Cancel" "Retry" You will notice that my printer is detected and connected (by wifi, I tried by ethernet and it's the same problem).

Connecting two linux PCs by ssh | NETGEAR Communities

14 Replies

antinode
Guru
Jun 11, 2021
> Model: XR500|Nighthawk Pro Gaming Router

   Firmware version?

> [...] I can use ssh from one PC to the other one if they are connected
> by ethernet to the router. I can't if one of the two PCs is connected by
> wifi. [...]

   Which kind of "can't"? Actual error message?

> I read here [...]

   Note that that fellow found the appropriate forum for an XR500.
- Philippe2021
  Guide
  Jun 11, 2021
  can't means that there is no error message. Even a ping does not work.I write "ssh <pc2>" in a bash shell from <pc1> and just nothing happens if one of the two PCs is connected to the router by wifi.
  - Philippe2021
    Guide
    Jun 11, 2021
    firmware V2.3.2.114
    I also have problems with my printer. Print jobs are stuck, and I have to retry and finally the page is printed...
    
    I start thinking that this router is just bugged and I'm going to return it if my intuition is correct...

antinode

Guru

Jun 12, 2021

> It's simple: I have <pc1> and <pc2> (it's 192.168.1.30 and 192.168.1.2
> but what's the point ?).

It's _not_ simple. As I always say, "Everything's complicated."

> From a shell prompt in <pc1>, ssh <pc2> [...]

Which part of "actual actions (commands)" was unclear? What, exactly
is "<pc2>"?

> [...] Especially when using a command-line program, copy+paste is your
> friend.

Still true.

A _computer_ does not have an IP address; a network _interface_ has
an IP address. If a computer has more than one active network
interface, then each one must have its own IP address. If you're trying
to reach a computer's wireless interface at the IP address of that
computer's (disconnected) Ethernet interface, then I'd expect problems.

Even if only network interface is active at a time, if it gets its
address (and other parameters) using DHCP, then I'd expect each
interface to get a unique IP address, because each interface has its own
unique MAC address.

I still know nothing about the XR500, but its User Manual suggests
that the Device Manager in its management web site will report on the
attached devices. I'd look closely at that report when you switch
between Ethernet and wireless on one of your <pcX> systems.

> [...] it's just stuck [...]

How long did you wait? Give it a few minutes, not only a few
seconds?

> [...] I don't know why. [...]

I knew that. That's why we're here.

> [...] What else can I say ? [...]

You could answer the questions as asked, with "actual actions
(commands) with their actual results (error messages, [...]", and not
simplify, generalize, or pre-analyze anything.

> [...] And by the way, that did not solve the problem either.

I doubt that the "NetDuma Partner" fellow in that other thread
actually believed that that setting made any difference...

> [...] I would not have guessed that would have affected it but happy
> you managed to resolve it!

...but if the user is happy, it's easier to stop troubleshooting than to
try to find out what actually happened. Few people have the patience
and discipline to change only one thing at a time, so a statement like
"I did X, and now it works" can be misleading.

Everything's complicated.

Philippe2021

Guide

Jun 12, 2021

A _computer_ does not have an IP address; a network _interface_ has
an IP address.  If a computer has more than one active network
interface, then each one must have its own IP address.  If you're trying
to reach a computer's wireless interface at the IP address of that
computer's (disconnected) Ethernet interface, then I'd expect problems.

I pick the IP adress in the Web interface of the router of course.

What, exactly
is "<pc2>"

<pc2> is an IP adress. Right now, my laptop computer is on wifi, and my desktop computer always on ethernet, and I have that from my desktop (mars):

XXX@mars:~$ ssh 192.168.1.4
^C
XXX@mars:~$ ping 192.168.1.4
PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data.
64 octets de 192.168.1.4 : icmp_seq=1 ttl=64 temps=198 ms
64 octets de 192.168.1.4 : icmp_seq=2 ttl=64 temps=16.4 ms
^C
--- statistiques ping 192.168.1.4 ---
2 paquets transmis, 2 reçus, 0 % paquets perdus, temps 1002 ms
rtt min/avg/max/mdev = 16.434/107.459/198.484/91.025 ms

My desktop computer can ping 192.168.1.4 which is my laptop on wifi but not get a ssh connection.

Even a

dmesg

does not give any information, not even a timeout message. The wifi blocks ssh for some reason (the port 22 is blocked maybe for some reason).

Philippe2021

Guide

Jun 12, 2021

I can give the logs of the router but that won't help I guess.

[admin login] from source 192.168.1.30, Saturday, June 12, 2021 08:16:44
[DoS Attack: SYN/ACK Scan] from source: 52.162.107.6, port 443, Saturday, June 12, 2021 08:11:20
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:49:19
[DumaOS] DHCP lease change., Saturday, June 12, 2021 07:48:39
[DumaOS] DHCP new event., Saturday, June 12, 2021 07:48:39
[DHCP IP: 192.168.1.3] to MAC address 24:20:c7:1c:42:c9, Saturday, June 12, 2021 07:48:39
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:48:28
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:46:58
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:46:29
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:46:14
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:45:28
[DumaOS] DHCP lease change., Saturday, June 12, 2021 07:44:53
[DumaOS] DHCP new event., Saturday, June 12, 2021 07:44:53
[DHCP IP: 192.168.1.3] to MAC address 24:20:c7:1c:42:c9, Saturday, June 12, 2021 07:44:53
[DumaOS] DHCP lease change., Saturday, June 12, 2021 07:44:27
[DumaOS] DHCP new event., Saturday, June 12, 2021 07:44:27
[DHCP IP: 192.168.1.3] to MAC address 24:20:c7:1c:42:c9, Saturday, June 12, 2021 07:44:27
[DumaOS] Using disabled(NOP) QoS subclass, Saturday, June 12, 2021 07:44:26
[DumaOS] Using disabled(NOP) QoS subclass, Saturday, June 12, 2021 07:44:26
[DumaOS] Using disabled(NOP) QoS subclass, Saturday, June 12, 2021 07:44:25
[DumaOS] Using disabled(NOP) QoS subclass, Saturday, June 12, 2021 07:44:25
[DumaOS] Using disabled(NOP) QoS subclass, Saturday, June 12, 2021 07:44:24
[DumaOS] DHCP lease change., Saturday, June 12, 2021 07:43:28
[DHCP IP: 192.168.1.3] to MAC address 24:20:c7:1c:42:c9, Saturday, June 12, 2021 07:43:28
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:42:36
[DumaOS] DHCP lease change., Saturday, June 12, 2021 07:42:04
[DumaOS] DHCP new event., Saturday, June 12, 2021 07:42:04
[DHCP IP: 192.168.1.3] to MAC address 24:20:c7:1c:42:c9, Saturday, June 12, 2021 07:42:04
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:41:06
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:40:25
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:40:14
[admin login] from source 192.168.1.30, Saturday, June 12, 2021 07:39:21
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:39:16
[DumaOS] DHCP lease change., Saturday, June 12, 2021 07:39:15
[DumaOS] DHCP new event., Saturday, June 12, 2021 07:39:15
[DHCP IP: 192.168.1.3] to MAC address 24:20:c7:1c:42:c9, Saturday, June 12, 2021 07:39:15
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:38:59
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:38:53
[DumaOS] DHCP lease change., Saturday, June 12, 2021 07:38:47
[DumaOS] DHCP new event., Saturday, June 12, 2021 07:38:47
[DHCP IP: 192.168.1.4] to MAC address 9c:b6:d0:8d:a5:3f, Saturday, June 12, 2021 07:38:47
[DumaOS] DHCP lease change., Saturday, June 12, 2021 07:38:47
[DumaOS] DHCP new event., Saturday, June 12, 2021 07:38:47
[DHCP IP: 192.168.1.4] to MAC address 9c:b6:d0:8d:a5:3f, Saturday, June 12, 2021 07:38:47
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:38:16
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:37:46
[admin login] from source 192.168.1.4, Saturday, June 12, 2021 07:36:53
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:36:46
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:36:16
[DumaOS] DHCP new lease allocated., Saturday, June 12, 2021 07:35:44
[DumaOS] DHCP new event., Saturday, June 12, 2021 07:35:44
[DHCP IP: 192.168.1.4] to MAC address 9c:b6:d0:8d:a5:3f, Saturday, June 12, 2021 07:35:44
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:35:20
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:34:46
[DumaOS] DHCP lease change., Saturday, June 12, 2021 07:33:38
[DumaOS] DHCP new event., Saturday, June 12, 2021 07:33:38
[DHCP IP: 192.168.1.3] to MAC address 24:20:c7:1c:42:c9, Saturday, June 12, 2021 07:33:38
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:33:12
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:32:54
[DoS Attack: SYN/ACK Scan] from source: 52.162.107.6, port 443, Saturday, June 12, 2021 07:32:49
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:32:47
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:32:22
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:31:42
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:30:42
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:30:12
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:29:38
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:28:55
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:28:29
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:28:13
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:27:25
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:25:55
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:24:34
[DumaOS] DHCP new lease allocated., Saturday, June 12, 2021 07:24:12
[DumaOS] DHCP new event., Saturday, June 12, 2021 07:24:12
[DHCP IP: 192.168.1.11] to MAC address 48:b0:2d:09:8a:35, Saturday, June 12, 2021 07:24:12
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:23:53
[admin login] from source 192.168.1.30, Saturday, June 12, 2021 07:23:51
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:22:59
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:22:28
[DumaOS] DHCP lease change., Saturday, June 12, 2021 07:22:25
[DumaOS] DHCP new event., Saturday, June 12, 2021 07:22:25
[DHCP IP: 192.168.1.3] to MAC address 24:20:c7:1c:42:c9, Saturday, June 12, 2021 07:22:25
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:22:13
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:21:29
[DumaOS] Marking device that is marked 192.168.1.3 11 10., Saturday, June 12, 2021 07:19:59

Forum Discussion

Connecting two linux PCs by ssh