Can't get MT2500 (Brune 2) VPN server working (ddns: PID '20882' exit WITH ERROR '1')

tyeezy · July 31, 2024, 6:55pm

Hi All,

Im having issues getting my MT2500 working as a Wireguard VPN.

My set up is

MT2500 >> Virgin Router << Internet

WAN Port connected to Virgin Router ethernet,
LAN port connected to my macbook to set up the GL iNet settings.

Ive enabled DDNS on applications
Ive set up wireguard to allow remote network access and configuration file to include DDNS

When I try connecting to the VPN using wireguard config , it connects fine but theres no internet and i can't access the GL Inet interface.

Ive checked the log on MT2500 and its saying

ddns: PID '20882' exit WITH ERROR '1'

When I ping the given DDNS host i get ( uy****.glddns.com: Unknown host)

So im feeling like it could be DDNS server issue?

Any ideas?

Note i followed the above for my office network and it worked straight away, but trying to do the same but with a new device through my virgin router is giving me the above issue.

Could it be the MT2500 ive got it faulty or could it be Virgin router giving issues?

Thanks in advance.
Tom

admon · July 31, 2024, 6:57pm

Is your DDNS check successful?

tyeezy · July 31, 2024, 7:43pm

No it wasn't...not sure where I go from there as it seems I can't amend the host name or try a different DDNS provider?

tyeezy · July 31, 2024, 7:58pm

Heres the log

Wed Jul 31 18:15:20 2024 kern.info kernel: [  283.364981] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Wed Jul 31 18:15:20 2024 kern.info kernel: [  283.373447] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Wed Jul 31 18:15:20 2024 daemon.notice netifd: Network device 'eth0' link is up
Wed Jul 31 18:15:20 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Wed Jul 31 18:15:20 2024 daemon.notice netifd: Interface 'wan' is setting up now
Wed Jul 31 18:15:20 2024 daemon.notice netifd: wan (7926): udhcpc: started, v1.33.2
Wed Jul 31 18:15:20 2024 daemon.notice netifd: wan (7926): udhcpc: sending discover
Wed Jul 31 18:15:21 2024 daemon.notice netifd: wan (7926): udhcpc: sending select for 192.168.0.35
Wed Jul 31 18:15:21 2024 daemon.notice netifd: wan (7926): udhcpc: lease of 192.168.0.35 obtained, lease time 86400
Wed Jul 31 18:15:21 2024 daemon.info avahi-daemon[3567]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.35.
Wed Jul 31 18:15:21 2024 daemon.info avahi-daemon[3567]: New relevant interface eth0.IPv4 for mDNS.
Wed Jul 31 18:15:21 2024 daemon.info avahi-daemon[3567]: Registering new address record for 192.168.0.35 on eth0.IPv4.
Wed Jul 31 18:15:21 2024 daemon.notice netifd: Interface 'wan' is now up
Wed Jul 31 18:15:21 2024 daemon.info dnsmasq[4074]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Jul 31 18:15:21 2024 daemon.info dnsmasq[4074]: using only locally-known addresses for domain test
Wed Jul 31 18:15:21 2024 daemon.info dnsmasq[4074]: using only locally-known addresses for domain onion
Wed Jul 31 18:15:21 2024 daemon.info dnsmasq[4074]: using only locally-known addresses for domain localhost
Wed Jul 31 18:15:21 2024 daemon.info dnsmasq[4074]: using only locally-known addresses for domain local
Wed Jul 31 18:15:21 2024 daemon.info dnsmasq[4074]: using only locally-known addresses for domain invalid
Wed Jul 31 18:15:21 2024 daemon.info dnsmasq[4074]: using only locally-known addresses for domain bind
Wed Jul 31 18:15:21 2024 daemon.info dnsmasq[4074]: using only locally-known addresses for domain lan
Wed Jul 31 18:15:21 2024 daemon.info dnsmasq[4074]: using nameserver 194.168.4.100#53
Wed Jul 31 18:15:21 2024 daemon.info dnsmasq[4074]: using nameserver 194.168.8.100#53
Wed Jul 31 18:15:21 2024 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Wed Jul 31 18:15:21 2024 authpriv.notice sudo:     root : PWD=/ ; USER=root ; GROUP=nonevpn ; COMMAND=/usr/lib/gl_ddns/dynamic_dns_updater.sh -- stop
Wed Jul 31 18:15:21 2024 user.notice ddns-scripts[8062]: myddns_ipv4: PID '8062' started at 2024-07-31 18:15
Wed Jul 31 18:15:22 2024 user.warn ddns-scripts[8062]: myddns_ipv4: Service section disabled! - TERMINATE
Wed Jul 31 18:15:22 2024 user.warn ddns-scripts[8062]: myddns_ipv4: PID '8062' exit WITH ERROR '1' at 2024-07-31 18:15
Wed Jul 31 18:15:22 2024 daemon.info avahi-daemon[3567]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::9683:c4ff:fe48:3c20.
Wed Jul 31 18:15:22 2024 daemon.info avahi-daemon[3567]: New relevant interface eth0.IPv6 for mDNS.
Wed Jul 31 18:15:22 2024 daemon.info avahi-daemon[3567]: Registering new address record for fe80::9683:c4ff:fe48:3c20 on eth0.*.
Wed Jul 31 18:15:22 2024 user.notice ddns-scripts[5875]: glddns: PID '5875' terminated by 'SIGTERM' at 2024-07-31 18:15
Wed Jul 31 18:15:23 2024 authpriv.notice sudo:     root : PWD=/ ; USER=root ; GROUP=nonevpn ; COMMAND=/usr/lib/gl_ddns/dynamic_dns_updater.sh -- start
Wed Jul 31 18:15:24 2024 user.notice ddns-scripts[8385]: ddns: PID '8385' started at 2024-07-31 18:15
Wed Jul 31 18:15:24 2024 user.notice kmwan: config json str={ "op": 2, "data": { "cells": [ { "interface": "wan", "netdev": "eth0", "track_mode": "force", "addr_type": 4, "tracks": [ { "type": "ping", "ip": "1.1.1.1" }, { "type": "ping", "ip": "8.8.8.8" }, { "type": "ping", "ip": "208.67.222.222" }, { "type": "ping", "ip": "208.67.220.220" } ] } ] } }
Wed Jul 31 18:15:24 2024 kern.debug kernel: [  286.762360] [add_dev_config 287]add node success. iface:wan, dev:eth0, ifindex:2
Wed Jul 31 18:15:24 2024 user.warn ddns-scripts[8385]: ddns: Service section disabled! - TERMINATE
Wed Jul 31 18:15:24 2024 user.warn ddns-scripts[8385]: ddns: PID '8385' exit WITH ERROR '1' at 2024-07-31 18:15
Wed Jul 31 18:15:24 2024 user.notice ddns-scripts[8388]: glddns: PID '8388' started at 2024-07-31 18:15
Wed Jul 31 18:15:24 2024 user.warn ddns-scripts[8388]: glddns: NO valid IP found

