@jrey I only looked because I was expecting it to comment out the periodic daily line but it didn’t. Then it rewrote the file at boot, still I commented, so I pulled up the patch details. no memory spike the next day so it must have worked.

Perhaps crontab write triggers again at other criteria?

@derelict Thanks for pointing this out - we hadn't had a rule on the previous version but added it in before the gateway rule and all is working OK again.

@viragomann

I found the culprit, why it only has been on this one unit, I cant explain. It was being blocked by Snort..

140:20
(spp_sip) Invite replay attack

Disabled the rule and it has resolved fine. All 4 units run Snort, only this one has had an issue.

Thank you for your help.

John

@steveits thank you for the reply, I'll try finding the docs :)

@eddie-raydian said in Fatal trap 12: page fault while in kernel mode after upgrade to 23.01:

@fsc830 first of all, this is not helpful and disrespectful to all users on the forum. If you cannot provide help or good feedback, I think we can all agree that it you should not post.

Second of all, asking, if a backup (or in case of VMware a snapshot) is available is a legitimated question to think about further steps.

Cant see, why this should be disrespectful.
But as you desired: I will not post to any of your questions again. 😎

@chpalmer Thank you, that helped for me :-)

Everything is now LIVE.
When I was out, I decided to try the site(s) and see what I got while totally away from the office, and I got the site but with a non-working SSL. OK, Good.
So, when I got back to the office just a few minutes ago, I grabbed the SSL cert I had installed the other day before creating the SSL through PFSense, and everything is working.
All sites are LIVE in front and behind PFSense.

Thank you, everyone, for all the help.
Have to say this community absolutely ROCKS!!!!

All the information to get the site(s) live was from this thread here, with the link(s) provided and the link(s) I provided.
So, if anyone has this same issue, all you have to do is follow everything from start to here, and you should be good to go.

I've tried to notate everything I had to do, so I can write an article for our Knowledge Base site.
Love sharing and exchanging knowledge.

@saqqara I don't have two LAN interfaces with the same IP address. The original is 192.168.1.0/24 and the new one is 192.168.2.0/24. But, with the spacing in my OP, it's a bit hard to see. I'll edit that to make it clearer.

BackupLAN is simply a backup interface. I recently lost access to my whole network (not just the internet) and one line in my logs implied there was a problem with the LAN interface that wasn't cleared by a reboot of the device. This is just something I can try if it happens again (to see if it's actually a problem on the LAN interface or something else).

@mer Well sadly, I am going back to 22.05. I am having too many DNS issues with Unbound (I've been posting in the pfSense and pfBlockerNG forums about this).

Any DNS queries for entries not (or no longer in) the cache are really slow. It causes my browsers to lag, app updates to fail, and worst of all: overnight backups are failing.

I'm just glad I ensure I have the previous good release + config file on a USB stick. I'll be repaving (and perhaps upgrading to ZFS in the process) in a few days. Can't take the network down without some notice...

@michmoor
I have two spare HP T730 boxes: one with the same Broadcom 5719 NIC and the other with Intel pro 1000. I tried using both but I am getting the same issue.

Furthermore, I have also tried disabling hardware offload with absolutely no effect.

The weird thing is that I am using a similar setup at my home with the same ISP with a broadcom NIC and that works fine

I have noticed that it usuallyt happens when the ARP entry for WAN gateway refreshes i.e. around 1200 seconds

Hi @stephenw10 , yes, they had external access only and were scanning the IPs. As you say its likely their scanner came back with "FreeBSD firewall" but no specifics. If I can get more details of what the scan actually found I'll post it, but I'll continue to work on the upgrade and ask for a re-scan when complete.

@vusq2023 said in netgate 1100 wifi setup through isp router/modem:

wifi connection through my isp router/modem

Sure. Note that will put the Wi-Fi clients outside your pfSense.

@vusq2023 said in netgate 1100 wifi setup through isp router/modem:

use the opt port for now to run another ethernet connection

Do you mean on the same network as LAN? Yes Netgate has instructions for removing the VLAN setup to do that. Otherwise sure you can plug something in and that will be a separate interface.

Yeah having servers and clients makes things confusing. A server running on TCP port 443 is going to see those packet size errors because https connection attempts if it's open to any external IP.

We probably need to see the OpenVPN logs from the client then. Ideally at the point it tries to connect but fails to pass traffic.

@troubleshooting74 said in synology agent:

pfsense where i'cant install agent

They have a agent for freebsd? I would find that surprising to be sure..

https://www.synology.com/en-ca/support/download/DS918+?version=7.1#utilities

I don't see a freebsd agent, only windows linux and mac

agents.jpg

Pfsense is not linux, it is based off freebsd - there is a difference between that and linux.. To have any hope of running the agent on pfsense you would at min need a agent meant to run on freebsd.

I think I have fixed it.
Since I've added to pfsense to see my ISP's router interface, I had to change the default gateway from auto to the proper gateway.
So far it seems to be working as it should!

@stephenw10 said in If Internet Down, Can't Get to pfSense Box?:

Perhaps when the WAN fails the modem creates an IP in the LAN subnet.

His cable modem uses 192.168.100.1, and the pfSense LAN is the default 192.168.1.1, so that can't (shouldn't) be the issue.
If pfSense obtained an 192.168.100.x from the cable modem as a pfSense WAN IP, this would break 'internet' access. But this shouldn't stop indefinitely the access to the pfSense GUI. There will be a delay, though.

Also, when WAN connects, "all hell breaks loose".
I mean : when you use the console access, option 8 (command line) and we tail every log file on the system, like :

tail -f /var/etc/system.log /var/log/resolver.log /var/log/dhsp.log etc etc etc etc

me you everybody will know what I mean. Thousands of log lines will show up an this is 'normal'.

Even the GUI web server is restarted, as it wants to listens to WAN.
If there is a stupid modem upfront that takes it time, or the upstream ISP DHCP server is somewhat slow, the creation of a working WAN connection can be slow.
During all this time, pfSense tries also to update some data that it want to get from sources on the Internet, like the package info and the current time (etc), then a delay is easily explained.

But again, eventually, it should show up.

That's why I proposed to go directly (enter it in the URL line of your browser) to the - not dashboard page - but another page like
http://192.168.1.1/system_usermanager.php as that page only needs local resources to get build.

@stephenw10 Yep its 10 years old.