Missing default route (and more after upgrade..)
0tt0 last edited by
Had this install of an older version of pfSense (2.0 or 2.1) running for 2-3 years without a single issue. This is a stand-alone guest-type of network that gets private address to WAN via DHCP.
Then all of a sudden I had a network problem and people couldn't access the Internet and after some time and to my surprise I found out that the default route was missing, wasn't really the first thing I looked for..
Anyway I wrote it off as a freak occurence since I had never heard of this type of problem (in any FW I worked with to be honest).
Anyway after that event and after a number of months the same error appeared again. And again. And again; now it has dissapeared from the routing table 2 days in a row. I reboot and it goes back in.
Since this was at first an older version I triggered an upgrade. There were some errors during this process, didn't have time to note them down thogh and when it was finished it landed on 2.3.5 and appeared ok at first glance.
However now another issue emerged - the captive portal stopped authenticating users, there was errors complaining about voucher lenghts (see pic - I attach all info here instead of making a new topic since the captive portal issue is only part of the problems now). There is mentioning of some SQLite3 class and missing info in config file.
BTW: Yet another thing I noticed that possibly have changed is that the server pushes the UTF8 type in the reply for the portal page, even though it is NOT ("charset=ISO-8859-1"), which makes the page look like shit in browsers. Why?
When testing a valid voucher it complains about lenghts, like if some config has been altered, which I have not done.
It seems no authentication works at all, neither voucher nor local user can log on through portal page. MAC whitelist work though.
I guess the upgrade failed somehow then, the system has no installed packages and never had.
Now on to what I started with, I upgraded in the hope of getting rid of the missing default route issue but that is still there after upgrade too. The last two days this has happended and I'm not sure what to look for. Anyway this seems odd, shouldn't the route info be present when it is somehow rewritten or is it explicitly deleted. What to look for? I guess some kind of event, possible interface related is triggering something that yields this error. I have no info suggesting the DHCP server is serving incomplete info.
So, to summon up:
. had issues with all of a sudden dissapearing default route in 2.0/2.1 install after several years of flawless service
. after upgrade to 2.3.5 the captive portal stopped working with authentication
. Also in 2.3.5 the missing route problem still exists.
I could use some pointers in order to be allowed to continue to use pfSense in this particular network.
These seems somewhat similar, relating to the route issue:
Version: 2.3.5-RELEASE (amd64)
![2017-11-28 default route missing.png](/public/imported_attachments/1/2017-11-28 default route missing.png)
![2017-11-28 default route missing.png_thumb](/public/imported_attachments/1/2017-11-28 default route missing.png_thumb)
![2017-11-21 Status_ Captive Portal_ GUESTS_ Test Vouchers.png](/public/imported_attachments/1/2017-11-21 Status_ Captive Portal_ GUESTS_ Test Vouchers.png)
![2017-11-21 Status_ Captive Portal_ GUESTS_ Test Vouchers.png_thumb](/public/imported_attachments/1/2017-11-21 Status_ Captive Portal_ GUESTS_ Test Vouchers.png_thumb)
![2017-11-21 Status_ System Logs_ System_ General.png](/public/imported_attachments/1/2017-11-21 Status_ System Logs_ System_ General.png)
![2017-11-21 Status_ System Logs_ System_ General.png_thumb](/public/imported_attachments/1/2017-11-21 Status_ System Logs_ System_ General.png_thumb)