admon · July 31, 2024, 8:02pm

Could it be that you only have an IPv6 contract?

tyeezy · July 31, 2024, 8:03pm

This is the message, however the reported IP is the correct outside facing IP

tyeezy · July 31, 2024, 8:04pm

Dont think so ( see screeenshot of modem)

admon · July 31, 2024, 8:07pm

The modem screenshot does not tell anything.

What ISP?

tyeezy · July 31, 2024, 8:12pm

Does it not show that it is IPv4?

Virgin Media (UK)

tyeezy · July 31, 2024, 8:21pm

If i ethernet direct from laptop into Virgin router this is what ifconfig showing. Does this help? (inet6 & inet)

bruce · August 1, 2024, 3:43am

Hi,

May I know does the Virgin router get the public IPv4 from ISP?

tyeezy · August 1, 2024, 7:04am

Yes it does, The router is also the modem.

bruce · August 1, 2024, 8:49am

Hi,

Have you downgrade or upgrade the firmware for the Brune2?
Please execute the command in the Brune2 SSH and post the return here, please blur the personal info:

cat /etc/config/gl_ddns

ifconfig

tyeezy · August 1, 2024, 12:36pm

config service 'ddns'
	option enabled_ssh '0'
	option http_port '80'
	option https_port '443'

config service 'glddns'
	option interface 'wan'
	option check_interval '10'
	option check_unit 'minutes'
	option force_interval '60'
	option force_unit 'minutes'
	option ip_url 'http://checkip.dyndns.com'
	option ip_source 'web'
	option password '32*****018ad7194'
	option username '9******83c20'
	option domain 'uy8****.glddns.com'
	option param_enc 'uy8****'
	option lookup_host 'uy8****.glddns.com'
	option service_name 'glddns.com'
	option force_ipversion '1'
	option enabled '1'

config service 'glddnsv6'
	option use_ipv6 '1'
	option interface 'wan6'
	option check_interval '10'
	option check_unit 'minutes'
	option force_interval '60'
	option force_unit 'minutes'
	option ip_url 'http://checkipv6.dyndns.com'
	option ip_source 'web'
	option password '32*****018ad7194'
	option username '9*****83c20'
	option domain 'uy8***.glddns.com'
	option param_enc 'uy8****'
	option lookup_host 'uy8****.glddns.com'
	option service_name 'glddns.com'
	option force_ipversion '1'
	option enabled '1'

ifconfig

br-lan    Link encap:Ethernet  HWaddr 94:83:C4:48:3C:21  
          inet addr:192.168.8.1  Bcast:192.168.8.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12385 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11588 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2622350 (2.5 MiB)  TX bytes:5959528 (5.6 MiB)

eth0      Link encap:Ethernet  HWaddr 94:83:C4:48:3C:20  
          inet addr:192.168.1.188  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::9683:c4ff:fe48:3c20/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:103676 errors:0 dropped:0 overruns:0 frame:3
          TX packets:21243 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:143460201 (136.8 MiB)  TX bytes:3141525 (2.9 MiB)
          Interrupt:75 

eth1      Link encap:Ethernet  HWaddr 94:83:C4:48:3C:21  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:26361 errors:0 dropped:0 overruns:0 frame:0
          TX packets:105934 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4043695 (3.8 MiB)  TX bytes:145037698 (138.3 MiB)
          Interrupt:75 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:187 errors:0 dropped:0 overruns:0 frame:0
          TX packets:187 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:18221 (17.7 KiB)  TX bytes:18221 (17.7 KiB)