Requested ^pfSense Config viewer^ (seeing configs on a dummy machine)
-
I made significant physical changes to the NIC's in my pfSense system. During the migration from the original NIC's towards the new NIC's, I made a mistake, which made my config completely unusable.
The problem is that pfSense does not work any more at all(!) if one used NIC fails / is replaced.
If the replacement is a planned action, you can migrate by moving all interfaces to a NIC which keeps in the system remove a card, place another one and mover the interfaces back to the new cards.What ever, I made a mistake and lost my (complex) config.
As a result I had to almost completely rebuild the config. That worked for 80% but there are still issues left.
For that reason I would be glad if I could load the old config in a dummy not working machine which could show me the config like it was in the original situation.
Of course I can to a certain extend read the config files to see how the previous config was, but that is not exactly easy and hardly usable to see what is missing in the new config.
So as the title suggest, I would be very pleased if I could see my older configs on a ^dummy^ pfSense machine, so that I could compare them with the actual config in my actual pfSense system.
And of course, I absolutely not like the way pfSense react on NIC changes or failures !!
-
You can load it in a VM that has the same number of NICs. You may not be able to use the same drivers so you'd have to re-assign them when you import it. But it should work.
-
Stephen, I tried it ..... and it is a drama ...
One of the problems is the way that interfaces should be assigned.
You have NIC's virtual or not and based on the Interfaces you create VLAN's
and the vlans will have interfaces. That is the only reasonable option!So I defined a VM having six virtual NIC's. And then started the VM
(I think I the configs to see did have five NIC's, two or four being part of a lagg, used in favor of nearly 20 vlans)It start asking to define the vlans ....... that is .... bizar ...
The first thing to do is to connect the original NIC's (or laggs) with the actual NIC's (in this case virtual NIC's).
And assuming that the relation ^old_NIC's to vlan's^ and ^new_NIC's to vlans^ are the same you are all ready done !!
As it is now IMHO ....... terrible!! ......
Not for this VM-case but in general
... asking to assign nics which where present before .... is bizar ....
... switching the whole firewall off if one NIC is failing or changed .... is bizar -
It should ask you to reassign the NICs before it reboots in the GUI.
But of you have laggs and VLANs I would just edit them in the config before restoring it.
