Fresh installation of 2.6.0, restored configuration but LAN interface changed
-
Hello.
Here's a brief overview of my pfsense confg:
I have 5 identical intel gigabit nics, one is WAN and 4 for my LAN which I have aggregated as LAGG0. I have around a dozen vlans configured and each is assigned an interface on LAGG0.Today I performed a fresh installation of pfsense 2.6.0. I downloaded a backup of my 2.5.2 configuration ahead of time, then after the installation I let the system reboot, bypassed my switch and connected my laptop directly so I could log in to the web configurator and then restored my configuration. After that completed, I waited until I had confirmed that all packages had been reinstalled (though I needed to manually reinstall avahi and freeradius.)
My issue is that after restoring, the last interface that I had assigned to the system long before today (VLAN 1031) is now appearing as the LAN interface as if it was the first interface configured, which is causing its ip adress 10.10.31.1 to be returned when I perform a DNS lookup for the hostname of my pfsense box, when in the past, I would get 10.0.0.1.
I reinstalled on the same hardware with no modifications so I'm not sure why it has decided to change the interface order.
- Did I do something wrong?
- Is there a way I can specify which interface I want to be LAN, OPTx, etc?
I do remember having a heck of a time configuring the LAGG interface to use all LAN ports and assigning the correct VLANs in the past, so perhaps this was bound to happen based on my interface configuration...?
I am aware that I can always start over from scratch, but I would obviously prefer to avoid that.
In any case, any suggestions or advice would be greately appreciated.
Thank you!
-
I'm sure it's not supported officially, and I'm willing to bet that it is highly frowned upon to manualy fiddle with config files, BUT I was able to manually adjust a copy of an XML configuration backup such that my LAGG0 interface is LAN and my other interfaces had the correct OPTx name that I wanted. I was sure to update all other references to these interfaces in places such as filter rules, etc. After making these edits, I restored from that manually edited backup file and everything seems to be working as expected without any issues. I still have the original in case issues arise and I decide to revert back to that known state.
-
Hmm, odd. I wouldn't expect anything to change there unless the NICs themselves were changed.
Sometimes editing the config file directly is the easiest way. You just have to be careful. It's all too easy to make a typo and end up with something that won't load.
Re-assigning interfaces like that is a typical scenario where editing the file is often the simplest solution. You shouldn't need to change anything in the rules, the only definitions using the physical NICs would be the Interafaces and LAGG. Even the VLAN should noy be in your case because they are on lagg0.
Steve
