@rgnldo
You are again guessing which
unbound parameters might be
'correct', but sneakily using the community as unwittingly exposed guinea pigs
without the users' permission - suppose your tweaks are not valid on the target router?
e.g.
View attachment 21153
i.e. depending on when someone installs
unbound, they may actually have any of the following:
Code:
edns-buffer-size: 1472
edns-buffer-size: 1232
incoming-num-tcp: 1000
incoming-num-tcp: 600
outgoing-num-tcp: 100
Most do not understand the consequences nor indeed what the actual parameters mean, so you need to have a sense of responsibility and open disclosure.
You are abusing the trust of users that wish to use
my script to install
unbound
THIS IS UNACCEPTABLE.
Add the rqeuested version header in '
unbound.conf' hosted on your GitHub together with a description of the change, so the script can advise if it may be necessary to review the changes you are
testing.
...or do you still think your attitude is acceptable?