@keyser I have 1Gbps fiber at home too, and agree that there's a gap to be filled. Right now I'm using a 6100 and while I agree that it's a bit pricey for a home router, when you spread it out over the likely 5+ year lifespan of the device it really doesn't matter that much. A 4100 is coming "real soon now" and will likely be that goldilocks device you've been waiting for. I'm sure it would have been here by now if it weren't for the supply chain nonsense.

@stephenw10 The original pfsense device had multiple IP addresses on the WAN interface. When I migrated to the SG-3100, rather that using the primary public IP address, it was using one of the other IP addresses on the WAN interface. Once I realized this, I modified the WAN interface, then the clients were able to connect again. The SG-3100 in now in place and all is well. Thanks for your assistance.

I can confirm this issue, I restored my SG2100 and first up I did change to http and port 8081. I was not able to login using Brave. I was however able to login via ssh. I changed browser to Midori (doing this on a Manjaro Linux install) then I was able to login and I got a log entry on my ssh session stating that a successful login was made. Now I tried to switch back to Brave, I try to login, I do see the same message in the ssh session that a successful login was made but the browser blinks and empties the login fields and does not login. Starting a private window and trying to login succeeds. So this has to be some kind of caching issue. I can confirm that it is a caching issue, deleting the browser cache does do the trick. After that I am able to login in again.

@blackh0le

I would only expect to see that if there are no IPSec tunnels enabled. What have you tried so far? How is it failing? Can we see any screenshots? Logs? Steve

Log lines indicate the exact moment of the events : @leonroy said in Unbound was killed: out of swap space: Jan 11 13:01:33 unbound 63374 [63374:0] notice: Restart of unbound 1.12.0. and while it's starting - 15 seconds later : @leonroy said in Unbound was killed: out of swap space: Jan 11 13:01:48 unbound 63374 [63374:0] info: service stopped (unbound 1.12.0). and a small instance (< 1 second) : Jan 11 13:01:48 unbound 63374 [63374:0] notice: Restart of unbound 1.12.0. To make a long story, go to the Unbound / Resolver settings page and uncheck this : [image: 1641975254934-ffec4b58-bccf-4e36-8b6e-dc41c1cea202-image.png] Stick a post-it on the pfSense box that says : "Check the resolver logs again after 48 hours and see how many stops/restarts happened the last 48 hours". If you find "a couple" or even less : issue solved.

There isnt much practical use in combining them because of different speeds. Even with weights, still when one hits the 30Mbit will take notice, especially if downloading something. Of course If you are a caffee with casual users it wont matter. You can always configure the slower line as a backup, only. While doing this you can use the slower line for eg iot, or other "batch" uses like backup syncs etc.

@stephenw10 @keyser @stephenw10 Thank you all for your reply. I did manage to get the cheap alternative power adapter with the same voltage and ampere, device had the same behaviour as with the original power adapter. Am now guessing it's the device. Thank you again. Good Day. Sway

@luckman212 said in Netgate 6100 - devd firing an event on power button press?: Any chance that in the future we could get the power button to fire notify events to devd upon a momentary press (< 3s)? Since the button is only connected to the uc it would require a code update for the controller and that requires reflashing the SPI chip. It have to be a really good reason! Steve

@stephenw10 Thanks, got the right file for installation! Regards, Norbert

@pfimprudence sorry to revist this old thread but did you ever have issues with the 2.0a BIOS you installed from Super Micro? I see now there is a version 2.3 on Super Micros site. Did you happen to try that? Also do you happen to get the 1.3 version from Netgate and can share? We have the version 1.2c from 2017 and I have not been able to get any official updates from Netgate team. We need to replace the M.2 SSD on our 1537 and I imagine that there is better support for current devices including NVMe with the newer BIOS. Not to mention any security flaws on Intel Xeon CPU that might have been fixed. (Really annoying there is no BIOS changelog anywhere..) Thanks!

Ah, there we go that's about what I'd expect to see. One of the interesting things about iperf is that it's deliberately designed to be single threaded. Running multiple parallel streams using the '-P' switch does not change that, you are still running one iperf process. But, as you already tried, that means you can run it multiple times to test combinations of CPU cores and streams. You still see a better result using -P because the firewall and the NICs can use multiple queues and therefore CPU cores to move that traffic. Steve

@stephenw10 said in SG-1100 factory reset no GUI access no console access: Nope the cable has always been standard in everything we've shipped. The USB-serial chip is on-board and the cable simply connects to it. I decided to have some fun and dug up my "USB cable box", took out four micro USB cables and tested all of them on SG-1100 console compatibility. Each cable passed that test, confirming the standard (data) cables are okay

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