@Rico said in Why do I get AES-NI CPU Crypto: Yes (inactive)?:

System > Advanced > Miscellaneous > Cryptographic Hardware > AES-NI CPU-based Acceleration
Hit SAVE and reboot pfSense.

-Rico

Thank you!

@sayin1974 said in fortigate 600c pfsense nasıl yüklenir:

fortigate wants to charge a lot for the license.
can i install pfsense on this device?

Probably not. Or not in any useful way. You will not be able to use any of the ASIC connected ports as they use proprietary code. That is most of them.

Steve

Yeah, interesting.

0x1509 - Quad port EEPROM-less Device ID (Default) 1 0x150E - Quad port 10/100/1000 Mb/s Ethernet controller, x4 PCIe, copper.

So no EEPROM, or not readable, on the OPs card. Maybe it's damaged or missing. Or a jumper got moved etc.

Steve

@haywooj thanks, will give it a try

@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