Menu
What's new
By:
Filters Better Search

Stubby-Installer-Asuswrt-Merlin

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

PoloNes said:
Guys, I'm a beginner.

I already installed stubby through amtm.
I would like to use cleanbrowsing adult.
How can I do it?

thank you.
Click to expand...
For the adult filter specifically:

Code: 
Adult Filter
Blocks access to all adult, pornographic and explicit sites. It does not block proxy or VPNs, nor mixed-content sites. Sites like Reddit are allowed. Google and Bing are set to the Safe Mode.

Domain:: adult-filter-dns.cleanbrowsing.org
IPv4 address: 185.228.168.10:853 and 185.228.169.11:853
IPv6 address: [2a0d:2a00:1::1]:853 and [2a0d:2a00:2::1]:853

Which translates to the following in stubby.yml:

Code: 
# # Cleanbrowsing-Security
  - address_data: 185.228.168.10
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

  - address_data: 185.228.168.11
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

   - address_data: 2a0d:2a00:1::1
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

  - address_data: 2a0d:2a00:2::1
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

Source: https://cleanbrowsing.org/guides/dnsovertls
 
Cleanbrowsing might not yet support TLS 1.3
Try changing the following line in stubby.yml to allow TLS 1.2
tls_min_version: GETDNS_TLS1_2
 
@bbunge @owine

The default installation works, with DNS 1.1.1.1.
With cleanbrowsing does not work.

After modifying the script and rebooting, the router gets WAN IP but does not browse.

Code: 
admin@RT-AC86U:/# /opt/etc/init.d/S61stubby check
 Checking stubby...              dead.

Is my stubby.yml correct?

Code: 
# stubby.yml configuration file created by Xentrk
# version 1.0.0
tls_ca_file: "/rom/etc/ssl/certs/ca-certificates.crt"
resolution_type: GETDNS_RESOLUTION_STUB
dns_transport_list:
  - GETDNS_TRANSPORT_TLS
tls_authentication: GETDNS_AUTHENTICATION_REQUIRED
tls_query_padding_blocksize: 128
edns_client_subnet_private : 1
round_robin_upstreams: 1
idle_timeout: 2000
tls_connection_retries: 5
tls_backoff_time: 900
timeout: 2000
appdata_dir: "/opt/var/cache/stubby"
listen_addresses:
  - 127.0.0.1@5453
  - 0::1@5453

upstream_recursive_servers:
# Quad 9 Secure Primary
#  - address_data: 9.9.9.9
#    tls_auth_name: "dns.quad9.net"
# Quad 9 Secure Primary
#  - address_data: 2620:fe::fe
#    tls_auth_name: "dns.quad9.net"
# Cloudflare Primary IPv4
# - address_data: 1.1.1.1
#   tls_auth_name: "cloudflare-dns.com"
# Cloudflare Secondary IPv4
# - address_data: 1.0.0.1
#   tls_auth_name: "cloudflare-dns.com"
# Cloudflare Primary IPv6
# - address_data: 2606:4700:4700::1111
#   tls_auth_name: "cloudflare-dns.com"
# Cloudflare Secondary IPv6
# - address_data: 2606:4700:4700::1001
#   tls_auth_name: "cloudflare-dns.com"

# Cleanbrowsing-Security
  - address_data: 185.228.168.10
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

  - address_data: 185.228.168.11
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

   - address_data: 2a0d:2a00:1::1
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

  - address_data: 2a0d:2a00:2::1
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

# Tweaks for statically linked binaries
tls_min_version: GETDNS_TLS1_3
tls_ciphersuites: "TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256"

DNS changes to router IP, is this correct?

OzaaOR6.png
 
EmeraldDeer said:
Cleanbrowsing might not yet support TLS 1.3
Try changing the following line in stubby.yml to allow TLS 1.2
tls_min_version: GETDNS_TLS1_2
Click to expand...

I'll modify it to see if it works.

EDITED

Did not work.
 
Last edited:
Here is a version of syubby.yml that I have used for Cleanbrowsing Adult. Am using this on a public access WIFI/Router running OpenWRT. Also works on Asus Stubby:
Code: 
# stubby.yml configuration file created by Xentrk
# version 1.0.0
tls_ca_file: "/rom/etc/ssl/certs/ca-certificates.crt"
resolution_type: GETDNS_RESOLUTION_STUB
dns_transport_list:
  - GETDNS_TRANSPORT_TLS
