Unable to ping between lan and opt
-
@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 -
@johnpoz It didn't get a gateway either
Edit: just checked. Lan is asigning a default gateway, opt isn't -
@bgksdfol and this windows machine wasn't setup for a reservation, it would just get IP out of the pool..
And in your normal dhcp settings for gateway - it is blank as well, you don't have say none in there? Or maybe a space? Wonder if that could mess it up?
Your running 22.05 or 2.6 on this sg1100, your not running some snapshot or dev version?
-
@johnpoz
It just gets allocated a static ip by the router.
The space in gateway is blank
22.05 release
In some way this is validating that I wasn't going insane, and really was banging my head against the brick wall for a month. -
I know that this isn't a satisfactory answer, Re-imaging the firewall resolved the issue.
-
@bgksdfol whatever works - sometimes starting clean is a faster solution. While its more satisfying to know the actual root cause off the issue.
Something was messed up that is clear, out of the box pfsense would hand out its IP on any interface as the gateway to dhcp clients, and also dns.. Unless you edit the dhcp server settings to do something different.
