For 2.7.2? You can extract the module from the 2.7.2 ISO image. The firmware is there too.

It looks like that driver has problems though. I'd be surprised if it works well for you.

Mmm, well they are both rev4 at least. I would certainly try the other port to see if anything changes there.

Otherwise, yes, we'd need to see what actually happens when it fails. If the link is still up is there anything in a packet capture for example. Anything logged in the macstats for the interface.

Some are supported by sfxge(4) but that driver is not in 2.7.2 by default.

@provels said in ZFS on SSD RAID10 efficiency:

@sergei_shablovsky Have you tried running

systat -iostat

to see if you even have any bottlenecks?

Need to remind that is NOT situation where some bottlenecks already limiting overall pfSense performance or create some kind of problems.

Till now I collecting info (by LibreNMS, Prometheus and ELK) about how exactly which type of workload impact on server’s hardware resources consuming.

To be prepared for situation when workload spontaneously rapidly growing.

In my mind, I think RAM for /var and /tmp and proc cores/GHz are the most important, followed by a disk redundancy strategy like a mirror set.

My initial question was about FreeBSD and pfSense FINE TUNING and

Also need to saying the time are running, FreeBSD changing (and pfSense+ version already using 15-CURRENT, but pfSense CE - still on 14-CURRENT), additional pfSense’s packages updated,… so IMPACTS ON DISK SUBSYSTEM are changing accordingly…
So periodically need to re-tuning both pfSense and FreeBSD.

After that, I'd opt for server redundancy/cold spare.

Of coarse, HA would be implemented.

You're already shipping the logs to another server anyway.

I use 10Gtek SFP+ for my SG6100 and UI Switch.
On Netgate Side a Intel flashed and on UI Side a Ubiquiti flashed version.

It works inkl. DOM support do see temp, RX/TX levels, Power draw...

The N100 seems plagued with problems but I'm not sure if that's actually anything to do with the platform or just that they seem to be favoured in as-cheap-as-possible chinese boxes with half-baked firmware. Particularly the power management seems incredibly variable from the reports we've seen on the forum.

But that's unlikely to be anything to do the PMC. It looks like that code doesn't yet know about the N100 specifics. I wouldn't expect that to be an issue though.

@RobbieTT said in Enhanced Intel SpeedStep / Speed Shift - Are they fully supported?:

@Sergei_Shablovsky
It's just iPerf generating or receiving traffic. In this specific example I am just using it with the GUI that is iPerfUtil but it remains iPerf under the easy controls so it works with any other iPerf network client.

Thank You for answering!

Do You testing iPerfUtil with iperf3?

Could You be so please to give me a link on iPerfUtil ?

Thank You!

@stephenw10 said in Quectel EP06-E LTE Module changes pfSense+ NID after cold start or hard reset:

AT+QCFG=“usbnet

After all, the Modem will respond to " AT+QCFG="usbnet",? "

@alleykat said in Normal Operating Temp NG-4200:

How do you reset RRD?

In Status > Monitoring > Settings (Advanced).

The default value for SpeedShift is 80.

At the command line run:

echo 'if_re_load="YES"' >> /boot/loader.conf.local echo 'if_re_name="/boot/modules/if_re.ko"' >> /boot/loader.conf.local

You can manually create ZFS snapshots at the CLI in CE, assuming you are running ZFS. However there are no public 2.8-dev snapshots yet.

@stephenw10 yeah. It's a FreeBSD issue. Amdtemp only supports families up to 17h. The 5700G is 19h.

ECC RAM is a nice to have thing and or but for a 24/7 running device it
makes sense. The TPM module I am using in the PC Engines APU6B4
I was able to buy one from Dasharo, I was soldering a 10 Pin header
on the bard and then I connect the TPM module there, together with
the latest BIOS version (19.01) the BIOS recognizes the TPM module
but pfSense itselfs is not taking any advantage of the TPM module.

Perhaps with the next BIOS it could be something is on change at
this point.

@stephenw10 Hi Stephen,
Just to say after so much trouble with this, I learnt that a work colleague of mine had the FS BOX which I just borrowed to recode the SFPs to Intel. As soon as I had done that and plugged them in, they came to life immediately without any need for tunables or other tweaks to get the link working. It's working on autoselect / autodetect with a fresh install of pfSense.

Thank you so much for helping me out with this, but I hope this thread is of use to others: any recent FreeBSD install or security appliance designed on top of FreeBSD using Intel SFPs, you really need Intel-coded SFPs otherwise it just won't work!

@coxhaus Only floating rules have a direction.

WAN/LAN/etc are only for inbound packets on that interface.

Unbound can forward, but if you do that uncheck the DNSSEC option which is on by default.

Yes, I only found one system here that reports that sysctl. And it probably shouldn't!

On most of those devices (except the 1100) the LEDs are closest to the PCB. In the 6100 and 8200 (and 4100) the PCB is above the ports to allow for a larger heatsink below it.

Well still no but I don't think that's that's same thing. They appear to be available only for Cortex-M CPUs and it's not clear to me if they can be updated after build.

Hmm, so it only fails to reconnect when coming out of standby?

The system could be holding the NIC powered to allow WoL etc. There may be some BIOS settings to disable that.