PfSense UI Not Updating frr.conf
-
I have an issue with a physical appliance. I Installed the latest FRR pkg and configured and all was well for some time. Now I'm having issues and any changes I make in the UI are not saved to the running config.
I can add neighbours, change neighbour settings, add published routes....frr.conf just stays the same.
I may have caused this by making a manual update to frr.conf running and coping to saved, but I'm unsure.
I've removed the FRR pkg, reinstalled, and all my config is still there.
Is there a way (I guess through the shell) to fix this issue, remove everything I have configured and start afresh? The device is 2000 miles away from me so reimaging it is not viable.
I'm logged in as admin....
If someone can tell me the folders or files I need to delete after uninstalling FRR to start afresh that would be great. Otherwise, if there's an easier alternative I'm all ears.
Thanks,
Jamie. -
I also found this in the frr-reload.log file:
WARNING: frr-reload.py failed due to vtysh (exec file) exited with status 13
-
Guys this shouldn't be a difficult question. If nobody on this forum can tell me how to remove all traces of FRR and start again, can someone at least point me to the developer that can?
This isn't funny. I've approved purchase for Netgate as out on prem and cloud firewall solution and this question must have a simple answer.
My next step will be to remove all Netgates from my international hybrid VWAN.
-
@jamiegb this is a forum only, you should contact https://www.netgate.com/support
-
@pete35 Appreciate that but this is the CE so AFAIK no support.
-
OK well I managed to figure it out myself.
First off, when you configure FRR or any of its subcomponents, you should note exactly which order you configured every component. When you want to, for example, delete a route map which is associated with a BGP Peer, the UI becomes divorced with the config file. The UI does not properly remove relationships between the two components (or if there's more links) and the config file is left in an unmanageable state (from the UI perspective).
To fix this issue:
- Uninstall the frr package
- SSH to PfSense and enter BSD shell (option 8)
- Locate all residual frr files left behind (no removed from package removal) by running
find / -name frr
andfind / regex '.*frr.*'
- Delete all the files and folders related to frr. In my case, there is nothing else in the OS which matches the name frr so delete all you find unless you know something is not related to the frr module. To remove directories add the -r switch to rm, eg
rm -s /var/run/frr
- Download a new backup of PfSense
- Open your .xml configuration file in your favorite XML editor (I use Notepad++)
- Search for the term <frr
- You will find all the PfSense configuration left behind when uninstalling the package should really remove it.
- Delete out all <frr.... elements / sections of XML
- Restore your backup to PfSense
- Reinstall FRR
There you go. Clean install of FRR. You're welcome.
-
I had the same problem. I was able to solve the problem, with clearing the "SAVED frr.conf" field under Services --> FRR --> Global Settings --> Raw Config.
After clearing the field, it was possible again, to use the GUI to configure frr. -
@schannes The documentation is not entirely clear but you are correct. If the config is saved than any GUI elements you set are not saved. You have to clear it first. Its wonky.