Messages

If I make a change to the gateway configuration on the primary, and then sync to the secondary, the gateway parameters sync as well.

I believe this didn't use to the be case, but recently after upgrading from 24.7 to 25.1_7 and _10 I'm noticing this. It's not desired behavior; I would prefer to have different gateways on the secondary router. Was not-syncing a bug that was corrected? Is there a way to prevent gateway parameters syncing, but keep the rest of the config in sync?

Otherwise, I suppose I could create a superset of gateways, configure them in both places, and use a script to toggle the appropriate gateways on/off in response to a CARP event, but that creates extra complexity and chance for errors. If there's a checkbox or advanced parameter somewhere, I'd love to know about it.

There was another similar post as well, with no responses.

Thanks!

Still seeing this as well. Occurred during 25_1 migration on one router.

Is it just checking for a presence of extra .conf files? If so, which ones are ok?

If there's no easy way to check for a clean config, can we just do this? :

- turn off unbound
- delete all of /var/unbound
- reinstall the package, hope for the best
- re-enable and attempt to reconfigure via gui

I don't want to create two days worth of work just to avoid a message. But if this is safe, it might be ok.

Thx

[/api/routing/settings/searchGateway]

Time-machine post for googlers...

Use API endpoint /api/routing/settings/searchGateway.

It will return a json object detailing all the gateways. One of them will have:

Code Select Expand

"defaultgw": true,
which gets translated into the words "(active)" in the GUI. You can use that to determine the active routing gateway status.