tls_authentication: GETDNS_AUTHENTICATION_REQUIRED
tls_query_padding_blocksize: 128
edns_client_subnet_private : 1
round_robin_upstreams: 1
idle_timeout: 2000
tls_connection_retries: 5
tls_backoff_time: 900
timeout: 2000
appdata_dir: "/opt/var/cache/stubby"
listen_addresses:
  - 127.0.0.1@5453
  - 0::1@5453

upstream_recursive_servers:
# Cleanbrowsing-Adult servers
  - address_data: 185.228.168.10
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

#  - address_data: 2a0d:2a00:1::1
#    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"
                
# Cleanbrowsing-Adult Alt servers
  - address_data: 185.228.168.11
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

#  - address_data: 2a0d:2a00:2::1::
#    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"
The IPV6 resolver addresses are commented out. If you use IPV6 remove the "#" like this:
Code: 
  - address_data: 2a0d:2a00:2::1::
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"
I strongly recommend you do not enable DNSSEC in Stubby or Merlin as I have had connection issues with CleanBrowsing.
You do not have to restart your router to get the changes to work. Run:
Code: 
/opt/etc/init.d/S61stubby restart
You may have to turn off the DNS WAN up check to get a reliable connection.
 
PoloNes said:
@bbunge @owine

The default installation works, with DNS 1.1.1.1.
With cleanbrowsing does not work.

After modifying the script and rebooting, the router gets WAN IP but does not browse.

Code: 
admin@RT-AC86U:/# /opt/etc/init.d/S61stubby check
 Checking stubby...              dead.

Is my stubby.yml correct?

Code: 
# stubby.yml configuration file created by Xentrk
# version 1.0.0
tls_ca_file: "/rom/etc/ssl/certs/ca-certificates.crt"
resolution_type: GETDNS_RESOLUTION_STUB
dns_transport_list:
  - GETDNS_TRANSPORT_TLS
tls_authentication: GETDNS_AUTHENTICATION_REQUIRED
tls_query_padding_blocksize: 128
edns_client_subnet_private : 1
round_robin_upstreams: 1
idle_timeout: 2000
tls_connection_retries: 5
tls_backoff_time: 900
timeout: 2000
appdata_dir: "/opt/var/cache/stubby"
listen_addresses:
  - 127.0.0.1@5453
  - 0::1@5453

upstream_recursive_servers:
# Quad 9 Secure Primary
#  - address_data: 9.9.9.9
#    tls_auth_name: "dns.quad9.net"
# Quad 9 Secure Primary
#  - address_data: 2620:fe::fe
#    tls_auth_name: "dns.quad9.net"
# Cloudflare Primary IPv4
# - address_data: 1.1.1.1
#   tls_auth_name: "cloudflare-dns.com"
# Cloudflare Secondary IPv4
# - address_data: 1.0.0.1
#   tls_auth_name: "cloudflare-dns.com"
# Cloudflare Primary IPv6
# - address_data: 2606:4700:4700::1111
#   tls_auth_name: "cloudflare-dns.com"
# Cloudflare Secondary IPv6
# - address_data: 2606:4700:4700::1001
#   tls_auth_name: "cloudflare-dns.com"

# Cleanbrowsing-Security
  - address_data: 185.228.168.10
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

  - address_data: 185.228.168.11
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

   - address_data: 2a0d:2a00:1::1
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

  - address_data: 2a0d:2a00:2::1
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

# Tweaks for statically linked binaries
tls_min_version: GETDNS_TLS1_3
tls_ciphersuites: "TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256"

DNS changes to router IP, is this correct?

OzaaOR6.png
Click to expand...
Based on Stubby not starting, I am assuming there is a syntax issue with your yml. It looks like the first IPv6 entry has an extra leading space on both lines at the very least.

Code: 
stubby -i -C /opt/etc/stubby/stubby.yml

Might provide hints.
 
Does this installation of stubby include a statically linked, more up to date (ie the 1.1 branch) version of OpenSSL, like pixelserv-tls? Or does it dynamically use the OpenSSL bundled with the merlin fw, which is 1.0 branch and thus does not support TLS 1.3.
 
