What's new

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!

where did you add the delay exactly?
on the post-mount.div file


# set environment PATH to system binaries
export PATH=/sbin:/bin:/usr/sbin:/usr/bin:$PATH
sleep 20############# stubby delay test
OF="$(find $1/entware*/bin/opkg 2> /dev/null)"
if [ "$OF" ]; then
ln -nsf "$(echo "$OF" | sed 's~/bin/opkg~~g')" /tmp/opt
/opt/etc/init.d/rc.unslung start $0
logger -t Diversion "started Entware services, from $0"
service restart_dnsmasq
diversion ash_history
fi
#eof
 
on the post-mount.div file


# set environment PATH to system binaries
export PATH=/sbin:/bin:/usr/sbin:/usr/bin:$PATH
sleep 20############# stubby delay test
OF="$(find $1/entware*/bin/opkg 2> /dev/null)"
if [ "$OF" ]; then
ln -nsf "$(echo "$OF" | sed 's~/bin/opkg~~g')" /tmp/opt
/opt/etc/init.d/rc.unslung start $0
logger -t Diversion "started Entware services, from $0"
service restart_dnsmasq
diversion ash_history
fi
#eof

Thx did this and also I've set my ipv6 dns on the ipv6 page with my LAN IPv6 Address of my router! Did a reboot and it worked.
 
also got this same question here.
You should have your ipv6 ip of your router in the WAN DNS settings. Yoy should have nothing for DNS servers set in the LAN settings.
 
You should have your ipv6 ip of your router in the WAN DNS settings. Yoy should have nothing for DNS servers set in the LAN settings.

thats what i just did! Thx!!! And i maybe wrong but the only place that you can set the dns for ipv6, at least on the web interface, its on the wan page... There is nowhere to set the dns ipv6 for lan, the ipv6 of the router gets used automatically as the dns for the lan clients.
 
You should have your ipv6 ip of your router in the WAN DNS settings. Yoy should have nothing for DNS servers set in the LAN settings.
That's the ticket. Copied the IPv6 page "LAN IPv6 Address" down into "IPv6 DNS Server 1" and set the other two blank. I didn't put any delay into post-mount.div, but I get my system clock from my local network so it's set long before any of this happens in the boot sequence.

So, sounds like the Stubby install script needs to copy the router's IPv6 address down into the IPv6 DNS Server 1 entry and zero the others just like it does for the IPv4 settings.
 
thats what i just did! Thx!!! And i maybe wrong but the only place that you can set the dns for ipv6, at least on the web interface, its on the wan page... There is nowhere to set the dns ipv6 for lan, the ipv6 of the router gets used automatically as the dns for the lan clients.
Gotcha! I don't know too much about IPv6.:)
 
thats what i just did! Thx!!! And i maybe wrong but the only place that you can set the dns for ipv6, at least on the web interface, its on the wan page... There is nowhere to set the dns ipv6 for lan, the ipv6 of the router gets used automatically as the dns for the lan clients.
No, the IPv6 page has settings for IPv6 DNS servers. Pretty sure this is what gets passed down to the clients. Pretty sure you shouldn't put IPv6 addresses on the WAN page. @RMerlin?
 
No, the IPv6 page has settings for IPv6 DNS servers.

Thats for wan and not for lan. After all, this page is the wan page for ipv6.

Pretty sure this is what gets passed down to the clients. Pretty sure you shouldn't put IPv6 addresses on the WAN page. @RMerlin?

No its does not, in other words, it does not get passed down to the clients! I've tested it... What the clients get is the router ipv6 ip.
 
Thats for wan and not for lan. After all, this page is the wan page for ipv6.
Right, just like the WAN page on the router is for the WAN. But notice it's set to your router's local IP address. The only place the external DNS is set is in the stubby.yml file.
No its does not, in other words, it does not get passed down to the clients! I've tested it... What the clients get is the router ipv6 ip.
What does your resolv.conf say? Mine has nameserver and 1 server line pointing to the IPv4 local address of the router, and a second server line pointing to the local IPv6 address of the router. Do you have all three DNS server lines in the IPv6 page set blank? That may be effectively the same as setting the DNS Server 1 line to the local IPv6 address of the router.

And I suppose in the end it doesn't matter as long as Stubby works and your IPv6 works. :)
 
Right, just like the WAN page on the router is for the WAN. But notice it's set to your router's local IP address. The only place the external DNS is set is in the stubby.yml file.

What does your resolv.conf say? Mine has nameserver and 1 server line pointing to the IPv4 local address of the router, and a second server line pointing to the local IPv6 address of the router. Do you have all three DNS server lines in the IPv6 page set blank? That may be effectively the same as setting the DNS Server 1 line to the local IPv6 address of the router.

And I suppose in the end it doesn't matter as long as Stubby works and your IPv6 works. :)

Here:
 
Last edited:
That's the ticket. Copied the IPv6 page "LAN IPv6 Address" down into "IPv6 DNS Server 1" and set the other two blank. I didn't put any delay into post-mount.div, but I get my system clock from my local network so it's set long before any of this happens in the boot sequence.

