Gl-inet router GL-MT3000 Beryl Update AGH to v0.107.59 from v0.107.57- error new wersion don't working

[UserArdek]

Prerequisites

• [x] I have checked the Wiki and Discussions and found no answer

• [x] I have searched other issues and found no duplicates

• [x] I want to report a bug and not ask a question or ask for help

• [x] I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Linux, ARMv7

Installation

Custom package (OpenWrt, HomeAssistant, etc; please mention in the description)

Setup

On a router, DHCP is handled by AdGuard Home

AdGuard Home version

v0.107.57

Action

I got the errors there are no MPTCP support, the adguard home is not working after update to v0.107.59 from v0.107.57. MPTCP: mptcp need to implement this function: net/mptcp/subflow.c,subflow_v4_init_req,1791 wget -O update-adguardhome.sh https://raw.githubusercontent.com/Admonstrator/glinet-adguard-updater/main/update-adguardhome.sh && sh update-adguardhome.sh

Expected result

Normal working

Actual result

After reboot: kern.err kernel: [ 108.485507] MPTCP: mptcp need to implement this function: net/mptcp/subflow.c,subflow_v4_init_req,1791

Additional information and/or screenshots

After revert to version v0.107.57 by the script: wget -O update-adguardhome.sh https://raw.githubusercontent.com/Admonstrator/glinet-adguard-updater/main/update-adguardhome.sh && sh update-adguardhome.sh --select-release is working fine.

[spamies1]

same issue here on GL MT3000 firmware 4.7.4, is this an adguard or gli.net problem?

[UserArdek]

I check this error on GL MT3000 (Beryl AX) and GL MT6000 (Flint 2) and on Flint 2 AGH 0.107.59 is working fine, on Beryl AX the issue exist, so I use version 0.107.57 on it.

[EarendilSI]

Same error with GL-iNet SLATE 7 and version ' 0.157.60 (also 0.157.59) after update from 0.157.52, version 0.157.58 works correctly

[UserArdek]

I just checked new version 0.157.60 of Adguard home on GL inet GL MT3000 (Beryl AX) - same error, on GL MT6000 (Flint 2) working flawlessly

[Admonstrator]

It could be an issue with the "small" packages as well, since my script does not use the original AGH binaries. Did someone try to use the official AGH releases?

[UserArdek]

How to install official AGH on GL-MT3000 ?

[UserArdek]

Official firmware from Gli-inet does not contain upgraded AGH .

[networkoctopus]

Ive had this kernel error with another application written in go. There seems to be issues with MPTCP and Go. I solved globally by disabling MPTCP on my Brume 2.

echo "net.mptcp.enabled=0" > /etc/sysctl.conf
sysctl -p

You can disable MPTCP on a per application basis by adding environment variable GODEBUG=multipathtcp=0 . I know how to do this for docker apps, but not sure about Adguardhome on openwrt.

Maybe add below to the AGH init.d service file? Not sure if it can be added to the yaml file.

[Service]
Environment="GODEBUG=multipathtcp=0"`

[spamies1]

Maybe add below to the AGH init.d service file? Not sure if it can be added to the yaml file.

[Service]
Environment="GODEBUG=multipathtcp=0"`

Wow Thanks for your help. With some added input from chatgpt I was able to get adguard working.

add the following line to the bottom of /etc/init.d/adguardhome

procd_set_param env GODEBUG=multipathtcp=0

procd_open_instance
procd_set_param respawn
procd_set_param group explict_vpn
procd_set_param stderr 1
procd_set_param env GODEBUG=multipathtcp=0
procd_set_param command /usr/bin/AdGuardHome --glinet -c /etc/AdGuardHome/config.yaml -w /etc/AdGuardHome -l syslog
procd_close_instance
[ -e /etc/edgerouter.fw ] && /etc/edgerouter.fw loaddns

edit:

Still working after 24 hours, seems the issue is resolved. Is this a Go or adguard issue? After updating the router firmware I had to update adguard and the issue returned until applying the above fix.

[Admonstrator]

edit:

Still working after 24 hours, seems the issue is resolved. Is this a Go or adguard issue? After updating the router firmware I had to update adguard and the issue returned until applying the above fix.

Thanks for letting me know, I updated my glinet-adguard-updater script!