Help from network people

[skotl]

Pretty much all of the info above is correct.

Devices should be able to see each other on the same network, and the gateway is the device / router that will handle traffic to everything on other networks. So 192.168.0.10 and 192.168.0.11 for IP addresses for each is fine, both with a subnet mask of 255.255.255.0 and default gateway of 192.168.0.1
Crossover cable isn't generally needed as most cards are auto-sensing.

I'd be starting to wonder about the firewall on the pi (if there is such a thing) rather than the Windows device. Remember that pinging is a different protocol - SSH, HTTP etc are TCP/IP commands whereas ping is ICMP. It may be that you don't have ICMP being allowed on either or both of the devices.

Dumb question - can you ping each machine from itself? So if the laptop is 192.168.0.10 can it ping 192.168.0.10, and can the pi ping 192.168.0.11? That doesn't prove the cabling but it does prove that the IP addresses are bound correctly, and that ICMP is working.

Next question - is sshd definitely running on the port you expect it to be? Run "netstat -na" and verify that port 22 is listed. sshd might be running on port 2222, or a different port entirely - run "netstat -nap" to check which processes are listening to which ports.

Next, verify that ssh is receiving connections, from the raspberry pi: "ssh 192.168.0.11 -p 22" (replacing the IP address and port / -p with whatever port is reported via netstat)

 

[Kayos]

Will it connect via a router/switch? If yes its a settings issue, if no its probably hardware

Will try with a switch

I am running out of play time so will likely leave it until next weekend now, plenty to be considering though

 

[skotl]

Following on from the above, when you're checking which port sshd is running on, also be sure that the IP address is the external (i.e. 192.168.0.x) address, not 127.0.0.1
If it's 127.0.0.1 then ssh isn't configured correctly and it will only accept connections from itself

 

[EM1L4]

Windows firewall in its default config will allow any outbound connections, it’s unsolicited inbound it will reject so you shouldn’t need to change anything there. NMAP will likley be using ICMP (aka ping) to find the pi, if it’s detecting it then it’s on the same lan e.g. they can talk with each other…are you handy with wireshark ? That’d be my go to to troubleshoot…

 

[skotl]

Following on from the above, when you're checking which port sshd is running on, also be sure that the IP address is the external (i.e. 192.168.0.x) address, not 127.0.0.1
If it's 127.0.0.1 then ssh isn't configured correctly and it will only accept connections from itself

For example, on my machine (wsl2 not a pi) this what the netstat output looks like:

So sshd is listening, but on port 2222 and is only accepting connections from itself (127.0.0.1 aka local machine).

To fix that I would edit /etc/ssh/sshd_config and look for the entries "ListenAddress" and "Port". I bet your "ListenAddress" looks like this... if so, change it to the 192.168.0.xx IP that you've assigned to the pi:

 

[daleyd]

On your w10 laptop are you using the “new” network centre (the one with the windows 10 look) or the traditional “control panel” method (change network adaptor settings). On my work laptop when I’ve tried to use the”new” method it doesn’t work for some reason so I go to control panel and do it that way by clicking on the adaptor and changing the ip.

 

[Kayos]

On your w10 laptop are you using the “new” network centre (the one with the windows 10 look) or the traditional “control panel” method (change network adaptor settings). On my work laptop when I’ve tried to use the”new” method it doesn’t work for some reason so I go to control panel and do it that way by clicking on the adaptor and changing the ip.

New method doesn't work, had to revert to old to make it accept the numbers

 

[daleyd]

New method doesn't work, had to revert to old to make it accept the numbers

Glad it’s not just me then….

 

[Kayos]

@skotl

netstat has given me some good information, sshd is listening on 0.0.0.0 but port 22 as expected
Spyserver is listening on 192.168.0.10:5555 but is unreachable from the laptop

There is some issue with the static IP settings, I think the easiest option is a new install and forget the GUI, setup static IP the old fashioned way and see what happens

I am mildly surprised this is a PI issue and not a windows one

 

[skotl]

@skotl

netstat has given me some good information, sshd is listening on 0.0.0.0 but port 22 as expected
Spyserver is listening on 192.168.0.10:5555 but is unreachable from the laptop

There is some issue with the static IP settings, I think the easiest option is a new install and forget the GUI, setup static IP the old fashioned way and see what happens

I am mildly surprised this is a PI issue and not a windows one

Ah. As you probably know, then, listening on 0.0.0.0 is the same as listening on all interfaces. I might still be tempted to edit sshd_config and hard code the static IP to see if that helps.
Were you able to connect directly from the pi to itself: "ssh 192.168.0.??"?

And there's definitely no firewall on the pi? What type of Linux is it running?

Edit: just in case it's Ubuntu or another Debian based distro, it is likely running ufw ("uncomplicated firewall") in which case you also need to type "sudo ufw allow 22/tcp" to allow inbound ssh connections.

 

[Kayos]

Ah. As you probably know, then, listening on 0.0.0.0 is the same as listening on all interfaces. I might still be tempted to edit sshd_config and hard code the static IP to see if that helps.
Were you able to connect directly from the pi to itself: "ssh 192.168.0.??"?

And there's definitely no firewall on the pi? What type of Linux is it running?

Edit: just in case it's Ubuntu or another Debian based distro, it is likely running ufw ("uncomplicated firewall") in which case you also need to type "sudo ufw allow 22/tcp" to allow inbound ssh connections.

Ive setup many Pis (ive also eaten many pies but thats another story) and to get ssh working I have just enabled it in the gui or with the Ncurses setup program

New plan
Install fresh basic os on pi, no gui or xserver
Use ethernet and dhcp to connect to network
Copy details and make network static
Install spyserver and test over network
Do the same on the laptop
Plug laptop into pi
Test

If it works then great, if not I will probably just eat another pie

 

[Kayos]

It was bugging me so I had another 30 minutes of play time and

Success!

It seems all the configuration tools assume even with a static ip you still want to connect to a router and have Internet access, so a bit of .config file editing solved that

Windows will accept whatever you give it, once its happy with the numbers it will change from "no network access" to "no Internet access" at this point it worked

Updates to the Pi will require a bit of messing about but other than that its doing what I want it to, SDR scanning on a laptop far too slow to run an SDR without connecting to the Internet

 

[sako243]

Incidentally you should be able to set the default gateway to the same ip as the device. It will try and look but then find no router service available and just ignore it.

It's pretty common to do that kind of setup on servers. We used to do it all the time at my previous job for our test setups.