So, sounds like the Stubby install script needs to copy the router's IPv6 address down into the IPv6 DNS Server 1 entry and zero the others just like it does for the IPv4 settings.

In my case i do not have ipv6 enabled and i also get my time served by my local synology nas ntp server.
 
Ahh, my bad, forgot the instructions were pointing at /tmp/resolv.*, not resolv.conf. My bad, my resolv.conf also only has 127.0.0.1. I should have asked for (please do not post*) does the output of "cat /tmp/resolv.dnsmasq" show 1 server line pointing to the IPv4 local address of the router, and a second server line pointing to the local IPv6 address of the router.)

Also, yes, my IPv6 page looks just like yours. On the WAN page under "WAN DNS Setting" I only have the local IPv4 address of the router, no IPv6.

* = IMHO, you shouldn't post local IP addresses. Although security through obscurity is not a great idea, having your local IP range in hand may help attackers. Maybe.
 
In my case i do not have ipv6 enabled and i also get my time served by my local synology nas ntp server.
Weird. I don't need a delay anywhere. Are you letting the firmware get the time from your nas or do you have something like my script getting it as early as possible? It was suggested to me that letting the firmware get it may still not occur soon enough.

I presume if you're using the firmware you have the IP address of your nas there and not the hostname? Having the hostname would require DNS being up of course.
 
Ahh, my bad, forgot the instructions were pointing at /tmp/resolv.*, not resolv.conf. My bad, my resolv.conf also only has 127.0.0.1. I should have asked for (please do not post*) does the output of "cat /tmp/resolv.dnsmasq" show 1 server line pointing to the IPv4 local address of the router, and a second server line pointing to the local IPv6 address of the router.)

Yes, i have both lines pointing just like you described!
 
Last edited:
Yes, i have both lines!
Maybe we just have a language barrier? On your WAN page do you have both the local IPv4 and IPv6 addresses under "WAN DNS Setting"? Maybe I misread
And i maybe wrong but the only place that you can set the dns for ipv6, at least on the web interface, its on the wan page... There is nowhere to set the dns ipv6 for lan, the ipv6 of the router gets used automatically as the dns for the lan clients."
Did you mean the GUI WAN page or the IPv6 page? I think IPv6 WAN and LAN are both on the one IPv6 page.
 
Maybe we just have a language barrier? On your WAN page do you have both the local IPv4 and IPv6 addresses under "WAN DNS Setting"?

Yes, on both wans! In the ipv4 one and in the ipv6 one as well... the ipv4 one was set by stubby itself and the ipv6 I've set it myself sometime ago. Both using the local ip of my router as the only dns server.

Did you mean the GUI WAN page or the IPv6 page? I think IPv6 WAN and LAN are both on that one page.

Yes, i mean the GUI WAN IPV6 page! In other words, on the following path: Router IP -> IPV6! I am pretty sure, that page is only for the wan IPV6 dns and it does not get passed down to the clients, because i already tested it, by setting another dns there, then i did a renew on my desktop(ipconfig /release + ipconfig /renew) and it got the same dns as before the change, in other worlds the router ipv6 ip.

EDIT:

I did an edit on my previously answer to you to clarify it a little better, read it again...
 
Yes, on both wans! In the ipv4 one and in the ipv6 one as well... the ipv4 one was set by stubby itself and the ipv6 I've set it myself sometime ago. Both using the local ip of my router as the only dns server.



Yes, i mean the GUI WAN IPV6 page! In other words, on the following path: Router IP -> IPV6! I am pretty sure, that page is only for the wan IPV6 dns and it does not get passed down to the clients, because i already tested it, by setting another dns there, then i did a renew on my desktop(ipconfig /release + ipconfig /renew) and it got the same dns as before the change, in other worlds the router ipv6 ip.

EDIT:

I did an edit on my previously answer to you to clarify it a little better, read it again...
Okay, we both did the same thing. :) Just misunderstood one another. I think the important thing is to have the local IPv6 address of the router on the IPv6 page, and not an external IPv6 DNS for Stubby to work. Which we both did, so all is well.

Thanks for bearing with me, I was wondering if settings in two different places were doing the same thing.

So interesting, there is no way to pass an external IPv6 DNS provider to clients? It will always pass the router's IPv6 address for DNS regardless? Interesting.
 
So interesting, there is no way to pass an external IPv6 DNS provider to clients? It will always pass the router's IPv6 address for DNS regardless? Interesting.

Using the web interface, i don't know anywhere in it where you can do that, in other words pass the IPV6 dns to the clients that you set on the IPV6 wan page! Now using ssh and other methods, then its different history... not that i know the commands to do that or if it is really possible or not, but i guess, it should be?
 
Last edited:
Weird. I don't need a delay anywhere. Are you letting the firmware get the time from your nas or do you have something like my script getting it as early as possible? It was suggested to me that letting the firmware get it may still not occur soon enough.

I presume if you're using the firmware you have the IP address of your nas there and not the hostname? Having the hostname would require DNS being up of course.
Yes using the ip , i tried you script yesterday but it did not work, could not find the server , all my devices sync to it with no problems, so i don't know what the problem was.
 

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!
Top