@johnpoz: Don't tap either.. Use TUN… So you smited me for that - really??? There are reasons for doing this, for example being to Steam In-Home stream from a distant network using a VPN. Just because it's not the most sane thing to bridge ports on a router doesn't mean there aren't valid use cases, so don't just smack down people for doing so. There's a reason they are in pfSense. In my network I have a 10GbE card in my router and workstation, which are bridged to a bonded fiber port to my switch for the rest of the network, and a similar situation for my file server. I don't have $500 - $1k sitting around for a fancy 10GbE switch, so pfSense does my heavy lifting until I can get my hands on that beautiful Unifi 16 XG @MrClayPole: So are bridges not supported on pfSense? They are, but are not suggested due to things like this, and it requires your router to interact with the packet which is slower than the in-hardware stuff traditional switches have. Hopefully this is patched sooner than later, but for now stay at an older version of pfSense if you need router advertisement and IPv6. I use bridges just fine, aside from the issue in OP's post.

Downloaded a fresh image, installed from USB and all is fine now.

Thanks, I'll go with the quad ethernet card then.

I tried many variations of "pfSense 2.4 gmirror" (and raid, mirror, etc) in Google and they all pointed to relevant threads here that mentioned using ZFS instead, including this thread which was at the top of most of the results. gmirror is inferior to ZFS, and it was more trouble to implement gmirror all over again than to use ZFS which was already in the new installer.

Thanks for the info. :( :o

Thanks KOM, I have created a ticket here. I fully expect to get shouted at though :) Thanks for your help.

Hi Vodafone fiber in Portugal connects to a GPON device ( in bridge mode) using DHCP in Vlan 100 for data, DHCP Vlan 101 VOIP and DHCP VLAN 105 for IPTV. The default router info is 192.168.1.254 router IP, vodafone/vodafone for user/pass.

2.3.x is based on FreeBSD 10.x, 2.4.x is based on FreeBSD 11.x, so lots of changes in between. It's possible your hardware or BIOS config doesn't like the 2.4.x memstick since it supports UEFI. There may be some option you need to change in the BIOS to work around that, or perhaps a BIOS update. You can, however, install 2.3.5 and then update to 2.4.3 from there if all else fails. Another suggestion, ditch Rufus and use Etcher.

You don't need to have any NAT rules at all if you don't want/need them. The default settings will NAT all traffic from the LAN subnet to the WAN IP address and that should work there. You will have an asymmetric route if the LAN side WIN7 client is not using pfSense as it's gateway. Depending on what the Win server box is doing it may block traffic. Steve

There are a number of threads on this. Depends on your setup as to how you upgrade. Most I've seen (and had to do) involve being physically connected to upgrade via console. Searching…. https://forum.pfsense.org/index.php?topic=109370.0

Hi to all, I have used pfsense on two apollo lake setups. My first apollo lake setup was an ASROCK mATX J3455 with two additional NICs and a Draytek VigorNic 132 occupying the expansion slots. I had no problems before the hpet bug. The setup was basic intended for home use. The hpet bug hit me after update and made the system unbootable. After reading the forums, I managed to successfully install (safe mode, loader.conf etc) a fresh 2.4.3 and setup a working firewall. I didn't notice any high CPU usage, but as I wrote it is a basic setup. I replaced the setup with another apollo lake, an ASROCK J3355 ITX (the VigorNic in the single expansion slot) due to a hardware problem of the previous MOBO. Interestingly, this MOBO was not affected with the hpet bug and installed 2.4.3 normally. Actually what happened was I forgot to enter safe mode but to my surprise the setup didn't freeze and continued. With respect to CPU usage, again I didn't notice any abnormality. However, I had to stop using pfsense, because for some unknown reason (I couldn't figure out anything from the logs) the box was crashing and rebooting every 15 mins or so. I have excluded hardware fault because this box now runs opnsense without any problems. The hpet bug that hit me with an update was a big let-down. Don't get me wrong or anything by no means do I blame pfsense or so; this was a core freebsd bug from what I have read. Having running stable for 6 months or so, it was shocking that an update would essentially destroy the system and also was a hassle trying to fix it. After this I keep my ISP's modem preconfigured and aside. I also beats me why j3355 was not affected by the bug. Best

Ok thanks, I will try to contact the Lanner support, maybe the know what's going on.

Bump. Anybody else experiencing this?

Everything seems fine… speed gave me issues but with a Ubiquiti AP if slected fulldx speed instead of auto.. i just tried without the bridge... same thing... going to install 2.4.2 from scratch and see if it makes any difference.

I had a similar issue when upgrading to 2.4.2. I haven't solved it… https://forum.pfsense.org/index.php?topic=141487.msg772193