PfSense itself can't connect to updateserver or ping anything
-
Hello,
my pfSense is running fine with capitive portal. Everthing is like it should be, I can use internet from the LAN side. From my PCs, to stuff like my Playstation and all guests how are using the capitive protal function, everone can use the internet.
The only problem is, that the pfSense cant check for updates and when im trying to ping the update server or use tracert from the pfSense, I cant reach any server in the internet.Does someone has a idea what I should check?
Best Regards,
Flico -
How is your network set up ?
The captive portal is on its own dedicated interface (OPT1 - which is as it ment to be) ? Or did you activate it on the LAN interface (special considerations are needed then, so that is not advised - this is an "expert-only" possibility).
Of of these is: Enter the LAN IP of pfSense on the "Allowed IP Adresses" otherwise even pfSEnse can't get out … which explains why 'updates' times out. -
in the register "Captive portal(s)" -> "Interfaces" its set to "LAN". (Is this not the way to go?)
I only have 3 interfaces LAN and WAN1 / WAN2. Both WAN Interfaces are connected to a seperate DSL Router with load balancing.
I added now the pfSense LAN IP to the "Allowed IP Adresses" but that alone was not the solution. :-(
-
CP on LAN => bad idea (TM).
-
why?
-
:)
See question in #1 en a (partial) explanation in #2.
Portal Interface => Give it a dedicated (5 $ NIC) interface - and live will be simple."System Admins" always put up "simple" systems because they are easy to maintain and understand.
Complicated, of-standard systems aren't tested thoroughly - so never used. At that moment, getting advise gets difficult.
Believe me, a pfSQEnse box with 3 (or more !) NIC's is easier.
You have your WAN
Your save internal LAN
Your visitors OPT1 = Portal Interface.
…. and live is easy. -
My Box has 3 interfaces but they are all in use. I have LAN, WAN1 and WAN2 because the pfsense uses 2 DSL lines.
