FRR starts exactly with the same configuration no matter what I do

Started by senseivita, June 29, 2023, 06:15:19 AM

Previous topic - Next topic
Hey all, :)

A while back I set up FRR from the GUI, but the lack of options and this problem where it would stop respoding to config changes (which I can only fix by reinstalling OPNsense and restoring an edited config backup without FRR) drove me FRR proper, v8 on the CLI/console.

However, after setting it up, enabling the daemons ([/usr/local]/etc/frr/daemons), and verifying it (along with watchfrr) would start; vtysh would create the config file and everything but in the end it always starts with the same configuration:


Building configuration...

Current configuration:
!
frr version 7.5.1
frr defaults traditional
hostname f.q.d.n
!
line vty
!
end


It completely ignores the config created on vtysh (written to /usr/local/etc/frr/frr.conf).

I searched for days for the config files or init script or whatever that was persisting that but I don't know much about FreeBSD so I couldn't come up with anything.

I found references to some files under an rc.d directory — I'm not sure which, given the they're a ton of these on repeated over several levels — but those files referenced didn't exist.

I removed FRR 8 and returned to the GUI version (os-frr), set it up but once again it won't send or receive any traffic. I noticed on neighboring routers there is no RIP or OSPF exchanged with OPNsense in their routing tables, only with other routers. And in OPNsense itself, the routing table lists only connected routes; it doesn't receive information either. The firewall is wide open on all affected interfaces.

I need to reset FRR, I think. But the file structure in FreeBSD in infinitely confusing even before getting to OPNsense's own customizations and I'm also trying to make OPNsense my main firewall, so reinstalling — that's full reinstallation or cloning VM template or reverting VM (not system-)snapshot. Otherwise it doesn't fix anything — each time there's a problem won't be an option anymore.

Could you guys give me some pointers how to do this, please? Finding out all related system files used by FRR.

Thanks.
I'm a bit dyslexic and it makes me forgo letters at the end of words. What gets written is written correctly though, I have good orthography in one or two languages, ironically. It's messed up, I know, I'm sorry. Just pretend you're my auto-complete. :)

It can be problematic going from using manual service to plugin because the plugin will not know all the files you may have created and can only reset what it knows. I'd try to clear all configuration files you wrote to the disk manually and also the file/directory /etc/rc.conf.d/frr as well as any contents of /etc/rc.conf relating to "frr".


Cheers,
Franco

Thanks,

Sorry for taking so long, I had been meaning to answer earlier but I had to exhaust all measures first. Y'know, do my part as well. :)

I'll make a list so I don't lose focus (ADHD), I...

- Uninstalled all versions of FRR
  - Including the pythontools package
- Open a text file to start documenting all of this
  - ...but forgot its name and now I can't find it :P
- rm -fR /etc/frr
- edit /etc/rc.conf to remove [watch]frr-related settings
- rm -fR /usr/local/etc/frr
- rm -fR /usr/local/etc/rc.d/{frr,watchfrr}
- found stuff in other directories, like the socket file in a var directory, (not in /var though, just some downlevel var) and some scripts inside an OPNsense directory, left those in place.
- Checked permissions on configuration files and socket files definitely the most tedious since I also had to find the docs for it too, fortunately they're actually quite straightforward :)

I reinstalled the CLI version first, didn't work. I repeated all of the above and reinstalled the GUI version; didn't work.



Running a packet capture on the interface connected to area zero I saw traffic of other routers but not of this one. FRR doesn't seem to be using the network at all because — I think I mentioned in the earlier post — it doesn't even learn RIP routes for which it doesn't have to form adjacencies in order to use them.

Now, I just reinstalled it, if I configure it now it will work for a while until a config change is required, if it doesn't go perfect, at some point it stops accepting, it seems, configuration changes and it's like it "decides to stay put" if you will. But, I have no proof, which is partly why I come for help. :/

Oh well, someone will catch it someday, thanks again, I've would've dropped it had I not seen your answer. :)
I'm a bit dyslexic and it makes me forgo letters at the end of words. What gets written is written correctly though, I have good orthography in one or two languages, ironically. It's messed up, I know, I'm sorry. Just pretend you're my auto-complete. :)