sadly only on our dreams an italian isp would do that

@eholcroft said in SG-1100 Throughput:

So just to close the loop on this:

Hooked up the XG7100 as a comparative test and got 873mbps on speedtest.net. That's more like it. Except I don't think I'll be putting a $1000 router in my home any time soon.

I'll take a look at the product lineup and see what Netgate pfSense will give me closer to what I need. The SG3100 I guess. Didn't really want to spend that much on a home router, but I'm in deep with Comcast Gigabit now so I might as well go all the way.

The picture offered here https://www.netgate.com/blog/netgates-new-sg-1100-punches-way-above-its-weight.html really seems a bit optimistic. Not sure what the conditions of that testing were but I wish I could replicate it here. So to other buyers out there be warned - while the SG1100 is an impressive little device, it doesn't quite live up to the hype.

I have no horse in this race, so to speak, but looking at the page you linked there are some bar charts at the bottom where the results somewhat agree with your real world experience. Of note, look at the bar chart showing packet filtering enabled. Notice that depending on the packet size configured (256 bytes, 512 bytes or 1500 bytes), the bits/second number changes quite a bit. What is actually more important is the pps (packets per second) processing rate. That is pretty much fixed and determined by the CPU in the box. It stands to reason, though, that larger packets wind up producing a greater bits per second rating. That's what the bar chart I referenced illustrates.

With your speed test site, you don't really know exactly what size all of the packets are. If they were all uniformly 1500 bytes, then maybe reaching the 800 megabits/sec rate is reasonable. However, with smaller packet sizes, since the packets per second rate is fixed, you get overall smaller throughput when measuring in bits/second.

Note that the first bar chart on the page is showing performance with pf (the packet filtering firewall) disabled. Very few users would run that way, though. That's just a plain vanilla router with no firewall enabled. The second chart shows performance with the firewall enabled.

thanks to both of you for responding. i have opened a ticket with support requesting a system image. i will post later how things transpire.

Chuck

@onlinecanuck said in SG-1100 WAN interface goes down very frequently.:

did have it set as DHCP before as I knew that was what my modem/router combo used...

Using DHCP on WAN is fine. But ....
There is one thing that needs to be checked : if your pfSense is using the default 192.168.1.0/24 and your upstream router has it's LAN in the same network 192.168.1.0/24, well, then things break.
Change your pfSense LAN network, for example 192.168.2.0/24 - or change the LAN network of your upstream router.

edit : keep in mind : when you connect a router like pfSense using it's WAN interface to a local, existing network, pfSense behaves as any other device that you already have on this LAN (there could be other PC's, printers, media stuff, whatever). All these devices are hardwired - or even using Wifi) to the upstream ISP router. This connection should always be stable and up. If not, check your cables and or switches.

@kiokoman great!

When I had just flipped the IPs between FWA and FWB yesterday I still had loss on FWB but did not test from FWA perhaps.

I just moved FWB IP to FWA and put another free address on FWB. Loss now on FWA.
Going to be calling the ISP again.

I did some other crazy stuff to route from FWB to FWA to get to 8.8.8.8, did packet captures and proved FWB was indeed sending request packets for the dropped pings being reported.

Thanks for the suggestion.

I pulled the trigger and did this - you need to restore the VLAN config from factory over top of a restore, and it then works okay.

They seem perfectly sufficient in the testing I have done. It does not run especially hot.

See: https://docs.netgate.com/pfsense/en/latest/solutions/sg-5100/m-2-sata-installation.html

Steve

It's DDR4 2400MT/s non-ECC, 4GB, 8GB, or 16GB SODIMMs.

Steve

Yeah that's not likely to be Unbound. It's exhausting the RAM and swap space (if you have an SSD) so something is using far more than expected.
Try running top -aSH at the command line to see what is using it if this is still an issue.

Steve

I had exactly the same problem today, with my sg-3100.
Luckly, I also had a backup config and a 2.4.4 p2 firmware in a pendrive.
Installed, upgraded, restored, download blacklist from squid/pfblocker, restored my keytab file to squid folder, and everything is working perfectly again.
I will perform the reboots from now on with the F option, to force fsck.

register and open a ticket at
https://go.netgate.com
they will assist you

Ok I messed up some DNS settings. All better now.

I understand, thanks for your fast reply .

Glad you have your XG-7100 back on track. ☺

-Rico

@vladanpopovic said in locked out - reset not working - SG3100:

address i get is not 192.168.1.X but something like 169.254.29.154 with a subnet 255.255.0.0 - I have no idea where this address comes from.

The DHCP client running on your device (PC, Phone, laptop, whatever) will auto-assign itself an 169.254.0.0/16 after a certain time-out : when no DHCP is answering its request for an IP/DNS/Gateway..

Yeah moved, sure didn't belong in the TNSR section.

That is odd. Are there no other log messages around the time of the reboot? Anything from before the reboot?

Since you can somewhat predict the occurrence, could you leave a system connected to the console port logging the output from there to see what happens? It may have some better info.

From the general symptoms it sounds like a power/environmental issue somehow, perhaps it's enough to trip the 5100 but not a UPS, though at least for me, my 5100s don't seem to be phased by small power blips even without a UPS.

If you leave the console connected and there is nothing logged before the reboot, then it would almost have to be power or hardware. A hardware issue would almost certainly be more random/less predictable, though.

ix0-ix3 should be assigned but not enabled by default. igb1 is LAN by default and that's where you be given an IP address via DHCP.

https://docs.netgate.com/pfsense/en/latest/solutions/sg-5100/io-ports.html

Steve

You would need to re-assign the WAN to ix0. By default it uses lagg0.4090 to connect to the Eth1 port via the internal switch.

So Interfaces > Assign. Change the dropdown on WAN to ix0. Either remove OPT1 or assign that as some other port and save.

Steve