Yes, that is possible.

Good to hear. Odd it's required. I know some others are using pfatt in 2.5/21.02. Steve

That is expected. the FreeBSD repo should be disabled so that pkgs are only pulled from out repo by default. Some are not the same and pulling them from FreeBSD directly can break things. Steve

Just to confirm, that is the expected U-Boot version in the SG-1100. You can see U-Boot report that in it's boot messages: U-Boot 2017.03-armada-17.10.2-g6a6581a-dirty (Nov 01 2018 - 16:04:57 -0300) Model: Marvell Armada 3720 Community Board ESPRESSOBin CPU @ 1200 [MHz] L2 @ 800 [MHz] TClock @ 200 [MHz] DDR @ 750 [MHz] DRAM: 1 GiB U-Boot DT blob at : 000000003f716298 Comphy-0: USB3 5 Gbps Comphy-1: PEX0 2.5 Gbps Comphy-2: SATA0 6 Gbps Steve

@welbo97 said in pkg-manager says netgate cert invalid: Is there a way to get it working without pulling power and doing a cold reboot? From what I've read on the forum., some chip has really to hardware reset. This can only be done by removing the power for a while.

@xyzzy Solved with usb stick install and config restore.

@jschenk Hi Databoy, I'm running into trouble getting those OPT3-OPT6 ports to work on the 4-port expansion card, see my post here if you have a minute to look over it? ( https://forum.netgate.com/topic/161836/seeking-advice-netgate-xg7100-1u-4-port-1000baset-expansion-card-not-giving-dhcp-lease/2 ). Was there anything special you remember needing to do to get the ports working?

@drphil said in SG-5100: Auto updated to new packages, but still old pfSense: saved config.xml on my local system, and then restored it ( That would be what did it. If it tried to reinstall the packages it would pull them from the current repo, so 21.02. Installing later software would install any dependencies for the newer OS as well. https://redmine.pfsense.org/issues/10464 Always select "Previous Stable Version" in System/Update if you want to stay on the older version. The Netgate version of pfSense does have a few packages preinstalled as you listed.

@orddie said in XG-7100 DT 10GBE: VLans?: Has the forum change to the point that users do not answer questions of users looking for help and just troll? do you think i'm like that too... Please take a look after me ... who can I be? ++++edit: well, I also use Intel 710 stuff, under PfSense or FresBSD, I am well kneaded out of this ...

I solved the issue changing this setting: [image: 1615025728064-screen-shot-2021-03-06-at-11.13.29-resized.png] Default gateway IPv4 was automatic and for some reason it wouldn't select the only gateway available. Setting it explicitly fixed the issue. Gab

@teamits Works for me, thanks!

@teamits Oh I see, makes somewhat more sense at the moment. Ha ha okay I do not think I will end up at 10000. Is the train-of-though 1) Block everything, 2) Allow what is needed, completely off? Otherwise, I think follow Lawrence Systems guides, Ah, cool. Of course, that leaves the problem that when I get into it and suddenly realize I simply cannot live without IDS etc. Gotcha on the 3100 - that's too bad.

@stephenw10 thank you. I thought of using some ETH port as dedicated untagged port in a management VLAN but that seems not to work as intended as I understand. OK: use the next switch for that, I understand. I will see this afternoon if my setup works.

@bmeeks Nice, thanks again

@metacyclic No logs, my observations were not being able to sustain 940/940Mbps using iperf3 or speedtest when traffic source is from a tagged VLAN.

@jimp Sounds about right... I'll get a config backup and reinstall. Thanks

@s0m3f00l https://redmine.pfsense.org/issues/11605

@keyser I would stay on 2.4.5_p1 until a later release. I wish I read that before I updated. After two days I am running on 21.02p1 but the setup is as basic as it gets. I tried restore and manual setup and each time reached a point I had to start over again to get service. I'm not one to complain but this was the one update that makes me want to look around for other options.

@kuser How? I created a ticket specifically requesting it and they sent me the 2.5 patch link instead.