I don't think there is a public diagram like that. Let me see what I can find though.

The NICs are the 4 Intel NICs from the C3558 SoC using the ix(4) driver and 4 Intel i225 NICs using the igc(4) driver.

Steve

Yeah, the default settings should work fine there.

You can uncheck hn ALTQ support since there are no hn NICs in the 2100. It doesn't make any difference though.

Steve

Since there is no SWAP on the 1100 that is actually telling you it's out of memory.

Look for processes using a low of RAM in the list.
Check the memory usage on the dashboard.

Steve

Yes, that's true, ZFS will not be an option on the 32 bit ARM platforms.

Steve

@stephenw10 apologies accepted, much appreciated.

Mmm, you might try enabling verbose boot and see if it shows you anything different when you reboot or shutdown with the card in.

The SoC used on the 2100 and 1100 does not have a hardware temperature sensor we can read in pfSense.
That's not something that applies to all ARM devices. The 3100 does have a sensor and it's selected automatically.

Steve

@tappy

Only took three tries for me to get a clean file system, but went for four just for good luck.

Thanks for the hint!

You very well may have a hardware issue, but one thing you can do for testing and to eliminate other possibilities is to remove all the extra packages you have installed. I see pfBlockerNG and bandwidthd at a minimum.

One of those may be causing the reboot. Removing both and then testing to see if the reboots recur is a good first step. If you don't have reboots with both packages removed, then add them back one at the time and test for a while between each add.

If you get reboots with the packages removed (that is, with a plain-vanilla install), then you likely have a hardware issue and Netgate will have to work with you on a warranty fix.

Yup, use that page or email tac@netgate.com directly to open a ticket in the new system.

Steve

Yes, we just changed ticket systems today. You can also email tac@netgate.com directly to open a ticket.

Steve

Yes, both those should work. The netgraph script also tags outgoing traffic for ISPs that require it but Frontier doesn't appear to.

I would personally use the switch port instead if you can because that is all contained in the config. If you ever have to reinstall and restore the config that will be far easier.

Steve

Yeah, nothing looks too terrible there. A bunch of errors are expected on the first boot after updating.

Steve

The 6100 PSU has a higher current rating (5A vs 3.3A) so it's impossible to recommend doing that.
The supplied PSU is capable of delivering the maximum power the 6100 can draw which of course it usually does not however.

Steve

https://docs.netgate.com/pfsense/en/latest/solutions/netgate-6100/wall-mount.html

@bmeeks Thanks, ticket created.

Greg

@stephenw10 said in Netgate 6100 10 gb Routing Throttled to 1 gb?:

@bpsantucci said in Netgate 6100 10 gb Routing Throttled to 1 gb?:

I'm not sure what you mean by routing or NATing in this case...

I mean if you are testing with a client on a 'LAN' and the server on a 'WAN' the auto outbound NAT rules will be NATing that out of the WAN interface. That requires additional processing limiting throughput.
pfSense determines what is a WAN interface in that situation by whether or not it has a gateway defined on it.

The throughput is limited by the CPU in the 6100 in that setup. As long as you have pf enabled and firewall rules in place ~5G is what I would expect to see in iperf3.

Steve

Got it...Never thought about it like that, but now I see how WAN/LAN NATing could create significant processing overhead. Thanks for the explanation!

Ordered mine on 11/24, just got an email this morning saying they will begin shipping the week of the 29th in the order received. Hopefully they got enough in to get mine shipped.... :)