@stephenw10 said in SG-2220 finally got the bug:

It would have been 2014. Might have been some in 2013.

No worries.. I was just curious.. Decent little box.. I shall miss it. ;)

@SteveITS Thank you.
Seems like the issue has been sorted.!!!

@pmwqld said in Netgate 4100 Failes to boot after storm:

@mcury Do you have a make/model of them?

iClamper is a company with a great reputation in Brazil.
We don't have a great infrastructure, so everyone uses it around here.
I have customers with farms, and if I don't use those there, especially there, every now and then lightning burns equipment.

It has a varistor component built in, it is like a little sponge or pillow that can protect you even if you don't have proper power grounding.

If you don't find it in your location, search for good companies with good reputation.

Out of my head, I probably bought more than a hundred of these in the past 5 years or so..

This is a guy testing it, video is in Portuguese, but you can generate subtitles or perhaps just watch it without audio to see how it works.
Youtube Video

As as test set the 1100 itself to use some external DNS server and recheck.

@bigsy Thanks, that's an interesting idea, I'll dig into it.

@Lugie said in Netgate 2100 PPPoE Throughput:

From what I see on other forums, people with fibre connections just don't use limiters anymore.

If you have a symmetrical (or very close to symmetrical) connection, then IMHO "buffer bloat" is kind of a solution searching for a problem. It was much more of an actual issue with highly asymmetrical connections such as the early DSL technology. It can also still be an issue with cable ISPs that offer say Gig download speeds but maybe only a few tens of megabits/sec upload speeds. For example, before my symmetrical Gigabit fiber connection I had 1 Gig down and 50 megabits/sec up from a local cable ISP. The actual speed tests wound up averaging about 800 or so down and 49-51 up. That was an asymmetrical connection.

Not saying Limiters don't have their place in certain specialized applications, but for most home users with a symmetrical connection (where download and upload speeds are the same), they are not needed.

Yes, the Netgate 4200 supports IIMB and can help with WireGuard, more details here:
https://docs.netgate.com/pfsense/en/latest/hardware/cryptographic-accelerators.html

@Koent The 4200 does not have a SFP/SFP+/SFP28 port, so no, it cannot possibly be made to work with the 4200.

You will need it’s older sibling - The 4100 - or it’s bigger brother - the 6100 - so get such a port.
It will likely work just fine in those if it works in ubiguity or mikrotik. Generally most SFPs slot compatible modules works in my experience.

Add me to the list of successful chip-pullers. SG-5100 would not boot at all, no boot menu. I pried the eMMC chip off the board and it boots right up now. 👍 Installed a M.2 drive while I was in there, just installed pfSense to it and restored my config. This thing is hopefully back in service for a bunch more years.

Both look like a filesystem issue of some sort which would be corrected by the reinstall.

However since uboot is completing on both the switch ports should be isolated.

Try interrupting uboot to reach the Marvell>> prompt then run printenv. Make sure there is an env named switch_disable. If it's missing you can force update uboot from pfSense to add it. That should normally have been added during a uboot update.

The default code does not. You could write a custom form that included an email address as a mandatory field but it would not be confirmed. You would also have to parse the logs to recover those addresses or include some code to export them.

@dmad

Thanks very much for the 2 links ! I am going to check them now ...

22.05 is tha last version that is supported for the sg1000. It will show that error.

So the issue you're seeing is that it's generating repeated alerts?

Steve

@stephenw10 That's built-in and I never had any issues with it on any other site:

363bf467-7bb9-43bb-bbb6-e53d8775ebf3-image.png

Go a new cable and it works now! Thanks.