Unbound settings overwritten

[pirx73]

I have unbound manager 3.25 running unbound 1.20
Unbound was installed using amtm's 5.1 "Install unbound manager" option
I wanted to enable "log-replies: yes" option
Unbound manager itself launches nano in view-only mode so i could not edit from there. Ok, no problem, file is located in
/opt/var/lib/unbound/unbound.conf
and i removed comment from the line.
Then in unbound manager i executed "1 = Update unbound files and configuration" to apply my changes
My changes are overwritten every time i launch this option.
What is the correct way to enable this option without it being overwritten?

 

[thelonelycoder]

Unbound manager may not read the config file before it updates files and configs - hence it uses the last variables it read during startup.
Best to manually edit the conf file, then reboot router. Or shut down unbound, edit and restart it.

 

[pirx73]

Thanks @thelonelycoder! this is what i figured out and did - edited config file from CLI, then from Unbound Manager stopped and started unbound.
Just a bit confused why you can't edit it directly from manager. Another thing i have to keep in mind - never use "1 = Update unbound files and configuration" option because it will overwrite my settings.
Should it behave like that?
EDIT: I get it. It reads config file only once - on startup, there is no option to make it reload config from changed file in any other way.

 

[Martineau]

I have unbound manager 3.25 running unbound 1.20
Unbound was installed using amtm's 5.1 "Install unbound manager" option
I wanted to enable "log-replies: yes" option
Unbound manager itself launches nano in view-only mode so i could not edit from there. Ok, no problem, file is located in
/opt/var/lib/unbound/unbound.conf
and i removed comment from the line.
Then in unbound manager i executed "1 = Update unbound files and configuration" to apply my changes
My changes are overwritten every time i launch this option.
What is the correct way to enable this option without it being overwritten?

By default unbound_manager starts in basic mode

and option 1 is to be used to reinstall/reset the current installation i.e. rather than tediously uninstall then reinstall any new installation modules etc. are retrieved from Entware.

If you start unbound_manager in 'advanced' mode, you will be able to access a comprehensive tools menu using option 3

unbound_manager    advanced

You can then edit the config file by simply using command vx which invokes nano to perform the edit.

 

[Martineau]

EDIT: I get it. It reads config file only once - on startup, there is no option to make it reload config from changed file in any other way.

You can load ANY config file inflight without needing to stop unbound by using the advanced menu command rl command.

You can use the vb command to backup the config file so you can test individual directives and save different versions of the config to easily restore using the rl command.

 

[pirx73]

Thanks! But how can i switch unbound to advanced mode from Unbound Manager which is launched from amtm?
Seems it always launches it in basic mode.

 

[Martineau]

Thanks! But how can i switch unbound to advanced mode from Unbound Manager which is launched from amtm?

post #4 shows the CLI command to be used, but I think you used to be able to switch between advanced/basic mode using a command from the unbound_manager command prompt.

Starting unbound_manager from amtm will always start unbound_manager in basic mode due to someone complaining that they were overwhelmed with 'unnecessary' menu options.

 

[Twiglets]

I have unbound manager 3.25 running unbound 1.20
Unbound was installed using amtm's 5.1 "Install unbound manager" option
I wanted to enable "log-replies: yes" option
Unbound manager itself launches nano in view-only mode so i could not edit from there. Ok, no problem, file is located in
/opt/var/lib/unbound/unbound.conf
and i removed comment from the line.
Then in unbound manager i executed "1 = Update unbound files and configuration" to apply my changes
My changes are overwritten every time i launch this option.
What is the correct way to enable this option without it being overwritten?

Edit the 'unbound.conf' file as required.

Start unbound in advanced mode:
Run 'sh /jffs/addons/unbound/unbound_manager.sh advanced'

You have a choice of 'rl' or 'rs' ...

'rs' will restart unbound ... ['rs nocache' will restart unbound without reading back the saved cache i.e. As if you started unbound from scratch]

'rl' will reload the conf file without stopping unbound.

then exit unbound menu with 'e'

[Oops late to the party !!! ... much refresh screen before replying.]

 

[pirx73]

post #4 shows the CLI command to be used, but I think you used to be able to switch between advanced/basic mode using a command from the unbound_manager command prompt.

Starting unbound_manager from amtm will always start unbound_manager in basic mode due to someone complaining that they were overwhelmed with 'unnecessary' menu options.

Thanks! I definitely did not complain about unnecessary options Now i know how to do it and it is fine by me Thanks again @Martineau!

 

[pirx73]

I hope @thelonelycoder does not mind - i tweaked unbound_manager.mod so it always launches unbound manager in advanced mode.

 

[TonyK132]

I hope @thelonelycoder does not mind - i tweaked unbound_manager.mod so it always launches unbound manager in advanced mode.

Would you share your tweak?

 

[thelonelycoder]

I hope @thelonelycoder does not mind - i tweaked unbound_manager.mod so it always launches unbound manager in advanced mode.

... which will be overwritten with the next amtm update. If I remember correctly @Martineau wanted it to start in easy mode.

 

[pirx73]

@TonyK132 I sure can, just thought is is quite "baby level", not worth mentioning.
Edit unbound_manager.mod file located in /jffs/addons/amtm directory
in the line 33 (for amtm 5.1, in other versions could be in different place) replace
/jffs/addons/unbound/unbound_manager.sh easy
with
/jffs/addons/unbound/unbound_manager.sh advanced

... which will be overwritten with the next amtm update. If I remember correctly @Martineau wanted it to start in easy mode.

I absolutely understand that. But it is not a big deal to change it back again.
Of course it would be nice to have setting in unbound.conf file specifying startup mode, but then again - not asking. I know how to do it and it is fine by me as it is

 

[TonyK132]

@TonyK132 I sure can, just thought is is quite "baby level", not worth mentioning.
Edit unbound_manager.mod file located in /jffs/addons/amtm directory
in the line 33 (for amtm 5.1, in other versions could be in different place) replace
/jffs/addons/unbound/unbound_manager.sh easy
with
/jffs/addons/unbound/unbound_manager.sh advanced

I absolutely understand that. But it is not a big deal to change it back again.
Of course it would be nice to have setting in unbound.conf file specifying startup mode, but then again - not asking. I know how to do it and it is fine by me as it is

Thanks for sharing. I would not have thought that setting would be in the amtm file.