Mmm, that should have been clear when we issued the RMA.

Please let me know if you still have questions or if we have a hole in our process that needs attention.

Steve

Mmm, as far as I know this is the first report of it we've seen.

The 3100 has a switch but it doesn't use a lagg or vlans by default. Only the 7100 does that.

Steve

No, shouldn't be if it's set to the 'Latest stable' branch in System > Update.

You can turn it off by running: pfSense-led.sh update 0

Steve

Yeah, it still checks against available kernel memory:
https://github.com/pfsense/pfsense/blob/master/src/usr/local/www/system_advanced_misc.php#L356

That could probably be removed with tmpfs there but it's only a significant restriction on arm32 and limiting ram disk size there is not terrible anyway.

https://redmine.pfsense.org/issues/13508

Steve

Nice recovery!

The ECL should work in a VM if it sees a mounted USB drive (daX). We have seen issues on faster machines, or slow USB drives, where it fails to mount before the ECL runs. I could imagine you might be hitting that in a VM.

Steve

@creationguy Temps are what i have as well. Mine was in an open rack in an open basement and i would get around 53. I have the 6100 and the temps are the exact same.

That's the maximum forwarding performance across all interfaces combined. That's also without filtering which is the biggest overhead you will hit there. 2Gbps is low though. I'd expect to see 3-4Gbps at least. There are a lot of variables there however.

I didn't have a chance to test the 10G port directly yet. I do have a new workstation that can test at those speeds far more easily so I should be able to get some numbers soon.

Steve

@stephenw10

Netgate 4100 it is then !

@stephenw10 Thank you!

Yes, that's it attaching normally.

Hi All,

Thank you all for your inputs. I do not really think an issue with the negate device. There are just many factor affect the speed/throughput.

I am going to investigate further on each of the components in the connection.

Thanks again for the inputs to point me to the direction to investigate further.

Best Regards

The older eMMC type cannot bye read by the utility if that's what you're asking. There is no way to allow it.

Steve

A follow-up:
This is a case of outdated information that has been addressed. If you find this forum and think the drivers aren't compatible please try another USB cable.

If you really want to get in the weeds you can dig out a multi-meter to verify your Mini-USB cable has all 4 wires and connections made, as well as the shield (the metal on both ends of the cable should register continuity on your multi-meter as well).

Of course testing those ends is a royal pain so I would just plan on checking other cables. Having a half-dozen mini-USB and microUSB cables lying around is a great thing because you never know when you might need one for something, or two or three somethings at the same time. 🙃

Ok thank you again for the help

Thanks so much for your suggestion Steve! I submitted a ticket per your direction.

The list shown in the GUI is the output of top with some flags: top -aSH

@stephenw10 My plan is have my 6100 sit in front of my UDM-SE to provide DNS with pfBlocker and Suricata. I have a /29 block from my ISP, so I can just pass of those IPs down to the downstream UniFi network.

Yes, that. Most people who end up using a lot of memory have just enabled all the feeds in pfBlocker or all the signatures in Snort with no thought to what they actually need.
I'm running Snort and pfBlocker on a 3100 here and not even using 50% of the 2GB it has but I only selected limited lists.

last pid: 63920; load averages: 0.25, 0.43, 0.44 up 5+06:28:22 14:09:29 65 processes: 1 running, 64 sleeping CPU: 2.6% user, 0.2% nice, 7.5% system, 0.2% interrupt, 89.6% idle Mem: 176M Active, 476M Inact, 169M Wired, 84M Buf, 1162M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 48523 root 2 41 20 351M 327M bpf 1 53:21 0.36% /usr/local/bin/snort -R _6830 -D -q --suppress-config-log --daq pcap --daq-mode passive --treat-drop-as-alert 82520 root 1 52 0 131M 42M accept 1 1:18 1.18% php-fpm: pool nginx (php-fpm) 28210 root 1 52 0 132M 40M accept 0 0:46 0.00% php-fpm: pool nginx (php-fpm) 59286 root 1 52 0 132M 40M accept 0 0:21 0.00% php-fpm: pool nginx (php-fpm) 42298 root 1 52 0 132M 39M accept 0 0:19 0.00% php-fpm: pool nginx (php-fpm) 67504 root 1 52 0 132M 38M accept 0 0:05 0.00% php-fpm: pool nginx (php-fpm) 2851 root 1 43 0 130M 38M accept 0 0:07 0.05% php-fpm: pool nginx (php-fpm) 44040 unbound 2 20 0 63M 35M kqread 0 18:52 0.00% /usr/local/sbin/unbound -c /var/unbound/unbound.conf 73345 root 1 20 0 49M 34M nanslp 0 0:33 0.05% /usr/local/bin/php -f /usr/local/pkg/pfblockerng/pfblockerng.inc dnsbl 428 root 1 20 0 91M 22M kqread 1 0:15 0.00% php-fpm: master process (/usr/local/lib/php-fpm.conf) (php-fpm) 61524 root 17 52 0 45M 18M sigwai 0 2:04 0.00% /usr/local/libexec/ipsec/charon --use-syslog 84665 root 155 20 0 64M 15M uwait 1 1:00 0.00% /usr/local/sbin/filterdns -p /var/run/filterdns.pid -i 300 -c /var/etc/filterdns.conf -d 1 51479 dhcpd 1 20 0 14M 10M select 1 0:30 0.02% /usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid m 33768 root 1 20 0 12M 8160K select 1 0:00 0.01% sshd: admin@pts/0 (sshd)

Steve

@gertjan RE: I don't know why, but I use the NUT package, not the apcupsd version.

We had been running the NUT package. I think that may only monitor the UPS but doesn't have the capabilities of the apcupsd package.

We also installed apcupsd on a Windows NUC that's on our LAN. If the power goes out the NUC will get a signal from the software on our 3100 and it too will shut down.

Well IPSec and OpenVPN with DCO will.

So not (yet) Wireguard, PPTP, L2TP, TINC.