Unable to ping between lan and opt
-
If a client device cannot ping its gateway then try another client device in its place. If that device can ping its gateway then you have ruled out your router as the problem.
If that new device still cannot ping a gateway then you can figure a configuration issue on your router.
-
@bgksdfol said in Unable to ping between lan and opt:
pi mask is 255.255.255.0
And is the gateway correct?
-
@bgksdfol It can ping its gateway, but not the gateway of the other lan port on the router
-
@johnpoz It is 0.0.0.0 so I am going to assume not
-
@bgksdfol said in Unable to ping between lan and opt:
It is 0.0.0.0 so I am going to assume not
That would default destination - but the IP, ie the gateway is what when you do a route -n
See my above screenshot from my pi..
My gateway is 192.168.3.253, which is pfsense IP on that vlan. if you don't your gateway pointing to pfsense IP on this network, then no your never going to ping anything off its network, nor would you be able to answer anything coming from another network.
-
@johnpoz The Destination is 40.0
Gateway is 0.0.0.0
mask is 255.255.255.0How do I correct the gateway?
-
@bgksdfol why don't you just set the pi to get its IP via dhcp?
Pretty sure that is the default, if you want your pi to always have the same IP - you can just easy set a reservation in pfsense dhcp server. Is that what you did and you put in some gateway there?
-
@johnpoz So the pi is getting a static ip from the OPT dhcp server. I am not sure how to set a gateway in the DHCP server
-
@bgksdfol so you setup a reservation there.
so for example here is reservation for my pi
The gateway should be left black, so it defaults to telling the client to use the pfsense IP on that network as its gateway. Did you put something in there? like 40.0 ?
-
@johnpoz The gateway field is empty on both the lan and opt dhcp server
-
@bgksdfol well then something wrong with your pi - if you plug in a laptop or pc to that network do you get the correct gateway?
Can we see the output of your route -n?
destination of 0.0.0.0 is correct for default route.. That should have gateway pointing to the IP address of pfsense on this network, which I take is x.x.40.1 (btw there is zero reason to hid rfc1918 space..
If your gateway says its 40.0 then that is wrong, but I don't see how pfsense would of handed that out?? You could of maybe overridden the dhcp settings on the pi?
Notice my output from above - gateway of 0.0.0.0 is correct for the local network, in my case 192.168.3.0..
default route (destination) 0.0.0.0 points to my pfsense IP 192.168.3.253 on this network.
the route to get to the network my pi is on 192.168.3.0/24 (see the mask 255.255.255.0) would 0.0.0.0
-
-
@bgksdfol
I read recently a post here, where a Pi didn't obey the gateway from the DHCP server.
Try to set it static.
Found this: https://raspberrypi.stackexchange.com/questions/57655/fixing-gateway-on-dhcp-connection-raspberry-raspbian -
@bgksdfol ah - yeah never going anywhere without a default gateway.. Never had any issues with my pi's have run many of them over the years currently 2 of them running..
What OS are you running on them?
Mine are both running
pi@pi-ntp:~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" pi@pi-ntp:~ $haven't looked at @viragomann link yet - but that might have a work around..
-
@johnpoz said in Unable to ping between lan and opt:
Mine are both running
Debain 7 (wheezy)
It is an old raspberry 2 -
@viragomann This didn't seem to change the route
-
@bgksdfol said in Unable to ping between lan and opt:
This didn't seem to change the route
You didn't have a real route before, you only had your the own subnet connection on the Pi.
Can you ping the other pfSense interface IP now? And also the devices in the other subnet?
-
@bgksdfol you should be able to manually add the default route with that command given in the link.
Taking a look here
https://www.raspberrypi.com/software/operating-systems/You should be able to run the 32bit version of bullseye on any pi.. now I am trying to remember why I didn't update to bullseye when it came out??? I think it had something to do with the gps ntp server running on one of them.. But why didn't I update the other one??
Hmmm - guess I got something to do tmrw ;) Maybe next weekend, I don't think I have any spare sds laying around.. That is why prob didn't do it, and just never got around to ordering them.. I got them setup exactly how I like, so like having a backup on sd so can just put the backup sd in and get back to exactly how I was..
-
@johnpoz said in Unable to ping between lan and opt:
You should be able to run the 32bit version of bullseye on any pi.. now I am trying to remember why I didn't update to bullseye when it came out??? I think it had something to do with the gps ntp server running on one of them.. But why didn't I update the other one??
I don't think it is the pi. I just swapped the pi out with a windows machine, and the windows pin timed out.
Is there something beyond setting the allow all firewall rules I should have done? -
@bgksdfol said in Unable to ping between lan and opt:
Is there something beyond setting the allow all firewall rules I should have done?
No - your saying your windows machine didn't get an IP from dhcp at all, and ended up with 169.254.x.x address - or did it not get a gateway either?
In windows you can look with ipconfig -all
$ ipconfig -all Windows IP Configuration Host Name . . . . . . . . . . . . : i9-win Primary Dns Suffix . . . . . . . : local.lan Node Type . . . . . . . . . . . . : Broadcast IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : . Ethernet adapter Local: Connection-specific DNS Suffix . : local.lan Description . . . . . . . . . . . : Killer E2600 Gigabit Ethernet Controller Physical Address. . . . . . . . . : B0-4F-13-0B-FD-16 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.9.100(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Thursday, February 2, 2023 10:45:14 PM Lease Expires . . . . . . . . . . : Monday, February 6, 2023 10:45:14 PM Default Gateway . . . . . . . . . : 192.168.9.253 DHCP Server . . . . . . . . . . . : 192.168.9.253 DNS Servers . . . . . . . . . . . : 192.168.3.10 NetBIOS over Tcpip. . . . . . . . : Enabled