JimbobJay said:
Does this installation of stubby include a statically linked, more up to date (ie the 1.1 branch) version of OpenSSL, like pixelserv-tls? Or does it dynamically use the OpenSSL bundled with the merlin fw, which is 1.0 branch and thus does not support TLS 1.3.
Click to expand...
That is a good point. I chose the statically linked stubby.
I am successfully using CleanBrowsing DNS over TLS via TLS 1.2.
 
CleanBrowsing requires alternate TLS port 853. Add the "tls_port: 853" attribute to the upstream_recursive_server section in the stubby.yml config file.

UPDATE: I may have spoken too soon -- this does not appear to resolve the failures.
 
Last edited:
visortgw said:
CleanBrowsing requires alternate TLS port 853. Add the "tls_port: 853" attribute to the upstream_recursive_server section in the stubby.yml config file.

UPDATE: I may have spoken too soon -- this does not appear to resolve the failures.
Click to expand...
Yup, Port 853 is standard DoT port.

If you are having problems connecting:
Check stubby.yml format with: stubby -i .yml files can be tricky. Make a copy of the original file before you edit it that way you will have a good reference or a place to go back. I use WinSCP to browse the router directories and edit files. With a right click on a file you can duplicate a file with a new file extension. I have several stubby.yml files saved so I can switch resolvers in a heartbeat to check if things are working. Example: for Quad9 I duplicate the file as stubby.yml.q9.

Disable dnssec in Merlin. Get stubby to work first...

Check the router time. Failure to get time can cause the router to not connect. This was corrected with an entry in dnsmasq.conf.add but sometimes may not work. If all else fails set the time server to an IP address vs. a URL (129.6.15.28 worked for me in US)

Disable router WAN connection check. In 384.9 Beta1 it is a setting called Network Monitoring in Administration/System. In prior versions it is in Tools/Other Settings (and as I remember it was called something else).
 
Still does not work.

There is an error in the beginning, but I do not understand it.

Code: 
/tmp/opt/etc/stubby$ stubby -i -C /opt/etc/stubby/stubby.yml
Reader error: invalid trailing UTF-8 octet: #E3 at 34
Could not parse config file # stubby.yml arquivo de configuração criado por Xentrk
# versão 1.0.0
tls_ca_file: "/rom/etc/ssl/certs/ca-certificates.crt"
resolution_type: GETDNS_RESOLUTION_STUB
dns_transport_list:
  - GETDNS_TRANSPORT_TLS
tls_authentication: GETDNS_AUTHENTICATION_REQUIRED
tls_query_padding_blocksize: 128
edns_client_subnet_private: 1
round_robin_upstreams: 1
idle_timeout: 2000
tls_connection_retries: 5
tls_backoff_time: 900
timeout: 2000
appdata_dir: "/ opt / var / cache / stubby"
listen_addresses:
  - 127.0.0.1@5453
  - 0::1@5453

upstream_recursive_servers:
# Servidores Cleanbrowsing-Adulto
  - endereço_dados: 185.228.168.10
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

# - endereço_dados: 2a0d: 2a00: 1 :: 1
# tls_auth_name: "adult-filter-dns.cleanbrowsing.org"
               
# Servidores Alt Cleanbrowsing-Adult
  - endereço_dados: 185.228.168.11
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

# - endereço_dados: 2a0d: 2a00: 2 :: 1 ::
# tls_auth_name: "adult-filter-dns.cleanbrowsing.org", "Generic error"
Could not parse config file "/opt/etc/stubby/stubby.yml": Generic error
 
PoloNes said:
Sorry, google translator.

Stubby is in English.
Click to expand...
Code: 
# stubby.yml configuration file created by Xentrk
# version 1.0.0
tls_ca_file: "/rom/etc/ssl/certs/ca-certificates.crt"
resolution_type: GETDNS_RESOLUTION_STUB
dns_transport_list:
  - GETDNS_TRANSPORT_TLS
tls_authentication: GETDNS_AUTHENTICATION_REQUIRED
tls_query_padding_blocksize: 128
edns_client_subnet_private : 1
round_robin_upstreams: 1
idle_timeout: 2000
tls_connection_retries: 5
tls_backoff_time: 900
timeout: 2000
appdata_dir: "/opt/var/cache/stubby"
listen_addresses:
  - 127.0.0.1@5453
  - 0::1@5453

