@PerfectBake420, The issue you are having CANNOT be fixed without upgrading both the Server and Client side Internet to a minimum of 100 x 100. Your upload speed needs to be just as fast as your download speed at both locations. This is the nature of QuickBooks and not a problem with your VPN. Intuit has something called the QuickBooks Database Manager that runs on the Server hosting QuickBooks. However, don’t confuse the “QuickBooks Database Manager “ with something like SQL. The QuickBooks database may as well be a “flat” file. This means every time you access QuickBooks from a workstation it is taking all of the QuickBooks files on the Server and passing them over the network to the workstation. There are four QuickBooks files that are involved with one company file. They are the QBW, DSN, ND, and TLG files. Combine the total size of all those files and that is what has to pass across the VPN. Obviously, things probably work well within your LAN because you most likely have a Gigabit switch which is 1000 x 1000. There is NO WAY you can make this usable for an end user without very fast bandwidth, in both directions, at both sites. An alternative would be to setup another workstation at your office (a VM perhaps). Install QuickBooks on that workstation and have the user log in via Windows RDP to that workstation across the VPN. OR, if QuickBooks Online is a viable option you could migrate to it and pay the monthly fee. Unfortunately, I know a ton about setting up QuickBooks and it’s something I’m not proud of. There is a saying in IT about QuickBooks. It goes….”I don’t know why they call it QuickBooks, cause there is nothing quick about it.”...at least from an IT standpoint.

@mccann25 I think we are having the same problem. I only have 1 DNS Resolver 127.0.0.1 -- I didn't get the Bad Gateway message, but I likely didn't wait long enough.

It's possible the hardware problem started from the reboot during upgrade and not from anything in 2.5.2. You'd be surprised at how many hardware issues only start or get noticed after a reboot, and then seem to coincide with an upgrade as a result. But there isn't a lot to go on to say with any certainty what the cause might be. Are those logs in reverse order with the newest on top? It appears that way. Normally that kind of log message about a NIC only happens from a hardware event (e.g. cable is unplugged).

@imburr said in Firewall *Stops* and Break in Logs For Extended Time: @bmeeks Very interesting! The work PC is connected via ethernet to a 8 port switch, which then has one homerun into the main 24 port switch, which then has one ethernet cable going to LAN on the pfSense. I cannot see for a way for it to be a physical loop, can a loop still happen in this instance, due to some misconfiguration or software issues? Most often I've seen network loops created by plugging one port into another on the same switch accidentally. It's also possible for something like bent pins on an RJ45 connector, or a faulty cable with an internal short, to cause a loop. It's just that a completely dead network where all devices on it seem "frozen", only for everything to return to normal when you remove, or power down, one device, is strong evidence for a network loop of some sort caused by that device. In your case, that seems to be your work PC. I would start simple by replacing the Ethernet cable for the work PC. Next, take a flashlight and carefully examine the pins inside the RJ45 Ethernet port on the PC's network connection. Look for two pins touching, or any that seem obviously bent or damaged.

Yes, I thought more people would have been seeing it given that I did. I queried it internally though and no-one else was having an issue. And then subsequent requests to the repo went through no problem. Perhaps I happened to catch the end of the issue. Steve

@rocket-0 With the Netgear modems you should not have to spoof at all on Comcast's Xfinity service. Simply rebooting the cable modem should be sufficient. Have you tried this?

@f3rn3po Ctrl+c

@cyberneticcody Can't edit for some reason... PFSense version is 21.05-RELEASE

Quick update, have narrowed down to /var/unbound/usr/local/lib/python3.8 Shell Output - df -hi /;du -s /var/unbound/usr/local/lib/python3.8; df -hi / Filesystem Size Used Avail Capacity iused ifree %iused Mounted on /dev/ufsid/5cdd3c209fe36da7 7.0G 2.0G 4.5G 31% 27k 935k 3% / 274800 /var/unbound/usr/local/lib/python3.8 Filesystem Size Used Avail Capacity iused ifree %iused Mounted on /dev/ufsid/5cdd3c209fe36da7 7.0G 1.4G 5.1G 22% 27k 935k 3% /

@gertjan said in Test email has no hostname?: @incith Locate : function saveAdvancedNotifications($post, $json = false) { global $config, $smtp_authentication_mechanisms, $pushover_sounds, $g; in the file /usr/local/pfSense/include/www/system_advanced_notifications.inc and add, as shown, a $g and save. Just wanted to say thanks for this!

@tagit446 i solved this problem, i realized that the NTP server wasn't working properly so i turned it off and seted the time and date manually by console. problem solved!

@brucexling exactly! Any book you buy is going to be outdated very quickly - even if just published a few weeks ago.. The living document is best resource..

@stephenw10 hello stephenw10, sorry for the delay i was not at the office for testing. I feel so stupide to haven't think about that alone, you were completly right as soon as ii changed serial to vga i could see all the boot. i steel have a lot a difficult to access my web interface cause it take ages to change page, i suppose it's because i have only one router with the Ha and no internet cause the old routeur is still in production. i suppose that the fact the the routeur hang several minute on ipsec when booting is du too that cause too. i will switch the routeur next week if everything is ok. Anyway thanks a lot for your help. have a nice week end

@bjurkovski said in Upgraded from 2.4.5 to 2.5.2 and having problems with config file restore on every reboot.: I wouldn't have had this problem if I had just disabled Python mode in my config before reinstalling I think this should get pinned because I run in this trouble too: If in the config, before reinstalling, the pfblockerng was in python mode then unbound is not working (he is missing the python module) and no packages can be installed because Url's cannot be resolved. So switching pfblockerng in unbound mode before save the config is the best way to workaround this issue. Regards, fireodo

@provels You're right. I noticed the issue again. After reloading Dashboard tab the scale was back to correct again. Here's screenshot before that (Left: Dashboard, Right (ok): Status/Traffic graph) [image: 1626332654403-fd08a016-fdb5-4465-90a3-c545ae435e38-image.png]

Finally I found solution on: https://forum.netgate.com/topic/164732/python-regex-list

@johnpoz There are some ips which do not resolve as they are out of dhcp range and not static or the device doesn't tell a hostname. But almost all ips resolve proper. If domain override exists with the lookup server pointing to itself, it causes the problem. Guess pfsense gets into a loop "ask itself many times" for the entries it can't resolve.

Hi, @Gertjan and @stephenw10 Thank you for your answers. Regards