pfSense can not access to the internet
-
What is actually set as default though? Here:
The current default shown in the table is invalid. re0 is not the WAN
-
This post is deleted! -
@stephenw10
Actually, re0 is for my LAN, and my primary WAN is on bge0 with METRO as its name. I select METRO for my default gateway IPv4
How do you think such a mistake could have happened in the routes list?
-
@vahidmoghadam
Did you state a gateway in the LAN interface settings by any chance? -
@viragomann
This is a shot of my LAN interface settings:
-
@viragomann @stephenw10
Really It's like a joke!!!!!!!!
Now, I click on the Save button on the LAN interface settings page. Without any change of values.
and the default route changed to bge0 on the routes list and the internet is coming into vessels of the pfSense.
It's really funny, It took about four hours of my time.Thanks so much. With your guidance, I was able to understand and solve the problem.
-
You have that labelled IPSec_GW so I assume it's for the IPSec routing workaround?
It still shouldn't be on the LAN interface directly like that. That makes pfSense treat LAN as though it's a WAN.
But it still shouldn't ever have selected it as default if you have METRO_GW set specifically.
If you remove the gateway from the LAN interface config and resave the gateway settings page with Metro as default it will re-add the correct default.
-
@vahidmoghadam Why do you have a /23 set on your LAN? It would be normal to have it as a /24.
-
Not that unusual to have more than 256 devices on the subnet. Or just to make numbering more logical etc
-
@Misterb
We have about 80 access point and about 40 printer and also about 100 desktop pc and there are number of laptops that using LAN, also devices on server room and many other small devices that all of them using from this address pool. So we need to have 512 (/23) address.Maybe in the near future I will have to increase it to 1024 (/22) addresses.
-
@vahidmoghadam Fair enough.