upstream_recursive_servers:
# Cleanbrowsing Primary IPv4
  - address_data: 185.228.168.10
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"
# Cleanbrowsing Secondary IPv4
  - address_data: 185.228.169.11
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"
# Cleanbrowsing Primary IPv6
  - address_data: 2a0d:2a00:1::1
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"
# Cleanbrowsing Secondary IPv6
  - address_data: 2a0d:2a00:2::1
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

# Tweaks for statically linked binaries
tls_min_version: GETDNS_TLS1_2
tls_ciphersuites: "TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256"
 
EmeraldDeer said:
Code: 
# stubby.yml configuration file created by Xentrk
# version 1.0.0
tls_ca_file: "/rom/etc/ssl/certs/ca-certificates.crt"
resolution_type: GETDNS_RESOLUTION_STUB
dns_transport_list:
  - GETDNS_TRANSPORT_TLS
tls_authentication: GETDNS_AUTHENTICATION_REQUIRED
tls_query_padding_blocksize: 128
edns_client_subnet_private : 1
round_robin_upstreams: 1
idle_timeout: 2000
tls_connection_retries: 5
tls_backoff_time: 900
timeout: 2000
appdata_dir: "/opt/var/cache/stubby"
listen_addresses:
  - 127.0.0.1@5453
  - 0::1@5453

upstream_recursive_servers:
# Cleanbrowsing Primary IPv4
  - address_data: 185.228.168.10
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"
# Cleanbrowsing Secondary IPv4
  - address_data: 185.228.169.11
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"
# Cleanbrowsing Primary IPv6
  - address_data: 2a0d:2a00:1::1
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"
# Cleanbrowsing Secondary IPv6
  - address_data: 2a0d:2a00:2::1
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

# Tweaks for statically linked binaries
tls_min_version: GETDNS_TLS1_2
tls_ciphersuites: "TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256"
Click to expand...


@EmeraldDeer @bbunge @dave14305 @visortgw @Xentrk and others.

Many thanks to all for the help.
Apparently it's working now.

