Recent content by tomsk

Since doing a dirty flash from 386 beta1 to 386.1 i have a problem with addons contacting GitHub for update checks. using AMTM i get out put like this amtm 3.1.8 FW by thelonelycoder RT-AC68U (armv7l) FW-386.1 @ 10.10.10.1 The Asuswrt-Merlin Terminal Menu 1 open...

Don't forget that you you will want to create an access-control-view statement to specify the source IP or IP block that you want to redirect... fortunately unbound manager does this for you Example : if you have a machine at 192.168.1.100 that you want to redirect to 192.168.1.200 if it...

you need to put redirect after the view name and before the domain A:Option ==> views "name" redirect domain.com then you will be prompted to put the resource record (RR) of the IP you're redirecting to Enter RR for "name" redirect e.g. IN A 192.168.5.1 ==>: IN A 192.168.1.xxx

There is a cron job which runs the unbound_log,sh script at 57 minutes past the hour, and these are outputs to the syslog form that script.. its normal to see these kind of message, however you shouldn't be seeing 0 counts. Check to see if your Unbound is running ok and you are not diverting...

I noticed this morning after flashing 384.19 yesterday afternoon that my unbound stats were not updating.... on checking the cron jobs i noticed some were missing. I tried rebooting the router and rechecking the cron jobs but i found that as the time progressed some were removed and replaced by...

im tempted to suggest you check your USB stick for corruption (is it an old stick?) .... maybe you can enable the disk check in amtm and reboot the router to see if it throws up any errors.

looks like an issue with your certificates ( or at least the one for .adnx.com) .... you could try purging them and seeing if that helps ... ep in diversion menu , option 3 manage pixelserv certificates, option 1 purge...

The format of the rpz file downloaded has changed... thats what's using the causing the config check to fail when the firewall is enabled.... every entry is interpreted as having a resource record of CNAME .. maybe @juched can take a look at this? error...

You can just remove the old key

I guess the trade off is your privacy as the purpose of using unbound in the first place is to do your own lookups with the root servers to prevent companies like Quad9 profiling your habits. One would hope that infected clients connecting to malicious name servers would be prevented by the many...

Not a decision if you have older hardware you can't run cake on.......

If its just been happening over the last few days there is the possibility its due to vunerabilities in unbound which have been recently patched.... if your unbound isn't at version 1.10.1 then you should upgrade it via entware. If your Unbound is the latest and greatest , can you share any...

The paper is an interesting , if weighty read .... good insight into how recursive resolvers work besides describing the vulnerability....

Yeah its wireless.... strange it shouldn't be on auto... thats what all that acsd stuff was i guess....thanks will adjust that.

Hi Jack, I updated to 4.1.1 directly from 4.0.5 and i noticed a couple of things.... i got a couple of syslog error and also the SSH session dropped when the the guest clients were bounced.......