Help from network people

[Kayos]

I need to do something I thought would actually be quite simple, connect a PI4 to a Win 10 laptop with an ethernet cable, but its proving rather difficult with the Win 10 settings

I can set the Pi to have static IP but the laptop is insisting on a default gateway when I do the same, but I do not know what to put, everything I try doesn't work

In this configuration neither device will have wifi active or be connected to the internet, all they need to do is talk to each other and play nice

I am giving them simple IP's like 192.168.1.10 on the laptop and 192.168.1.20 on the PI, is this correct?
Also do I need a crossover cable? I have one but thought they were unnecessary these days

Any help on the settings from people who understand the dark art of networks?

 

[growntree]

Yes, you'll need a crossover cable to connect directly from computer to computer. Just put the raspberry pi ip address in for the default gateway on the windows 10 pc. 255.255.255.0 will do for the subnet mask.

 

[Kayos]

Yes, you'll need a crossover cable to connect directly from computer to computer. Just put the raspberry pi ip address in for the default gateway on the windows 10 pc. 255.255.255.0 will do for the subnet mask.

The machines will not ping with the settings suggested with a crossover cable or a straight cable.

Plus everything I can find, as far back as 2013 says crossover cable on a Pi isn't needed as the ports auto negotiate

 

[growntree]

A bit more information...
You could also just leave the windows 10 pc on dhcp and it'll just pick its own ip address and just add 1 to the last bit and use that as the static on the pi.
Modern switches, guns and routers do the auto crossover for you, but network cards in computers don't which is why you'll need the crossover cable.

 

[Kayos]

There are no routers or anything or a DHCP server, just the laptop and the PI

According to the PI4 book I have it does not need a crossover cable so either I have a pile of faulty cables or I am doing something wrong, the second option is more likely as neither type of cable works

 

[ajlelectronics]

Gateway is your router address and then connect both devices to the network in the normal way. Check that the static addresses you have chosen cannot be used by the dynamic pool. Net mask is 255.255.255.0

 

[growntree]

The machines will not ping with the settings suggested with a crossover cable or a straight cable.

Plus everything I can find, as far back as 2013 says crossover cable on a Pi isn't needed as the ports auto negotiate

I hadn't heard that about the pi, but if it auto negotiates then a crossover will still work.

Check windows firewall as it may well be blocking the ping and allow connections on your local network.

 

[ajlelectronics]

There are no routers or anything or a DHCP server, just the laptop and the PI

According to the PI4 book I have it does not need a crossover cable so either I have a pile of faulty cables or I am doing something wrong, the second option is more likely as neither type of cable works

Why not just connect it into the network? That has to be easier.

 

[Kayos]

Why not just connect it into the network? That has to be easier.

It will be a standalone setup

Basically the PI has an SDR connected and is running as a server, the laptop has the SDR software running

In normal use it is done through the network but when I am out mobile there is no network to connect to

And don't try making sensible suggestions like plug the SDR into the laptop, the low power, lightweight machine I use for it simply can't cope, hence using the PI to do most of the work and the laptop to control it

 

[EM1L4]

Pi setup:

192.168.0.10, DG- 192.168.0.100, Mask- 255.255.255.0

laptop

192.168.0.11, DG 192.168.0.100, Mask- 255.255.255.

it won’t need a DG, as it will be talking directly to the Pi, so it doesn’t really matter what IP you put…

Geekfo: The Default Gateway is for accessing networks (such as this website) outside your LAN. It so the device know’s who it needs to talk with to get the external network, your router (if you were using one) would typically be the DG, as it has access to the WWW and can communicate with networks outside tour LAN

++ Crossover cables are rarely required for modern devices….

 

[julianf]

Yes, you'll need a crossover cable to connect directly from computer to computer.

I won't pretend to really know this stuff, but I'm not sure the above is correct.

It was in the past, but I think that anything manufactured in the past decade or whatever will be auto sensing. Ie the port will configure.

I'm running two machines here in that configuration and was not choosy about the cable at all.

 

[brewdexta]

@Milo1 is correct. The default gateway address doesn't matter, but it has to be in the same network as the device or it will complain, so with an IP of 192.168.0.11 with a mask of /24 or 255.255.255.0 (same thing, 255 = 8 bits, so 3 x 255 = 24 bit mask) then the permissible DG can be anywhere between 192.168.0.1 to 192.168.0.254. so 192.168.0.100 as Milo1 suggest will be fine.

 

[Kayos]

Still not working but it accepts @Milo1 settings

Ping Pi from laptop and get a timeout
ping random IP from laptop and get "Destination host unreachable"

Ping laptop from Pi and get "network is unreachable"

Turn windows firewall off, same results

 

[gaz1]

 

[Kayos]

Windows version of Nmap can find the Pi but not get anything from it, not even detect the unusual open port

Maybe this is an issue on the Pi, not the laptop?

 

[EM1L4]

Still not working but it accepts @Milo1 settings

Ping Pi from laptop and get a timeout
ping random IP from laptop and get "Destination host unreachable"

Ping laptop from Pi and get "network is unreachable"

Turn windows firewall off, same results

On the pi open a shell window and type “ip addr show” does that match the suggested settings? If it does open a command promt on the latop and type “ipconfig” and see what it says for the ethernet adapter…

a reboot maybe needed…

 

[EM1L4]

Windows version of Nmap can find the Pi but not get anything from it, not even detect the unusual open port

Maybe this is an issue on the Pi, not the laptop?

Ahh,

so you can ping it, have you enabled ssh on the pi?

 

[Domdom]

Things to check.
Windows firewall, worth disabling the windows firewall service completely.
Check the ARP tables. Command prompt, arp -a and see if you have the mac address of the Pi in the table. If you don’t then you have a physical problem for sure.
Try connecting both devices to a small unmanaged switch, even an old DSL router with a built in switch would do. Same tests and you should see a mac address relating to the switch.

Make sure the physical layer is working before the network layer.
physical - cables and interfaces at the physical layer
Datalink - MAC addresses, sometimes called Layer 2
Network - IP layer

 

[Kayos]

Ahh,

so you can ping it, have you enabled ssh on the pi?

Cant ping it with ping
SSH is enabled, tried to ssh in with no joy

everything is as expected only thing I haven't set but is showing on the Pi is "broadcast 192.168.0.255"

 

[mike os]

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