Code: 
[01:35:19.850516] STUBBY: Read config from file /opt/etc/stubby/stubby.yml
[01:35:19.851556] STUBBY: DNSSEC Validation is OFF
[01:35:19.851727] STUBBY: Transport list is:
[01:35:19.851865] STUBBY:   - TLS
[01:35:19.852009] STUBBY: Privacy Usage Profile is Strict (Authentication required)
[01:35:19.852123] STUBBY: (NOTE a Strict Profile only applies when TLS is the ONLY transport!!)
[01:35:19.852266] STUBBY: Starting DAEMON....
[01:35:33.382446] STUBBY: --- SETUP(TLS): : Verify locations loaded
[01:35:33.383219] STUBBY: 185.228.168.10                           : Conn opened: TLS - Strict Profile
[01:35:33.455078] STUBBY: 185.228.168.10                           : Verify passed : TLS
[01:35:35.760571] STUBBY: 185.228.168.10                           : Conn closed: TLS - Resps=     1, Timeouts  =     0, Curr_auth =Success, Keepalive(ms)=  2000
[01:35:35.760630] STUBBY: 185.228.168.10                           : Upstream   : TLS - Resps=     1, Timeouts  =     0, Best_auth =Success
[01:35:35.760639] STUBBY: 185.228.168.10                           : Upstream   : TLS - Conns=     1, Conn_fails=     0, Conn_shuts=      1, Backoffs     =     0
[01:35:45.764912] STUBBY: 185.228.169.11                           : Conn opened: TLS - Strict Profile
[01:35:46.379259] STUBBY: 185.228.169.11                           : Verify passed : TLS
[01:35:48.535606] STUBBY: 185.228.169.11                           : Conn closed: TLS - Resps=     1, Timeouts  =     0, Curr_auth =Success, Keepalive(ms)=  2000
[01:35:48.535666] STUBBY: 185.228.169.11                           : Upstream   : TLS - Resps=     1, Timeouts  =     0, Best_auth =Success
[01:35:48.535675] STUBBY: 185.228.169.11                           : Upstream   : TLS - Conns=     1, Conn_fails=     0, Conn_shuts=      1, Backoffs     =     0
[01:36:16.934685] STUBBY: 2a0d:2a00:1::1                           : Conn closed: TLS - Resps=     0, Timeouts  =     0, Curr_auth =   None, Keepalive(ms)=     0
[01:36:16.934746] STUBBY: 2a0d:2a00:1::1                           : Upstream   : TLS - Resps=     0, Timeouts  =     0, Best_auth =   None
[01:36:16.934755] STUBBY: 2a0d:2a00:1::1                           : Upstream   : TLS - Conns=     0, Conn_fails=     1, Conn_shuts=      0, Backoffs     =     0
[01:36:16.934781] STUBBY: 2a0d:2a00:2::1                           : Conn closed: TLS - Resps=     0, Timeouts  =     0, Curr_auth =   None, Keepalive(ms)=     0
[01:36:16.934791] STUBBY: 2a0d:2a00:2::1                           : Upstream   : TLS - Resps=     0, Timeouts  =     0, Best_auth =   None
[01:36:16.934799] STUBBY: 2a0d:2a00:2::1                           : Upstream   : TLS - Conns=     0, Conn_fails=     1, Conn_shuts=      0, Backoffs     =     0
[01:36:16.935019] STUBBY: 185.228.168.10                           : Conn opened: TLS - Strict Profile
[01:36:19.070751] STUBBY: 185.228.168.10                           : Conn closed: TLS - Resps=     1, Timeouts  =     0, Curr_auth =Success, Keepalive(ms)=  2000
[01:36:19.070816] STUBBY: 185.228.168.10                           : Upstream   : TLS - Resps=     2, Timeouts  =     0, Best_auth =Success
[01:36:19.070826] STUBBY: 185.228.168.10                           : Upstream   : TLS - Conns=     2, Conn_fails=     0, Conn_shuts=      2, Backoffs     =     0
[01:36:33.453898] STUBBY: 185.228.169.11                           : Conn opened: TLS - Strict Profile
[01:36:36.128927] STUBBY: 185.228.169.11                           : Conn closed: TLS - Resps=     1, Timeouts  =     0, Curr_auth =Success, Keepalive(ms)=  2000
[01:36:36.128991] STUBBY: 185.228.169.11                           : Upstream   : TLS - Resps=     2, Timeouts  =     0, Best_auth =Success
[01:36:36.128999] STUBBY: 185.228.169.11                           : Upstream   : TLS - Conns=     2, Conn_fails=     0, Conn_shuts=      2, Backoffs     =     0
[01:36:39.632171] STUBBY: 2a0d:2a00:1::1                           : Conn closed: TLS - Resps=     0, Timeouts  =     0, Curr_auth =   None, Keepalive(ms)=     0
[01:36:39.632228] STUBBY: 2a0d:2a00:1::1                           : Upstream   : TLS - Resps=     0, Timeouts  =     0, Best_auth =   None
[01:36:39.632237] STUBBY: 2a0d:2a00:1::1                           : Upstream   : TLS - Conns=     0, Conn_fails=     2, Conn_shuts=      0, Backoffs     =     0
[01:36:39.632262] STUBBY: 2a0d:2a00:2::1                           : Conn closed: TLS - Resps=     0, Timeouts  =     0, Curr_auth =   None, Keepalive(ms)=     0
[01:36:39.632272] STUBBY: 2a0d:2a00:2::1                           : Upstream   : TLS - Resps=     0, Timeouts  =     0, Best_auth =   None
[01:36:39.632280] STUBBY: 2a0d:2a00:2::1                           : Upstream   : TLS - Conns=     0, Conn_fails=     2, Conn_shuts=      0, Backoffs     =     0
[01:36:39.632446] STUBBY: 185.228.168.10                           : Conn opened: TLS - Strict Profile
[01:36:42.024019] STUBBY: 185.228.168.10                           : Conn closed: TLS - Resps=     1, Timeouts  =     0, Curr_auth =Success, Keepalive(ms)=  2000
[01:36:42.024087] STUBBY: 185.228.168.10                           : Upstream   : TLS - Resps=     3, Timeouts  =     0, Best_auth =Success
[01:36:42.024096] STUBBY: 185.228.168.10                           : Upstream   : TLS - Conns=     3, Conn_fails=     0, Conn_shuts=      3, Backoffs     =     0
 
EmeraldDeer said:
Code: 
# stubby.yml configuration file created by Xentrk
# version 1.0.0
tls_ca_file: "/rom/etc/ssl/certs/ca-certificates.crt"
resolution_type: GETDNS_RESOLUTION_STUB
dns_transport_list:
  - GETDNS_TRANSPORT_TLS
