SG-2100 HANGING UNIT

kevs

Yes it is 22.05 because it was booted via USB but when I removed the USB it will came back to the old one which is 22.01 I do not know why it cannot rewrite the new version in my device.

kevs

Hi @bingo600

When I removed the USB, this now happened when I reboot the firewall.

bingo600

@kevs
I have no experience with the 2100 .....
Just wanted to point out that it wrote 22.05 in the screenshots you provided.

Just a thought ... Are you sure you installed the 22.05 onto the 2100 disk , and not the USB

On an Intel system , I don't think o have ever seen the "pfsense login prompt" , when booted from an Install-Stick.

/Bingo

Gertjan

@kevs

While rebooting, disk are logically detached - also known as unmounted.
Like Windows, FreeBSD doesn't like it at all when USB drives are removed without OS intervention.

ugen1.2 - da0:umass etc are all names for your USB stick.
Like Windows, you do not install Windows on the USB disk you install from, but to the hard disk build in your system.
It really looks like somewhat unexpected happened to the drive : did you install pfSense onto the USB drive instead of the build in "2100" drive (whatever its name might be ?)

Rebuild your USB stick.
Re install pfSense, and this time, look carefully to the list with 'drives' listed when choosing the destination disk.
There should be a 'device' that is the drive build into the 2100. Use the pfSense "2100" doc to know what it looks, how it's called.
If nothing is listed ... well, that would be an issue. Drive do die ...

stephenw10

What was the exact name if the recovery image you wrote to the USB stick?

That doesn't look like the correct image to me.

Steve

stephenw10

Or in fact it looks like you have an m.2 SSD in your 2100 and you may have installed 22.05 to the eMMC instead?

kevs

@gertjan said in SG-2100 HANGING UNIT:

Re install pfSense, and this time, look carefully to the list with 'drives' listed when choosing the destination disk.

Actually, there is no prompt disk destination if where about to install the new pfsense version.

what I did is I made the USB into a bootable USB in which I put the pfsense image, then I plugged the USB into the firewall then powered it up, when it was now booting I pressed any key to stop the auto boot then I type the "run usbrecovery" in the command line. I am expecting the prompt to let me choose in what location would I want to install the new version but no prompt at all instead continue booting from the USB image.

kevs

Hi Sir @stephenw10

This is the image name that I downloaded over the internet and write on the bootable USB.
pfSense-plus-Netgate-2100-22.05-RELEASE-aarch64.img

FSC830

As far as I know you need a recovery image for running a new, clean setup.
The recovery images can not be downloaded in same way as the update images, you need to create a support ticket (TAC) and they will send you a download link.
Naming of these images is usually like this:

pfSense-plus-Netgate-3100-recovery-22.05-RELEASE-armv7.img

Regards

kevs

Hi @fsc830

The reason why we're going to reinstall the pfsense images is that the network interface of our Netgate 2100 firewall has a link-up problem. Actually, when we plugged in the device and connect the LAN cable it will link up and can ping, but after a couple of minutes or when the device is getting warmer, the connection will automatically drop and the light indicator in the ports are not responding or even lighting when we plugged the cable in each of every port.

Do you think if we reinstall the image it can fix the problem of our device?

FSC830

I dont have a glue if reinstalling the image solves this issue.
If this is a hardware related issue I am rather sure it wont do that.

I just wanted to pinpoint that IMHO you are using a wrong image for reinstalling if trying to run a new setup from scratch.

Regards

Gertjan

I agree with @fsc830

If it was a "wrong settings" settings issue, I would start by not retrieving or using the exiting configuration.

@kevs said in SG-2100 HANGING UNIT:

it was now booting I pressed any key to stop the auto boot then I type the "run usbrecovery" in the command line. I am expecting the prompt to let me choose

When the installer form the USB installer auto-start, you should not interrupt it.
If there was something to recover, there will be an option in the installer menus to indciate that you can recover it.

stephenw10

@kevs said in SG-2100 HANGING UNIT:

This is the image name that I downloaded over the internet and write on the bootable USB.
pfSense-plus-Netgate-2100-22.05-RELEASE-aarch64.img

That's the wrong image. It needs to be the recovery image:
pfSense-plus-Netgate-2100-recovery-22.05-RELEASE-aarch64.img.gz

That is the live boot image which is why it simply reverted to the previous install when you removed it.

Where did you get that image? It's only made available in special circumstances. Do you have the ticket number?

Either way I would open a new ticket and request the recovery image.

Steve

kevs

Hi @stephenw10

I already requested the right recovery image and already installed the new version of pfsense, so I assume that the main problem with my firewall which is the LAN link connection will solve but still down after a couple of minutes.

Perhaps, you have other solutions that you might recommend to solve our problem. Can you help us, please?

Gertjan

@kevs

These are the things you can do :
Swap cables.
'Force' an fixed speed,, like 100Mbits/sec, do not use "auto select".

I doubt if there is anything else you can do.

kevs

@gertjan said in SG-2100 HANGING UNIT:

'Force' an fixed speed,, like 100Mbits/sec, do not use "auto select".

@gertjan

We already did, changing the cables but still, nothing happens.
How will we fix the speed? We cannot link the connection, as in access.
For the first time plugging in the firewall after a couple of hours, the Lan will link up and the indicators will light but after a couple of minutes, it will take down again, with no connection and no lights on all the available NIC unless we will unplug the firewall for a couple of hours then plugged it back but still it will go on that routine.

FSC830

If this is a hardware issue you cant fix it - except swapping the device.

Regards

stephenw10

I still don't see anywhere that you tried running etherswitchcfg at the command line which was the first thing I asked you about.
You should see something like this:

[22.05-RELEASE][admin@2100-3.stevew.lan]/root: etherswitchcfg
etherswitch0: VLAN mode: DOT1Q
port1:
	pvid: 41
	state=8<FORWARDING>
	flags=0<>
	media: Ethernet autoselect (none)
	status: no carrier
port2:
	pvid: 42
	state=8<FORWARDING>
	flags=0<>
	media: Ethernet autoselect (none)
	status: no carrier
port3:
	pvid: 43
	state=8<FORWARDING>
	flags=0<>
	media: Ethernet autoselect (none)
	status: no carrier
port4:
	pvid: 44
	state=8<FORWARDING>
	flags=0<>
	media: Ethernet autoselect (none)
	status: no carrier
port5:
	pvid: 1
	state=8<FORWARDING>
	flags=1<CPUPORT>
	media: Ethernet 2500Base-KX <full-duplex>
	status: active
vlangroup0:
	vlan: 1
	members 5
vlangroup1:
	vlan: 41
	members 1,5t
vlangroup2:
	vlan: 42
	members 2,5t
vlangroup3:
	vlan: 43
	members 3,5t
vlangroup4:
	vlan: 44
	members 4,5t

Except yours won't be running in DOT1Q mode with the same VLANs I have configured.

Can we assume all 4 LAN ports behave the same?

Steve

kevs

Hi @stephenw10

Please see attached screenshot below for your reference in running the etherswitchcfg command.

stephenw10

Mmm, that looks broken. hw-loopback is not valid there.

Try to power cycle the unit completely. Shut it down then remove the power for 10s.

After it reboots run etherswitchcfg again and see if that shows differently and if the LAN ports now function as expected.

If that's just happening spontaneously during normal running that points towards a hardware issue.

The only time I've ever seen that was in a unit that had a cell modem fitted which is why I asked you about that earlier.

Steve