@rikazkhan not sure if you realized it, but the last reply to this thread (before yours) was well over a year ago. :)

@stephenw10 FYI update: I was able to solve my issue of an unrecognizable filesystem error/partition. I put the drive in an enclosure and connected it to Windows, then used diskpart to "clean" the drive, which removed all partitions. Then, I was able to reinstall pfSense using recovery. now, I can see my disk from the GUI, and it seems to be running well. I hope this helps someone else. [image: 1711831584741-image-3-30-24-at-1.38-pm.jpg]

Yes any of those should work. Additionally you may be able to to use a DAC cable dircetly between the switch and the 2100 combo port. You would need to configure one of the 2100 LAN ports as a separate WAN though.

@stephenw10 Thank you so much for helping with this. While the network is designed to have the ability to switch traffic within the bridge, there is actually very little of that in practice. Most of the devices are just wifi clients heading to the internet. That said, I know there is broadcast traffic and other multicast and discovery traffic that would flow automatically within the bridge but other than that there is just limited use of intra-bridge traffic for things like IoT controller-devices communications. The network is in production and I would prefer not to have to remove the bridge unless it's my last option. Thanks again for helping.

There's no offiicial procedure for that and I could imagine the CPU cooling being worse with the fans pushing air toward it. The shroud becomes much more important. Additionally there is no easy way to change the flow from the PSU fan.

@stephenw10 Thank you for your reply, I'll think about it for a moment and see if get one and try it out.

Hmm, you were on 23.09.1 and it doesn't show 23.09.1 as an available branch? I don't think I've seen that happen before.

@powerguy42 how many did you end have failing? Any luck with a replacement? I just installed 11 or so of these in 2022 just before they suddenly went EOS. They have been OK but we suddenly had our first PSU failure. Now that I’m reading some more on these units, it sounds like the PSU failure is pretty common.

Yeah just came across this too, who has 5 minutes to wait for a router to boot? Pretty poor default, but easy enough to fix from the console.

@stephenw10 Stephen, thanks for all your help!

Yes if a state exists for that traffic it will continue to be used.

@nick-loenders If you want this for lab/home and have free time and like to tinker, you can probably make your own by using a rectangle PVC pipe piece. Some PVC glue, you can have a good-guy employee even cut it for you at the hardware store.

@SteveITS Wow! They already sent me the software. I wish I had posted here 2 days ago. Thanks so much for your help!!!

@stephenw10 Ok, now I understood and can put this pin on it for later improvement. Thank you very much for your kind help!

@tgl said in packages missing on new 4200: ... I don't know what "bootstrapping clock" is unless it's trying to run ntpdate. Digging in the rc scripts shows that it's doing this: /usr/bin/timeout -k 45 30 /usr/local/sbin/ntpd -g -q -c /dev/null {$ntp_boot_time_servers} I didn't research that ntpd call in detail, but I suppose it's morally equivalent to ntpdate, and would probably complete pretty quickly if it had connectivity to the mentioned servers. So that mystery is explained.

You should see upgrade_log.latest.txt after an upgrade has run. Can you mount the cf dataset manually as shown here?: https://docs.netgate.com/pfsense/en/latest/troubleshooting/single-user-mode.html#re-mount-zfs-volumes-as-read-write

I don't think a drive for the 4200 has been decided on yet. I've tested it with the drive we use in the 6100-max and 8200 which reports as: Geom name: nda0 Providers: 1. Name: nda0 Mediasize: 120034123776 (112G) Sectorsize: 512 Mode: r2w2e4 descr: M.2 (P80) 3TE6 lunid: 010000000000000000000036ba0299d8 ident: YCA12203170170456 rotationrate: 0 fwsectors: 0 fwheads: 0

@thiagopinski27 said in assignment new ethernet: tg-3468 Can we see it's output in pciconf -lv ? That looks like a Realtek 1G NIC though so I'd expect it to be supported by default.