If anyone has had this issue - updating to the release version of 21.02.2 seems to have fixed it! I think it's related to this reported ticket: Regression #11436 Will report back if I see any further related glitches.

@pfgate said in pfSense 2.5.1 Announcement, Release Notes, Installation Instructions: I see that 2.5.1 is available in the GUI. I've poked around a little and can't find an announcement, any release notes, or installation instructions. I'm new here so I'm likely not looking in the right places. RedMine now shows 2.6.0 items on the roadmap page. Are 2.5.1 items now on a different page? Wonder if the News and Documents pages in RedMine might be a place to publish announcements, release notes, and installation notes. https://redmine.pfsense.org/projects/pfsense/roadmap I have 2.5.0 and have set up two WireGuard peers, with pre-shared keys. I think I read that I'd have to delete/disable the WireGuard server before upgrading to 2.5.1. That correct? Hi, maybe this is the right pace :) https://www.netgate.com/blog/pfsense-plus-21-02-2-release-and-pfsense-ce-2-5-1-release-now-available.html

@jimp OK, thanks for letting me know, I know you guys must be busy at the moment sifting through any possible bugs being reported. Thanks for the speedy point release, you guys must have been working hard, wasn't expecting to see it so quickly.

@gertjan said in Troubleshooting new pfsense 2.5.0 installation: the x.x.x.10 and x.x.x.20 are switch together Yes, both are switched together

@danielino1981 said in Multiple LAN on Pf Sense: I don't want the VLANs If you don't want to use VLANs, you'll need a separate interface for each LAN. The Qotom comptuer I use has 4 Ethernet ports, so I could have 3 LANs without using VLANs.

@gertjan Thanks

if you run status > filter reload does it fix it? i have had that issue consistently on 2 different Netgate products

@72zoea said in Button to turn off internet for a group of devices: to quickly turn off internet Login to pfSense. Goto Firewall => Rules => LAN. Click on the [image: 1618387747203-70e8a4ea-e703-4545-91ec-563f181862c5-image.png] symbol, and then the green Apply. so, 5 or 6 clicks ..... as pfSense uses a GUI. You have to create a firewall rules that uses an alias as a source. The alias should contain the IP(s) to be block. Enabling or disabling this rule will do what you want. Btw, I do recall that there are other ways to learn how to clean up after tea. I was a kid before ^^ ( and there was no Internet during the vast majority of existence of mankind )

@nibblet said in New installation and packages.netgate.com issues: @teamits Ahh, thanks for that, that helps a lot, altho now I am left with an interesting pickle on how to solve this, as I don't believe the proxy server is clever enough to look up a SRV (it only sees the http request) record and there is no external DNS. However, I could probably setup an internal 'dummy' netgate.com domain with SRV records mimicking what's outside which may be enough to poke the firewall to pickup the right domain, the issue would be somehow keeping this up to date. At least I know why its not working now :-) how you solve this problem? thanks

Perfect .. that helped immensely .. Thank you!!

@tbaker9595 I'd be a bit skeptical you'd get that much throughput on pfSense...check the XG-1541 vs the same device list with TNSR here, particularly the "TNSR vs pfSense Software" button/tab.

@papdee Yes, I've seen that video already, thanks. I understand your latter point thanks for making that clear.

@papdee said in Bandwidth loss through pfSense firewall built on old dual homed PC?: maybe try using CAT6e That won't make a bit of difference. Gigabit Ethernet was designed before there was even CAT 5e and is rated for 100M over plain CAT 5.

@gertjan My iPhone is using DHCP. I have set DHCP reservations on the pfSense side. I push DNS server through DHCP to the clients and have setup a NAT rule to redirect all DNS traffic which does not go to the Pihole to redirect to the Pihole. What I meant with the above post that I changed DNS (and removed the NAT redirect rule) as a test. To filter out where the problem relies.

Thank you.