The fastest way back is probably to reinstall 23.09.1 clean if you have a config backup.

You should be able to login at the amnesiac prompt though. admin/pfsense or root/pfsense should work if it's unable to find any login config. Also try admin/root.
Otherwise root/<your_password> should work if it can still see that config.

Steve

Thanks Stephenw10 & Jarhead for taking time to respond to my post. My issue is resolved now.
All I wanted to do was to configure the Netgate 2100. So, the router was not connected on the WAN side. Just to my laptop on the LAN side. It turned out the culprit was my ethernet cable. Ever since the dial up modem era, I have been setting up my home LAN. I had never experienced a bad ethernet cable!! The one I was using now is a new one & fresh out of the box. I never suspected that this cable was the culprit.

What do you see on the serial console?
https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/connect-to-console.html

If it's booting as far as just one LED flashing blue it is mostly booting correctly.

How did you use the reset button?
https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/factory-reset.html

Steve

@stephenw10 said in Netgate hardware for latest Verizon ONTs?:

Not an Nbase-T port, so a 2.5G link will not work there?

Right, as far as I can tell from the available info it will do 1G or 10G and nothing in between.

We have seen some SFP/RJ-45 modules that do work but we can't guaranty that because the C3K SoC does not claim to support them.

Got it. Thanks for the clarification.

@John_McNoob said in NetGate 2100 Vlans:

Now my ruls look like this

Action = pass - Interface = GuestNetworks - Address Family= IPv4 - Protocol = TCP/UDP - Source = GuestNetwork subnets - Destination = GuestNetwork address - Destination Port Range DNS(53) / DNS(53)

Action = pass - Interface = GuestNetworks - Address Family= IPv4 - Protocol = Any - Source = GuestNetwork subnets - Destination = Invirt match = Address or Alias = Alias-name

Yes, that's fine.
Think, I messed some "inverts" up...

@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