@stephenw10 thanks for replying.
We're currently running a HA Cluster on 2.4.4-RELEASE-p3. Do you know how I could port that to the current running system and I can test on the slave?
If not I'll see if we can fine some hardware and another card to test with.
Are you able to test a 2.5 snapshot?
Now is the time to report issues with that if you can. It may be something upstream in the driver of course. We are limited in what we can do if that's the case.
Hi @lifespeed - I'm using the Supermicro 5018D-F8NT system with pfSense, which is based on this board:
In terms of specifications, this board looks very similar to the one you linked to. In my case, the onboard SFP+ interfaces are actually using the ix (ixgbe) driver in pfSense / FreeBSD as opposed to the ixl drivers.
I'm thinking this may be the case for the X10SDV-4C+-TP4F as well. Overall, this setup has been flawless with the exception of this issue (which has only been occurring recently):
Hopefully this will resolved in the next version of pfSense and newer version of FreeBSD.
Hope this helps.
What does the "watchdog" feature in the BIOS setup options of the APU2C4 really do? Do I need it enabled or what? Thanks.
Also, I just re-installed pfsense 2.4.4 p3 on my APU2C4 and for some reason the temperature sensors are not working again even though I have the correct module set:
I thought the support for these sensors was added since the release of 2.4? I didn't remember encountering this issue when I reinstalled in the past with lower versions of 2.4.
Reloading amdtemp.ko and doing a sysctl -a | grep temperature doesn't output anything.
Just want to let you guys know: I have the Qotom Q575G6 with Multi WAN Gigabit and Suricata running. IPsec VPN brings the CPU up to 40% usage. I'm really happy with this device. It's running flawless and very fast.
I just subscribed to thank you for your work,
I was going mad trying to understand the issue and finally this morning I found a post that directed me here.
The issues I had on my ci323 nano seems all solved now.
ZFS seems the most vigorous FS available in pfS, that's why I moved over from UFS to ZFS. The (re)install is a breeze, with a current config file at hand.
My APU2C4 has ECC and to me this and the ZFS FS seems max what I can do against sudden power surges, that being said, I would will always use the "halt" command before I pull the power cord ;)
@bouke Kudos for pointing out the flaky mSATA issue link, didn't knew that.
@phatty that is unfortunate. I did find some old documentation on features that were made available to customers like AT&T, but unfortunately, AT&T never implemented them. One of the features was a Pass-Through for customer data, which allowed the gateway to also perform the required tasks that allow it to work on AT&T's ATM network. I'd describe it as a smart Bridged Mode that doesn't prevent the gateway from doing what it needs to do. They have many different options to implement what is needed, but I have a feeling that they aren't doing it to force you to upgrade to an OC3 or similar connection. :/
50% CPU usage on that dual core CPU is probably 100% on one core if you;re checking on the dashboard.
Suricata can use the other core bringing it up to 100% total. You would have to check at the command line to see the CPU usage breakdown: top -aSH.
That is more that I would have thought but the single thread rating of the E4500 is significantly higher than, say, the J1900 that has been seen to be limited to ~500Mbps PPPoE. Though those Celerons seem particularly effected by this for some reason.
Just to add in case people still have pppoe performance caps due to cpu power, make sure you enable powerd on units that support intel turbo.
Without powerd turbo clocks wont kick in. powerd isnt just for power saving.
Also it seems "some" igb chips do support rss properly with pppoe, I switched to a pppoe isp last month and see my rss is working properly on the igb driver. I have 2 queues for both isr and igb, the rx is almost a 50/50 split, and its tx thats lopsided at 90/10.
Yeah, I would ask on the OpenWRT forum: https://forum.openwrt.org/
But.... get the x86 image. Try to make it boot from it. Check the console output toi see what it working and what isn't. Make changes as necessary.
You might also be able to change the IDs it presents by accessing the command line under some other OS. It's been while but I seem to recall reading those Quectel devices were very similar to Sierra internally.
Hmm, but you were able to interrupt the boot loader and enter characters which implies the console is working fine at that point. Hard to say then, I don't recall anything stopping at that point previously.
Ok, so unless you can see any jumpers that might set them then, as I said two years ago, you will have to start poking at GPIOs to try to find what controls them. You might find a clue in the RIOS boot logs or filesystem.
In the end - I realised that the larger boxes have i386 CPU, which pfsense stopped supporting (AES-NI), so I went with OPNSense for both the 3300 and the 1100 (1.5GHz Celeron M)
Both work like a charm!
In a current CPU the TDP is only vaguely related to power consumption, and mostly in that low TDP parts have their max performance throttled to hit a specific max TDP number--at idle they're going to be close to the same. In an old opteron the power management features are much less advanced, and the idle power consumption in a typical "mostly idle" fw configuration is going to be much, much higher than a relatively cheap processor with a more modern core. And not just the CPU--the older chipset, especially for a rackmount server, is going to be much more power hungry than something new. If you're paying california power rates I'd probably just buy a newer box rather than fiddle with the current one. At lower power rates pulling one 4386 and leaving the system alone is the most practical approach, because the break even time for buying anything else will be long.
I went with the Asrock, it works perfectly under Pfsense and has great fan control to run totally silent in a very quiet room.
CPU i3-9100, overkill but 9100T are hard to find on stock
Used the intel I219V port for LAN and I211AT for WAN
Hope it helps other users
Ah, good info! I would expect a 6100 i3 to work there. I just haven't seen one at a price I can justify.... yet.
Unlocking the BIOS is non-trivial. Finding the password is probably never going to happen.
@kiokoman thanks. Some random Nvidia 2gb pcie card I got for free aome years ago. One slot and has hdmi. Am4 lacks video except for the apu units. Since i got a videocard, going for it. Tempted to get a 2700 non x 8 cote for 100$ more for fun...
Here for our new gateway of defense :
SM SYS-5018D-MF ( + 8Gb ram and a Xeon E3-1240LV3 ). I add also Intel Ethernet Server Adapter x4 LAN, and last but not least i will use SSD (x2 in case of...)
They claim to support FreeBSD though the FreeBSD mlx5 driver doesn't list that card specifically.
pfSense does not include the Mellanix drivers by default, you would need to copy the kernel modules across from an equivalent FreeBSD version or compile the drivers if something newer is required for that card.
I would test it in FreeBSD to initially if you can.
We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.
Subscribe to our Newsletter
Product information, software announcements, and special offers. See our newsletter archive for past announcements.