well. you cannot import config to different device without manually editing the xml configuration
Eero 2017-10-24 14:03 GMT+03:00 Adrian Zaugg <a...@ente.limmat.ch>: > > Hi > > When loading a configuration file from a different device (with other > NICs) to a freshly installed pfSense, it correctly detects a mismatch of > the network interfaces and redirects the user to the interface setup > page. If there are VLANs defined in the loaded config, the VLANs are > still bound to the non-existent NICs, thus the user has to open the VLAN > assigning page and correct this. Pressing then on save, pfSense executes > the change immediately leading under unlucky conditions to the loss of > the connection to the admin interface of pfsense. > > In my opinion if pfsense discovers a mismatch in interface assignment > after restoring a configuration file, the changes made by the user to > VLANs and interface assignment should not happen immediately. It should > let the user finish all the reassignment work and then do the reboot of > the device like it does it always after restoring a config. > > How to reproduce: > - do a fresh pfsense installation and boot, connect to the web-gui > - instead of following the presented wizard, chose Diagnostics -> > Backup/Restore from the menu > - load a config using VLANs originating from a different device, which > has other kind of NICs built in (different brand e.g.) > - when presented with the interface assignment page, change to the VLAN > page and reassign a VLAN to the inner interface > - press save > > > Regards, Adrian. > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold > _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
