YazFi AdGuard Home on Raspberry Pi and YazFi

[Gary_Dexter]

sounds to me like maybe you are trying to give a guest network an ip range that your VPN provider is also issuing? (strange guess). Or another possibility would be adguardhome doesn't have that network range 10.0.0.0/8properly configured as a private network it services, but it does have 192.168.0.0/16 configured to be a private network range it services.

No VPN setup.

I’m using 10.12.12.0/24 for my main network and that works fine with no issues. It was just the YazFi network that was being strange (10.12.13.0/24).

Interestingly as well after the change, devices have maintained the final octet in their IP addresses - for example 10.12.13.7 has become 192.168.12.7, 10.12.13.10 has become 192.168.12.10 etc.

I guess this is by design in YazFi?

 

[SomeWhereOverTheRainBow]

No VPN setup.

I’m using 10.12.12.0/24 for my main network and that works fine with no issues. It was just the YazFi network that was being strange (10.12.13.0/24).

Interestingly as well after the change, devices have maintained the final octet in their IP addresses - for example 10.12.13.7 has become 192.168.12.7, 10.12.13.10 has become 192.168.12.10 etc.

I guess this is by design in YazFi?

Typically clients control the final octet unless you statically control it.

 

[Gary_Dexter]

Great thanks!

Well it’s working now - I’m happy to leave the IP’s as they are as I don’t use them for remote access or anything.

One of life’s mysteries I guess - thanks to all that chipped in!

 

[JimbobJay]

Weird. Might be worth making the AdGuardTeam aware of this on their github page because it sounds like it could be a potential bug on their end.

 

[bennor]

I’m using 10.12.12.0/24 for my main network and that works fine with no issues. It was just the YazFi network that was being strange (10.12.13.0/24).

There is coding (below) in the YazFi script that appears to include the 10.x.x.x IP range. Someone would have to do more controlled testing with Asus-Merlin, YazFi and Adguard Home to figure out exactly where the conflict is.

IP_Local(){
    if echo "$1" | grep -qE '(^10\.)|(^172\.1[6-9]\.)|(^172\.2[0-9]\.)|(^172\.3[0-1]\.)|(^192\.168\.)'; then
        return 0
    elif [ "$1" = "127.0.0.1" ]; then
        return 0
    else
        return 1
    fi
}

Edit to add: There is also the following discussion, link below, over on AdGuardHome's GitHub that may be relevant. If I understand that discussion right one person was having issues using 10.0.0.0/8. One or more fixes/workarounds are mentioned. One of the possible fixes (see this link) involves using the private_networks field of the AdGuardHome.yaml file.

Private IP's PTR no answer [RFC1918 Private Address Space] · Issue #4497 · AdguardTeam/AdGuardHome

Prerequisites [ yes] I am running the latest version [ yes] I checked the documentation and found no answer [ yes] I checked to make sure that this issue has not already been filed Issue Details Ve...

github.com