@TheNarc said in Cannot load a compiled .ko Intel NIC driver to pfSense 2.4.5: The stable/11 branch is here: https://github.com/freebsd/freebsd/commits/stable/11 But I've been unsuccessful in linking r357046 to a commit hash, which is not entirely surprising as I'm not too well versed in git. I thought github's search would be able to find it, but I haven't had luck yet. I'll let you know if I locate it though. It will be good to know, but I managed to compile it as follows: The VM image didn't had enough space, so I've created a VM from 11.3-STABLE ISO Installed subversion (svn) Used the following: svn checkout https://svn.FreeBSD.org/base/release/11.3.0 /usr/src/ to download the source - So you were right using Release SRC on STABLE. I still don't understand why it works, but I'm glad it did. What I saw in the FreeBSD svn manual, is that we can use svn -r (and the number of revision), in order to update the source to exact revision. But it didn't worked for me, or it's a more complex syntax, or I don't have access to the repository. If you find out please let me know. We will need it when pfSense based on FreeBSD 12 will be released :) In the end I would like to thank you, for all your tips @TheNarc , @stephenw10 and @jimp . It worked

Both parts of that dhclient fix are in 2.4.5 so you might want to test that again. Steve

Check the bios for any sort of USB power saving features that might be shutting down the NIC at reboot.

Yup, it's in our branches too. It will not be in 2.4.5 though. https://github.com/pfsense/FreeBSD-src/commit/53c20dbd882153f18322848108a8488519b59ff9 Steve

@stephenw10 said in Firebox X550 hanging on boot: However that appliance is now ancient in computing terms. I got my hands on one of the last ones ever built which replaced a unit under warranty days before Watchguard quit them altogether. That was over ten years ago and it served me well until we out grew it. (Could not transfer speeds we do today with all our subnets and VPN's) Ran Watchguard software for just under a year before becoming a pfsense box. Ancient is very true at this point.

@stephenw10 Unfortunately I had to give those back to my ex employer. Ok o decided to buy SFF dell instead of buying server, if that would be not powerfull enough i'll buy server.

I've never used that particular card myself but I wouldn't expect any issues with it. If you don't need Gig VPN then that CPU will do almost anything you might want. Steve

Ohhhh I like that! Thanks for posting!

@Rico Fully agree on this. It's worth spending some extra money to avoid playing the "it's not our fault" (TM) roulette with your vendors

Yup, that's certainly what I would expect.

Yeah, there we go that VID:PID is not recognised by u3g so no com ports are created. Recompiling u3g to include that would likely allow it. If you do that route you should test it in FreeBSD first. You may also be able to change the ID of the device to something that is already recognised. Some modems will allow you to set the ID directly using AT commands. If the hardware is sufficiently similar it might come straight up. You would have to do that from Linux or Windows. Steve

@johnpoz said in Will this Dell Optiplex be a good Home pfSense option?: @AR15USR said in Will this Dell Optiplex be a good Home pfSense option?: •2-3 VLANS How is that going to work? I doubt the r7000 supports vlans - is it going to be running 3rd party firmware? Decided to use DD-WRT fyi... . @stephenw10 said in Will this Dell Optiplex be a good Home pfSense option?: Should be no problem them, that hardware will barely be troubled by that. Steve Thanks for the confirmation...

Like what software can do it on that hardware other than pfSense? I have no answer for that. pfSense may be able to do that but it's a scenario I have ever tested. Nor a hardware I have ever tested. If you have the hardware I can only advise you test it yourself and find out. It should not be that difficult to do. Steve

igb(4) is the correct, and only, driver it should be using and it's in kernel in pfSense. There is no need to load anything. You need to determine how it's failing. If the card does not appear as a PCI device that's something very low level like a bad card or a BIOS fault. If the driver fails to attach you need to see what the error it reports is in the boot log. Steve

@stephenw10 yes, just realised my typo. xtm5 :) Thank you, will go for that one instead.

I believe that should work though I have not tested it myself. Although those are mPCIe form-factor they are still USB connected. It is far more difficult to remove it accidentally though and I would not expect it to require mode-switching. It may even be possible to use the cellular package with that to get link stats. Steve

All of those links take me to a page that requires login on aliexpress. Is there any reason the official netgate solution wouldn't work for you? I'm not sure if the SG-3100 would work for the home, office and guest setup using the LAN and OPT1 interfaces. Not sure if the RT-AC87u setup as an access point with a separate guest login would prevent the guest users from accessing the rest of the LAN it's connected to. My feeling is it wouldn't so you might need another interface and AP for the guest if that's the case (SG-5100). If price is an issue, I hear good things about the apu2 platform.

Yeah looks like that. I've decided to try and figure out HA in VMs on unraid... just for fun. One is working perfectly, now on to the HA setup :) cheers.

Oh, the internet is working. Seems very slow. I hope the internet is only for the VM router and hypervisor and not this local computer, where I stream videos. I will need to only allow certain devices on the router for internet, due to low need and a low internet plan. The hypervisor has a very slow connection with a ping of 4000 ms. Looks like I can progress to the network configuration. Case closed and thanks.

@valnar said in 2020 home build or buy?: I have a 200/10Mb cable circuit and run pfSense on a PCEngines APU2C4 (new one is APU2E4). It's more than powerful enough and barely sips electricity. I run Plex through it just fine. It can handle 500Mb+ Concur. I just installed pfSense on a PC Engines APU2E4. I don't have gigabit fiber WAN yet (currently just 25 Mbps ADSL) but there are plenty of credible reports that the APU2E4 will push 500 Mbps (unencrypted) without optimization, and 950-1000 Mbps with a couple of minor tweaks. The APU2E4 has a few specs that make it especially pfSense-friendly: AMD Embedded G series GX-412TC, 1 GHz quad-core CPU WITH AES-NI support. 4 GB of ECC RAM Up to 120GB internal mSATA (not CF card) storage 3 Intel i210AT ethernet ports. (The i210AT has double the number of transmit/receive queues vs the closely-related-and-more-common i211AT.) DB9 / RS232 serial console port 2 x USB 3.0 ports Completely fanless, and very low power draw, around ~6 watts idle ~10W max. Compare that to using a random old desktop or server PC which could draw easily 30W-40W idle, maybe much more depending on configuration.) Very compact (about 6" x 6" x 1" thick) Very competitive price point If you enjoy spending hours to days messing around with random old hardware, trying to figure out whether the ethernet interfaces in it are a) compatible with BSD b) reliable in general c) performant enough to allow pfSense to shine as it should, and mucking around with BIOS-related boot quirks, etc, by all means, dig around in your closet or go to Goodwill or a flea-market. If you want a smoother, easier pathway to a decent-performing and reliable pfSense community-edition install, go with a well-known hardware vendor with recent good compatibility reports.