102.7 Alpha Builds available

[Ripshod]

Flippin' IPv6. That was my issue too I believe.
Turned it off and we're all good again.
Thanks @bennor and @dave14305

 

[bennor]

Previously, with DNS Director set to router the dns settings in the dhcp server (in my case YAZDHCP) were respected. Since installing this alpha that is no longer the case. I have never had to set individual devices up in dns director.

With the prior firmware change in DNS Director, typically now when setting Global to Router it will result in Pi-Hole only showing the router as the source IP request rather than the individual client when such a request is rerouted by DNS Director. At least that's what happens with my Pi-Holes when I previously set Global to Router after the DNS Director change in the firmware. Its why I now use Global to User Defined 1 with the Pi-Hole IP in the User Defined 1 field.

 

[Ripshod]

With the prior firmware change in DNS Director, typically now when setting Global to Router it will result in Pi-Hole only showing the router as the source IP request rather than the individual client when such a request is rerouted by DNS Director. At least that's what happens with my Pi-Holes when I previously set Global to Router after the DNS Director change in the firmware. Its why I now use User Defined 1 with the Pi-Hole IP in the User Defined 1 field.

I find that strange tbh. In pi-hole's client list I've always had the four clients listed, never the router.
If this goes any further I suggest a new thread(?).

 

[TurnstileBlues]

I use VPN Director quite heavily, but everything fine here. AX86U-Pro, dirty flash.
IPV6 has always been disabled for me, so I'm guessing that's why things have gone smoothly for me?

 

[dave14305]

Flippin' IPv6. That was my issue too I believe.
Turned it off and we're all good again.
Thanks @bennor and @dave14305

I don't understand how that would make a difference between the previous firmware and this Alpha. Devices using Pi-Hole locally shouldn't ever encounter DNS Director because those queries should never reach the firewall, unless you don't have a Pi-Hole IPv6 address given out for DNS over IPv6, which would then default to going to the router.

 

[Mutzli]

Everything is working well with this alpha update. Just some benign Broadcom VLAN cleanup error after rebooting that I haven't seen before.

• [ERROR vlan] vlanIoctl ,668: Failed to delete VLAN device wds2.0.1.52

 

[Ripshod]

I don't understand how that would make a difference between the previous firmware and this Alpha. Devices using Pi-Hole locally shouldn't ever encounter DNS Director because those queries should never reach the firewall, unless you don't have a Pi-Hole IPv6 address given out for DNS over IPv6, which would then default to going to the router.

I updated to this alpha early yesterday morning since then pi-hole had only registered 68 queries in 24hrs. Since I turned IPv6 off today pi-hole has registered 1344 queries ,and that's only going to increase.
From this I can only assume IPv6 is now bypassing everything.
Next thing to try is pi-holes local address in the IPv6 field in dns director.

*edit* That totally worked. IPv6 queries for the 4 devices are all now going to pi-hole.

TL;DR IPv6 now has to be used in DNS Director as well as the IPv4. Setting DNS in the DHCP Server is not working for me at all anymore.

 

[bennor]

*edit* That totally worked. IPv6 queries for the 4 devices are all now going to pi-hole.

TL;DR IPv6 now has to be used in DNS Director as well as the IPv4. Setting DNS in the DHCP Server is not working for me at all anymore.

The TL;DR is if you have IPv6 enabled on the router you may have to input the Pi's IPv6 address into DNS Director.

Since I don't have IPv6 enabled on the router I didn't have it in the DNS Director's IPv6 field on the release Asus-Merlin firmware. Haven't tried the Alpha yet.

PS: Those with Raspberry Pi's, one way to find their Pi's IPv6 address is by issuing the following command via SSH: ip -6 --brief a

 

[dave14305]

Setting DNS in the DHCP Server is not working for me at all anymore.

Why do you think that is? What are you entering?

nvram get ipv6_dns1_x
grep option6:23 /etc/dnsmasq.conf

 

[MDM]

All works fine with this Alpha.
Flashing went on first attempt with normal time...

 

[Howard_inGA]

Dirty one step upgrade was flawless...
Solid since completion.
Thanks, Merlin!!

 

[Ripshod]

Why do you think that is? What are you entering?

I used to set it this way in DHCP Server

It used to work fine, including the IPv6 (10.0.0.15 being pi-hole)
Now I have to do it this way

or I get zero traffic through the pi-hole

 

[dave14305]

I used to set it this way in DHCP Server
View attachment 70041
It used to work fine, including the IPv6 (10.0.0.15 being pi-hole)
Now I have to do it this way
View attachment 70040
or I get zero traffic through the pi-hole

Isn’t there a “IPv6 DNS Server” field on the YazDHCP page?

 

[Ripshod]

Isn’t there a “IPv6 DNS Server” field on the YazDHCP page?

There is but I'm not going to filter all traffic, I've only ever wanted it for the 4 devices with browsers, plus any visitors.

 

[heysoundude]

I used to set it this way in DHCP Server
View attachment 70041
It used to work fine, including the IPv6 (10.0.0.15 being pi-hole)
Now I have to do it this way
View attachment 70040
or I get zero traffic through the pi-hole

Right: pointing this traffic at/to the link-local v6 addy keeps it from leaving (looking outside) the LAN, which is rather the entire point, isn’t it? It’s an easy logic error to commit…so any how-to or help docs should state it clearly.

 

[Ripshod]

Right: pointing this traffic at/to the link-local v6 addy keeps it from leaving (looking outside) the LAN, which is rather the entire point, isn’t it? It’s an easy logic error to commit…so any how-to or help docs should state it clearly.

That's the way I understand it, but up until this release I could set dns in the DHCP server to the pi-hole (IPv4) and the IPv6 traffic followed. Now I have to specify the IPv6 for pi-hole. I'm not saying this is wrong. Maybe this new way is how it's supposed to work, but it's not the way it has been working for me for a long while now.
Anywho, it's sorted for me now so a non-issue.

 

[heysoundude]

It is the proper/correct way…
I’d be interested to see, for dual-stacked network, just how much is v6 traffic vs v4. I’d wager it would be surprising, perhaps even shocking, that v6 might be preferred when available.

 

[Ripshod]

@heysoundude I'm with Vodafone UK, who seem to prefer IPv6 over IPv4. pi-hole stats on the traffic for my mobile phone (most used for browsing) show 11945 IPv4 queries, and 33363 IPv6 queries. Huge difference.

 

[Tim Storey]

Dirty upgrade, everything on my small uncomplicated network is working fine.

 

[joec]

Just installed 3006.102.7_alpha on my be58_go. If you configure it in Public WiFi Mode (WISP) mode. The options "Enable local NTP server" and "Intercept NTP client requests" are missing. These options are available it you configure this route in Wireless router mode.