@greg_e said in USB NIC on 2.4.4.p1 release?: If I absolutely need to do something else, I'll put one of my old Cisco routers between the two networks and then use vlans to run through the firewall. I'm not parsing that. It seems like you could just route between the VLANs in pfSense using a router on a stick setup. But anyway getting hardware with real NICs is better. Steve

@stephenw10 Did as you said, and it worked like a charm! Thanks again.

Hmm, interesting. I don't see anything indicating an ARP issue logged there. I would take a packet capture on the WAN when it is down and see what is being sent and if anything at all is coming back. One thing that may happen is if you set promiscuous mode in the pcap it comes back up. We have seen that happen before but I think only on ppp connections. I assume you're running 2.4.4p2? Since the issue is carried between OSes it seems likely a hardware issue. On which case I would check for power saving options that maybe enabled. There is a PCIe power saving setting that some BIOSes enable that can behave like this. Steve

@stephenw10 Thank you for replying. As with moth things, 10 reboots and plugging and unplugging it decided to work lol. So its running and I successfully have internet everywhere in the house both wired and wireless behind the cable modem into Pfsense into the wireless router and into a small switch...I'm exhausted. Now I need to figure out the easy part and how to use it. Thank you again.

One more link --- Not sure this is POE -- http://www.electronicnetwork.com/en/onrisc-baltos-ir5221.html

Ah, nice find!

I going to say probably not since I've never seen anyone else report that. What hardware is it internally? If it's not x86 then definitely no. If it is and it's not locked down, to a signed boot image for example, then maybe. Steve

Have a look at the Fractal Design cases: https://www.fractal-design.com together with Noctua FANs they are pretty awesome. If you want to extend your build to a big VM host the Define R6 is really nice with plenty of space for disks, and you can use the 5.25" bay for a temp/fan monitor of your choice.

It seems unlikely but I guess it could be. Some small variation in the components. If it works reliably connected that way I would just move on TBH. Steve

What hardware is that on? Specifically what NIC? When do you see that? Is it actually causing a connection problem? Steve

Nice! Just ordered (with Voleatech since I'm located in Germany).

I would be very surprised if it is not but you need to know the PCI-ID of the card to know for sure: https://github.com/pfsense/FreeBSD-src/blob/b964e7355f44df566d5906568c7598e7f9313da0/sys/dev/ixgbe/ixgbe_type.h#L84 Steve

That is true, it will only boot 2.4+ due to the UEFI requirement. There are some pretty detailed write-ups out there for compiling Coreboot. There is also (or at least was) a third party BIOS that enabled legacy booting on the original Minnowboard max and Turbot. Steve

yes you are right...put a gigabit switch on lan and everything is okay...many thanks

Probably the powerd settings. Adaptive rather than the default 'high-adaptive' will run the CPU slower on average in variable load conditions resulting in marginally less power consumption and hence heat. No fan at all with the same heatsink would concern me. It's a smaller heatsink than the MBT-2220 which is entirely passive but a greater potential power dissipation. Steve

Multiple queues should exist for ix or ixl interfaces by default. You can configure a fixed number using those options if you wish otherwise the system will add as many as the driver supports or your have cores for. You should see the queues in top -aSH at the command line. Steve

It will pass >200Mbps with 1500B packets using AES-128-CBC. More than that if you can use AES-GCM. Far more if you can switch to IPSec. Steve

Great, thank you!

Hmm, well if you use Squid/Squidguard to do web filtering I would want to see 2 cores there really, at least. Steve

Seems like you're hitting the legacy console issue which is known in 2.4.4+ though it would not normally reboot by itself. Either boot the device in UEFI node which should give a working console or do this: https://www.netgate.com/docs/pfsense/install/upgrade-guide.html#upgrading-from-versions-older-than-pfsense-2-4-4 Specifically the section regarding Atom systems with Intel HD graphics. In your case your device appears to have a serial console so you could also install using that which does not have this problem. Steve