Restore backup on new hardware - webui inaccessible after saving interface assignment.

moosport

Install pfsense in new hardware (x11sdv). Able to access webui through one of the ports.
Initial restore from backup file. pfsense prompt to assignment interfaces.

Change both WAN and LAN.
Click save.
webui immediately do not response.
4.PC connected directly to pfsense lost connectivity

Tried different method.

Change one of VLAN interface.
Click save
try to change different tab for another VLAN. webui immediately do not response.
4.PC connected directly to pfsense lost connectivity

Not sure what is the issue.

SteveITS

@moosport from which interface are you connecting if you change LAN?

moosport

@SteveITS

WAN - igb0
LAN - ixl2
PC connected to igb1.

If I connect PC to the switch with uplink to pfsense, same problem.

SteveITS

@moosport You are clicking Save but not Apply?

I previously found some odd behavior:
https://redmine.pfsense.org/issues/14591

moosport

@SteveITS

Yes, It happens when saving. When I first attempt the upgrade last week, I clicked on Apply Changes on 1 interface change and lost access immediately.

I surmise I applied changes for WAN and I was connected to downstream switch. LAN was still pointing to old interface. This time around I made sure to click Save only for WAN, LAN and all VLANs. But same issue happen after the first save.

SteveITS

@moosport hmm and igb1 still has its own unique subnet? They are not overlapping ?

What does it show on the console after this happens?

stephenw10

Yeah check for a subnet conflict.

Is igb1 even assigned in the new config?

What does the console show?

moosport

@stephenw10 said in Restore backup on new hardware - webui inaccessible after saving interface assignment.:

Yeah check for a subnet conflict.

Is igb1 even assigned in the new config?

What does the console show?

There are no conflict. Subnets are the same from restore.

Did not get to configuring igb1. Lost access.

Console has WAN ip and gateway IP assigned.

In DHCP server, gateway static ip is assign per MAC address. Does it needs to be updated before interfaces assignment?

stephenw10

So you moved the PC you're doing this from to LAN? Above you said it was connected to igb1.

You're passing DHCP leases to known MAC addresses only? That should be fine from pfSense's point of view. Of course the client will see the DHCP server changed MAC address and may reject leases if that's also locked down.

Does the client get a lease in the expected subnet?

Can you ping out from the console to the client device on LAN? Or to anywhere?

moosport

@stephenw10 said in Restore backup on new hardware - webui inaccessible after saving interface assignment.:

So you moved the PC you're doing this from to LAN? Above you said it was connected to igb1.

You're passing DHCP leases to known MAC addresses only? That should be fine from pfSense's point of view. Of course the client will see the DHCP server changed MAC address and may reject leases if that's also locked down.

Does the client get a lease in the expected subnet?

Can you ping out from the console to the client device on LAN? Or to anywhere?

Not those connected to the switch downstream from pfsense.

I did not get to test from console as I run out of time.
I was expecting a quick migration with moving the cables over. Run restore from backup. Reboot all switches.

stephenw10

If you're using static ARP anywhere it could result in this kind of breakage. Almost always a bad idea to use static ARP for this reason.

moosport

@stephenw10 After a few hours, I got new hardware working. This time I pre-edit the backup xml file and rename interfaces for WAN, LAN and VLANs.

After restoring the backup config, there are a few setting needed to be fixed. Namely dhcp for vlans had to be re-enabled. ip address ranges for wireguard was transposed with another vlan.

Multiple reboots of switches. Only outstanding item is UPS configuration need a quirk added.