tls_authentication: GETDNS_AUTHENTICATION_REQUIRED
tls_query_padding_blocksize: 128
edns_client_subnet_private : 1
round_robin_upstreams: 1
idle_timeout: 2000
tls_connection_retries: 5
tls_backoff_time: 900
timeout: 2000
appdata_dir: "/opt/var/cache/stubby"
listen_addresses:
  - 127.0.0.1@5453
  - 0::1@5453

upstream_recursive_servers:
# Cleanbrowsing Primary IPv4
  - address_data: 185.228.168.10
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"
# Cleanbrowsing Secondary IPv4
  - address_data: 185.228.169.11
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"
# Cleanbrowsing Primary IPv6
  - address_data: 2a0d:2a00:1::1
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"
# Cleanbrowsing Secondary IPv6
  - address_data: 2a0d:2a00:2::1
    tls_auth_name: "adult-filter-dns.cleanbrowsing.org"

# Tweaks for statically linked binaries
tls_min_version: GETDNS_TLS1_2
tls_ciphersuites: "TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256"
Click to expand...
Get rid of the last three lines. You do not need tweaks...
 
Just for people to know, stubby and getdns is updated in Entware
getdns - 1.5.1-1
stubby - 0.2.5-1

Anyone can try help compile it with statically-linked OpenSSL 1.1.1a?
 
Can anyone shed some light on why Stubby is being called to start just moments before the router powers down in a reboot?
 
DonnyJohnny said:
Just for people to know, stubby and getdns is updated in Entware
getdns - 1.5.1-1
stubby - 0.2.5-1

Anyone can try help compile it with statically-linked OpenSSL 1.1.1a?
Click to expand...
Upgraded successfully to the new versions on my "older" router.

Code: 
opkg update

opkg upgrade

You will get an error message which you can ignore:
Collected errors:
* resolve_conffiles: Existing conffile /opt/etc/stubby/stubby.yml is different from the conffile in the new package. The new conffile will be placed at /opt/etc/stubby/stubby.yml-opkg.

I rebooted the router to make sure everything works. If you want just restart getdns and stubby.

bb
 
You must log in or register to reply here.

Similar threads

RMerlin
Release Asuswrt-Merlin 3006.102.1 is now available for Wifi 7 devices
4 5 6
Replies
106
Views
18K
jksmurf
J
RMerlin
ANNOUNCEMENT: Asuswrt-Merlin support underway for 3 Wifi 7 routers
5 6 7
Replies
130
Views
29K
scasapending
S
DMcD-EMS-USMC
  • Locked
3006.102 alpha 2 Build(s) Now Available
Replies
2
Views
1K
octopus
octopus
RMerlin
Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices
4 5 6
Replies
100
Views
15K
RMerlin
RMerlin
octopus
  • Locked
[ 3006.102 alpha Build(s) ] Testing available build(s)
2 3
Replies
59
Views
11K
octopus
octopus
Similar threads
Thread starter Title Forum Replies Date
M Asuswrt-Merlin with Nextcloud's share folder functionality Asuswrt-Merlin 1
visortgw Asuswrt Merlin 3006.102.3 Alpha1 for GT-BE98 Pro Asuswrt-Merlin 38
A ASUSwrt-Merlin connection to modem as Access Point and/or Bridge Asuswrt-Merlin 6
kaotic2499 Please add Asuswrt-merlin to GT-BE98 (Non-pro) version Asuswrt-Merlin 22
RMerlin Release Asuswrt-Merlin 3004.388.8_4 is now available Asuswrt-Merlin 160
RMerlin Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices Asuswrt-Merlin 100
B Unable to establish VPN connection to my PiVPN (ovpn) from my Asus RT-AC86U running Asuswrt-Merlin 386.14 Asuswrt-Merlin 1
F Several Questions Re:Asuswrt-Merlin Feature Implementation Asuswrt-Merlin 2
Yota How to enable port randomization in Asuswrt-Merlin? Asuswrt-Merlin 4
RMerlin Beta Asuswrt-Merlin 3006.102.2 Beta is now available for Wifi 7 devices Asuswrt-Merlin 70

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 573 (members: 24, guests: 549)
Top