Current best practice for persistent cable_guy configuration?

[amarburg (Aaron Marburg)]

Hi all. We’re currently using BlueOS 1.4.2

We’d like to add a persistent networking change (an additional default route). I believe this can be done by adding the appropriate entries to /root/.config/blueos/cable-guy/settings-1.json?

I want to be sure we’re modifying a file which will be read on startup (rather than one that is a dump of current state).

And would that also work with more recent BlueOS releases (1.4.3-beta or 1.5.0-beta)?

[EliotBR (Eliot)]

Hi @amarburg,

I’ve asked internally, and apparently:

@joaoantoniocardoso

• This is only possible in newer BlueOS versions (1.4.3 betas, or 1.5 betas, via the new routes API or the settings-v2.json file)
• For current BlueOS, you would need run your own service on startup to create that route every time (e.g. a cron job)

[amarburg (Aaron Marburg)]

Thanks for the followup!

We ended up solving the problem by configuring the system via DHCP. I will keep an eye on the routes/ API going forward, however.