@michael2z said in Upgrading a Netgate 5100:

Has anyone succeeded in upgrading a Netgate 5100 to the latest pfsense version. Any do's and don't's appreciated.

I have a Netgate SG-5100 device. I maintain it on the most recent pfSense Plus versions as they are released, so I'm never more than 1 version behind. I just click the Upgrade button and let it go. I have no optional packages installed. Generally takes about 5 - 7 minutes if I recall for an upgrade.

You would need something in between to act as a USB host and bridge the two USB-serial connections. Like a RasPi perhaps. But if you're doing that you might as well just use the RasPi as a terminal server.

@stephenw10
My only thinking is you don't want to bridge any pfsense interfaces, use layer 3 routing in a larger network between interfaces. Layer 2 has a lot of baggage. The same if you are using slow communication lines. Route over them, layer 3 instead of bridging them, layer 2. At least it was that way 20 years ago with a network of 4000 Windows clients. I would think the principles would still apply for the fastest speeds on large networks.

Hello,

I was able to configure the WAN correctly by defining a VLAN with the tag required by the ISP and define the WAN on this interface.

A step-by-step guide with screenshot is available here: https://ic.rcasys.com/s/RantzDKFxHjX3Ba

Thanks @stephenw10 and @keyser for your support!

We still test on older hardware because we need to know if there's a specific issue that might apply before release. I tested 24.11 on APU and FW-7551 for example. However after EoL if there is some hardware specific regression we can't guarantee to fix it. Most of the time it's trivial to fix so we do. For example at some point the 3100 will no longer be supported because the effort required to get it to build as the only armv7 platform we have will be too great. It's no longer a tier1 architecture in FreeBSD so there are often things that break there.

Thank you. It turned out that I had a faulty interface setting that kicked in when the unit was rebooted. I had to revert to reset the device, restore previous settings and delete the faulty setting to get all working again.

A learning process indeed.

Thank you for the suggestion!

Yup if you have WoL enabled for example the NIC will remain linked when the PC is in standby.

@KOOL43 Well thats hard to say. I have a 2100 with a running GPON 1.25/2.5 BiDi SFP trancievers from fs.com. Before that I tested it with a Nokia tranciever with similar specs, and that also worked without issues (but was a loaner). So I would expect it to work, but it’s impossible to guarantee it up front.

@mon007 said in Newly purchased Netgate 8300 Appliance.:

Hi @elvisimprsntr,

Thank you for your reply. We are using a brand-new UPS with all-new batteries. Unfortunately, both of our current units are not pure sine wave models. I’m a bit of a newbie when it comes to UPS systems, so I really appreciate your advice. I’ll make sure to purchase the required type.

Thank you again!

A pure sine wave model is likely to cost more than one doing "stepped aproximation". That's one way to know it's likely a pure sine wave box (along with the manufacturer explicitly stating that in their specifications).

The maximum throughput without any packages or VPNs on the 2100 is 600-700Mbps. No problem for 400Mbps. But if you want to pass 400Mbps over wireguard you are going to be CPU limited. If you want to do that with Snort or Suricata running, even more so. Memory shouldn't be an issue unless you load up ever list and definition in pfBlocker and Snort (which you shouldn't!).

@johndoe102 said in Kea DHCP and MAC Address Control (MAC allow) - no access after restart.:

if I set the IP manually to the different one , but from the same subnet ... I cannot connect to the pfsense

That implies it's not on or not functioning. Can you ping the pfSense LAN IP? Replace the patch cable between pfSense and your switch?

The logging is a known issue: https://redmine.pfsense.org/issues/15411

It will correct itself or you can restart syslogd to correct it immediately.

Increased CPU usage should only be when using he GUI. Try checking top -aSH at the CLI without the webgui open.

You could try adding a boot delay to the 1100 so the NUC has finished booting before it starts.

Though if it sends an escape sequence that can interrupt the boot that could cause a problem at any time. The # implies the root prompt which is an odd place to end up.

The 1100 logs everything once the kernel starts but it doesn't log input at the console.

@keyser Fair enough.

I already have a managed switch, but took it down recently. I currently have everything sitting atop my dryer. I am trying to reduce clutter. However, construction is coming soon 🤞and I will soon have a dedicated area for my Proxmox servers and this network equipment. I currently have an 1100 setup, a single OpenWRT router, and a POE switch up on the dryer now. The one renter just wants WiFi, no cables, so I can accommodate that with the OpenWRT router and vLANs. It's a far cry better than 2 OpenWRT routers, a managed switch, a PoE switch, and a Netgate 1100. My 1 bother is in an ADU just outside the house, so he has a separate OpenWRT router in bridge mode, connected to the LAN interface via a 100' Ethernet cable.

Probably more than anyone wanted to know, but Ok. Gotta go now.

I know this thread is old, but it helped me with my WAN uplink speed negotiation issue I experienced after updating my 2100 to 24.11.

Sometimes the obvious is the easy solution. After the 24.11 update, my WAN was set to 100BaseT. I spent at least an hour trying to figure this out, rebooting everything under the sun. Then I came across this thread, swapped out my cable, and BOOM! back to 1000BaseT.

Possibly, if it's actually physically broken.

Yes, just restore the full config file and it will pull in any required packages.

@marcg I've got that one in my cart. Waiting for the total to reach free shipping.

@jlbeebe +1. The plastic on the top half of the casing does not permit many micro USB cables to be fully inserted into the socket on the board.