@SteveITS Hello Steve, Ok, filled out what I think is the correct request to get an image file, will see what happens. I appreciate in information. After the ports went dead, I lost access to the GUI even though a keyboard and monitor connected to the device was acting normally.

I was able to solve this issue....looks like the IP address didn't get updated by the DDNS client...i found out by calling Verizon FIOS and cross checking the IP address with what Cloudflare (my Domain provider). All is good now...back in the game. Thank you for all of your support and ideas. jim

Yes, pfSense has a startup and shutdown sound that plays if you have a system speaker. Again that's an x86 thing though. There's no connect to the internet sound but it would be trivial to add, on x86!. I came from IPCop myself, and Smoothwall before that.

I would expect it to start after restoring power. It can't see any difference there between that and pulling the power cable. Does it start if you press the power button? Is it connected to a UPS? Steve

I assume it still responds from the LAN side though? And the other device never loses it's IP address? I would try running a packet capture on WAN when it fails to see what's happening. I expect to see pfSense either ARPing for the gateway or trying to renew it's DHCP lease. You should see the DHCP client logging that though.

@GeekyTim said in SG-1100 - Unable to check for updates and unable to see/install packages: Updating pfSense repository catalogue... pkg: No SRV record found for the repo 'pfSense' pkg: An error occured while fetching package This could be simply a DNS issue. Try running: pkg-static -d update That will show more error info.

@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