@mcury Yes, just wondering out loud if a restart would have cleared that condition. If not, that would imply something was changed/bad that wasn’t in the configuration, yet is persistent.

@LeeS said in 7100 1U and 10G Speeds: My testing has been from a laptop on the LAN (cabled at 1G) through a web browser connecting to the Netgate 7100, and then running Speedtest from the command line Do you mean the GUI command prompt? That itself uses some CPU cycles. Better to test at the actual comm and line via SSH if you have to. But, yes, testing from the firewall directly like that will always be lower that routed traffic. You could tune the firewall to give a better result there but that doesn't really matter when what counts is what clients behind it can see. So, also yes, a real test here should be run from clients behind the firewall. Either a 10G connected client or several 1G clients running at the same time. But I expect to see somewhere in the 3-4Gbps range when testing that way.

@johnpoz said in the issue is as I warned for and is now an exploit: If I had to guess, he has some sort of Aphasia, maybe drug induced? hahaha.

@stephenw10 said in 1541 HA throughput and port configuration problem: If it's less than, say, 3Gbps it should be fine 3Gbps for each fiber, so 6Gbps ? It provides a good margin from now I think. Currently, each fiber is at 800Mbps.

@SteveITS said in Upgrade 1100 to 21.02 lost DHCP: If it's that old it probably can't get current anyway: https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades-1100-2100.html I would reinstall (it's a free ticket to get the file) and restore from backup. Though "Bad device mmc 0" doesn't sound good. eMMC has a lifetime but you probably can't install the utility to check that in this state: https://docs.netgate.com/pfsense/en/latest/troubleshooting/disk-lifetime.html Yes, I logged a ticket and did a reinstall. Restored operations. Thank you for the disk lifetime link.

Update: Was able to contact negate support and they assisted me thanks.

Know this is an old post but just wanted to add thanks. Had exactly the same request and it was baffling me how to setup. This post answered it perfectly. Much appreciated

Hmm, that driver is in-kernel for anything recent I've tested. In OpenWRT 23.05 you might need to add the driver but it is supported: Thu Jan 25 20:18:28 2024 kern.info kernel: [ 3144.289358] usb 2-1: new full-speed USB device number 2 using xhci-hcd Thu Jan 25 20:21:56 2024 user.info kernel: [ 3352.280701] kmodloader: loading kernel modules from /etc/modules.d/* Thu Jan 25 20:21:56 2024 kern.info kernel: [ 3352.289372] usbcore: registered new interface driver usbserial_generic Thu Jan 25 20:21:56 2024 kern.info kernel: [ 3352.295985] usbserial: USB Serial support registered for generic Thu Jan 25 20:21:56 2024 kern.info kernel: [ 3352.302595] usbcore: registered new interface driver cp210x Thu Jan 25 20:21:56 2024 kern.info kernel: [ 3352.308220] usbserial: USB Serial support registered for cp210x Thu Jan 25 20:21:56 2024 kern.info kernel: [ 3352.314219] cp210x 2-1:1.0: cp210x converter detected Thu Jan 25 20:21:56 2024 kern.info kernel: [ 3352.320194] usb 2-1: cp210x converter now attached to ttyUSB0

The SSDs are usually mounted in brackets. The power and SATA cables can be a bit tight if the riser card is present. [image: 1706207999371-1537-sata.jpg]

@stephenw10 I discovered I was connecting console too late after boot. Left it connected and restarted. Was able to interrupt boot to the Marvell prompt. I'll try USB recovery next. Thanks, M

There are some things you can see from uboot. Firstly that at boot it reports: Model: Silicom Rogue-2 CPU 1200 [MHz] L2 800 [MHz] TClock 200 [MHz] DDR 750 [MHz] DRAM: 3.4 GiB You can check the board info: Marvell>> bdinfo arch_number = 0x00000000 boot_params = 0x00000100 DRAM bank = 0x00000000 -> start = 0x00000000 -> size = 0x04000000 DRAM bank = 0x00000001 -> start = 0x05400000 -> size = 0x7AC00000 DRAM bank = 0x00000002 -> start = 0x80000000 -> size = 0x40000000 DRAM bank = 0x00000003 -> start = 0xC0000000 -> size = 0x10000000 DRAM bank = 0x00000004 -> start = 0xE0000000 -> size = 0x08000000 baudrate = 115200 bps TLB addr = 0x7FFF0000 relocaddr = 0x7FF36000 reloc off = 0x7FF36000 irq_sp = 0x7F623350 sp start = 0x7F623350 Early malloc usage: 228 / 2000 fdt_blob = 000000007f623360 And adding up those sizes gives 0xD6C00000 = 3602907136 = 3.6GB = 3.35GiB

It's front to back. So from the IO panel to the Power Supply.

@Diane9K I agree with you, the information was helpful

@stephenw10 ended up factory resetting and rebuilding from scratch. Had to do factory reset it twice, but the behavior is now gone. Thank you. Mind giving some of comments upvotes? I am running into another issue which I am attempting to create another post on in a different section of the forum, but I am hitting the spam blocker.

I also purchased a heat sink for my SG2100MAX, I do not think it needed it but it helps keep it cool. Looks like the same vendor except mine is the 2242 M.1 [image: 1705774876059-img_0095.jpeg] I also got one for my pcie mini wireless card. [image: 1705774938458-screenshot-2024-01-20-at-00.12.40-resized.jpeg] My SG2100 uses passive cooling. With the minipcie wireless card and the SSD the heatsinks can go a long way to help in the California summer heat waves. We will see this summer. The same 2100 cpu is in the Raspberry PI and it will use CPU throttling if it gets to 80C. I am also going to add a heat sink on the memory and the cpu next week.

I just went through the same upgrade (my SG-1000 was a rock for the ~7 years I had it in use) and found this thread very helpful. After a few attempts, I was able to get a working xml that imported everything correctly into the SG-1100. I had a bunch of vlans with opt interfaces that needed to be re-mapped into the internal switch. I started by booting the SG-1100 and exporting the default config to look at side-by-side with my SG-1000 config. I decided to keep my interface mappings of <opt#> to vlan consistent, so I re-mapped the builtin OPT port on the SG-1100 (<if>mvneta0.4092</if>) to <opt0> in my xml file. Since the SG-1000 doesn't have this port, my initial conversion process left it unused In the <interfaces> and <vlan> sections, I merged the SG-1100 defaults with my custom interfaces/vlans for the custom interfaces, I changed all the <if> tags from cpsw* to mvneta* but kept the subinterface numbers the same for the vlans, I updated the interface names to match what the resulting data interface data I also had to copy the <switches> section out of the default SG-1100 export and populate the <vlangroups> and <swports> subsections with the proper port tags / pvids for my vlans Just sharing my notes in case anyone else is searching for help with the same upgrade.

@stephenw10 Yes, exactly. No traffic. The downward one never flashes. I'm going to try to get spf+ modules and install the community version because I'm going around in circles :(

Just an update - I swapped out the router last night, moved the main router to my desk with the intention of booting it up isolated and connected only to my laptop - but it failed to boot! Luckily I still had the recovery USB handy - so I just did a usb recovery and restored the config....so I guess that is one way to upgrade ;) thanks again for the suggestions. J

You are able to connect to the serial console? What do you see when you try to boot the USB drive? How does it fail? https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html Steve

Yup updates are always included. And in fact you do have TAC-Lite with any Netgate hardware so you can open a ticket for basic setup, config conversions, firmware requests etc. Steve