IPv4 Upstream Gateway on WAN cause PfSense malfunction
-
Hello.
After some problems with PfSense webgui malfunction finally it seems that I find where my problem comes but I don't know where create the topic about interfaces so here I am.
In a fresh and new pfsense installation If I configure the WAN interface with a Static IPv4 and IPv4 Upstream gateway at the momment that I aply the changes Pfsensestart to through timeouts and it takes more than 1 and alh minute to load the dashhboard page.
If I configure the WAN with static Ipv4 but no upstream gateway then works fine. So the problem is the IPv4 Upstream gateway.
¿Any help please?
-
Where are you trying to access it from?
Are you creating a subnet conflict with an existing interface?
Is there anything logged once you regain access to the webgui?
Steve
-
I have the pfsense connected to a computer directly via LAN. At the moment the appliance is not connected to anything else. Even the WAN port is not connected.
There are only 2 networks.
WAN - 10.50.20.5 /20
LAN - 10.0.0.1 /24I just restored to factory defaults to confirm that there is no other configurations. So I just completed the Setup Wizard the malfuction happens. I change the Ipv4 Upstream gateway to "none" and it resolves the problem.
-
Hmm, odd. Can you connect out from the console still?
Do you see anything logged?
If you connect the WAN so the gateway is valid does it work as expected?
-
I can connect via hdmi and work with console or enable ssh from it and connect without problems.
I connected the WAN to a second network card of the computer with the IP 10.50.20.1 (the IP gateway I have configured as IPv4 Upstream gateway). Now doenst matter if the IPv4 Upstream gateway is configured or not, the problem with loading time persist. It seems a little bit random, but there is one thing sure, the problem is with the WAN interface.
I have to say that I had this problem with 3 different appliances in the last two or three months approx. In fact, I opened some topics before at the IPSEC section because first time that this happend it was configuring some IPSEC tunnels. And was the 2 last days doing some tests that I finally see that doing no previous configuration, just LAN to enter to the dashboard, the problem was origined configuring the WAN.
-
So can I assume there is nothing logged when this happens?
Is it all pages that are slow or just the dashboard, which is what always opens when you first connect?
-
-
Ok, then it;s almost certainly because the firewall it trying to reach out to check for updates etc which it does when you visit the dashboard. You can disable that, and the support status and any other widgets you might have added, if the firewall doesn't actually have internet access.
When it's actually connected to a valid WAN that won't be a an issue.Steve
-
How can I disable that behaviour? Just to try and see if that is really the problem.
-
Remove the support status widget if you have it.
In Sys > Update > Update Settings check 'Disable the Dashboard auto-update check'
-
Good morning.
I disable that option and removed every widget from Dashboard page and the problem persist.
Yesterday I detected that the problem is in this pages aswell:
System -> Register
System -> UpdateToday I switch on the pfsense. As usually the login takes to long. And randomly te Dashboard and System - Register has been working fine some time and after some minutes start to work bad again.
I really don't understand what's going on. If this is caused because the WAN is expecting to be connected to something then in my opinion clearly this is not how should work. Is going to turning mad more than one person trying to configure pfsense with no clue about this problem.
-
Both of those pages also require upstream connectivity so will load slowly without it.
Have you tested it with a valid WAN connection?
-
As I said before, at this moment I dont have the possibility to connect it to any WAN. Im outside the next week so I will try to connect it when I came back. So pls dont close this topic.
-
You can reply here any time. There is no time limit on threads currently.