Just add ports 1 and 5 as tagged members on those VLANs in the switch config. [image: 1705272549921-screenshot-from-2024-01-14-22-48-58.png]

What NICs does the CE device have? If it only has assigned NICs that actually do exist in the 8200 then it will just try to use them rather than asking you to reassign them. Since you have Netgate hardware you can open a ticket with us and have the old config converted so it will import directly. https://www.netgate.com/tac-support-request Steve

@OhMyFlavors Yea seems like a faulty drive. Luckily it was still under warranty and was approved for RMA. Thanks Stephen for all your support. Much appreciated.

@dscheive said in SG-1100 too bright leds: like the underglow from some teenagers civic. Ha.

I would recommend just re-installing clean. 21.02 is a very old version and trying to upgrade to 23.09.1 from that will require several steps. Make sure you have a backup on the config. Steve

Nope you can always open a ticket for firmware requests like that.

That's a great idea! I may just get lucky with a spare board laying around with a last-ditch-effort on this. Much appreciated, Steve! Best regards, Michael

@stephenw10 et all I've been liaising with QSFPTek.com support team and they've been very helpful and have stated the Intel branded DAC cables should work "out of the box". They provide MBR details and a 5 year repair warranty on their DAC cables, which I believe is a solid warranty option. However the proof is in the pudding... I have ordered the DAC cables and will post an update on the functionality when I can.

It should be on there I can see the replies internally. I replied on the ticket. We finally replicated the issue and it looks to be how Squid is handling the SRV requests/records. Digging continues. Steve

Hmm, not much we can do if the serial/usb device isn't even detected.

The firmware update will default the boot device value in the BIOS but won't change anything on the drives. You should be able to see what device you're booting from currently using a combination of the commands: `glabel status' and 'mount -p' To change the boot device you need to set it in the BIOS setup using the serial console. Most importantly though you will only be able to upgrade the firmware there from 23.05.1. 23.09(.1) currently has a bug preventing that. So you if you have that or an earlier version installed to the other boot device you may be to boot to that and run the update. Or if you are running ZFS you can probably roll back to a BE snapshot from 23.05.1 Otherwise you may need to install 23.05.1 in order to run the firmware upgrade. Open a ticket with us to get the install image for that if you don't have one: https://www.netgate.com/tac-support-request Steve

If it's showing anything on the console it's not the CPU issue. It looks like it sees the boot device and is loading the boot loader but never and actually tries to load the kernel if that's all that ever shows. I would just reinstall clean from there if you have a config backup. Open a ticket to get the image: https://www.netgate.com/tac-support-request Steve

It can't open the file to write the notice. Since you had to pull the power the first thing I would do is run a manual fsck: https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-check.html#manual-filesystem-check Steve

@recoveringchemist Restore: https://docs.netgate.com/pfsense/en/latest/backup/autoconfigbackup.html Yes you can restore to the same or usually different hardware. Models with switches are a bit different because of how each handles it internally but Netgate support will convert it for free. But not needed with the same hardware. Can’t say if it’s 100% the same but it doesn’t matter you can just restore. Have restored to same and different hardware many times.

@stephenw10 moved to: https://forum.netgate.com/topic/185194/aws-s3-cp-crashes-the-firewall-when-using-squid-web-proxy

It does look like you upgraded to the 24.03 dev snapshot though. If you're running ZFS you might consider rolling back to an earlier BE snapshot and re-upgrading to reach 23.09.1.

@GeorgeCZ58 Yeah both connectors are connected to the board. I've tested the fans and they work I'm starting to lean to a motherboard issue.

I created a regression for this as advised: https://redmine.pfsense.org/issues/15112

Yes, more like it. In that sort of test the limit is often iperf itself which is deliberately designed to run on a single thread. You can see it's running on Core3 and that is also being used to move packets. So a test through the 6100 between different interfaces using external iperf nodes should show significantly more.