Wireguard client was working. Just goes "connect" -> "abort". Missing wg0 interface

pseudosavant · 2022-02-25T01:33:27.462Z

Hi, I recently got a GL-MT1300. I’m using it as a ‘VPN router’ at my house to my parent’s home. Basic setup. Change the wifi network names. Enable goodcloud. Setup the wireguard client. It worked great for about 2 weeks, and then it just stopped. The exact config, copy and pasted, works perfect on my Windows 10 Wireguard client and my iOS Wireguard client.

The “connect” button just eventually ends up saying “abort” and the dot to the left is orange. I’ve been using OpenWRT for years and when I ssh’d in I noticed that there wasn’t a wg0 interface. I tried reverting to stock and reconfiguring (SSID names, add 1 WG client profile, enable goodcloud, that’s all) but it still doesn’t work and there still isn’t a wg0. I never supply a “listen port” but it seems the router auto generates one?

Any ideas how to get my Wireguard client working again? Seems like a lot of users have posted about this same exact problem without ever finding a resolution.

UPDATE: I noticed that the wg0 interface is created when I click “connect”. It still doesn’t work though. I added more diagnostic info.

I pasted some diagnostic info below:

ifconfig before connect:

root@GL-MT1300:~# ifconfig
br-guest  Link encap:Ethernet  HWaddr 4E:4F:64:2C:D7:AA
          inet addr:192.168.9.1  Bcast:192.168.9.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

br-lan    Link encap:Ethernet  HWaddr 94:83:C4:15:09:45
          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:17336 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17737 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3330314 (3.1 MiB)  TX bytes:15692067 (14.9 MiB)

eth0      Link encap:Ethernet  HWaddr 94:83:C4:15:09:44
          inet6 addr: fe80::9683:c4ff:fe15:944/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:22459 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11552 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:9589399 (9.1 MiB)  TX bytes:2815334 (2.6 MiB)
          Interrupt:23

eth0.1    Link encap:Ethernet  HWaddr 94:83:C4:15:09:45
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1799 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2379 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:159266 (155.5 KiB)  TX bytes:274752 (268.3 KiB)

eth0.2    Link encap:Ethernet  HWaddr 94:83:C4:15:09:44
          inet addr:192.168.1.198  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:18969 errors:0 dropped:91 overruns:0 frame:0
          TX packets:8801 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8673715 (8.2 MiB)  TX bytes:2253450 (2.1 MiB)

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:82 errors:0 dropped:0 overruns:0 frame:0
          TX packets:82 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8369 (8.1 KiB)  TX bytes:8369 (8.1 KiB)

ra0       Link encap:Ethernet  HWaddr 94:83:C4:15:09:47
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:25

rax0      Link encap:Ethernet  HWaddr 94:83:C4:15:09:46
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:18411 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20216 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4012582 (3.8 MiB)  TX bytes:15876234 (15.1 MiB)

ifconfig after connect

root@GL-MT1300:/etc/config# ifconfig
br-guest  Link encap:Ethernet  HWaddr 4E:4F:64:2C:D7:AA
          inet addr:192.168.9.1  Bcast:192.168.9.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

br-lan    Link encap:Ethernet  HWaddr 94:83:C4:15:09:45
          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:59909 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60837 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13383906 (12.7 MiB)  TX bytes:80430455 (76.7 MiB)

eth0      Link encap:Ethernet  HWaddr 94:83:C4:15:09:44
          inet6 addr: fe80::9683:c4ff:fe15:944/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:112341 errors:0 dropped:0 overruns:0 frame:0
          TX packets:73297 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:96193115 (91.7 MiB)  TX bytes:51434058 (49.0 MiB)
          Interrupt:23

eth0.1    Link encap:Ethernet  HWaddr 94:83:C4:15:09:45
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7732 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8948 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:621546 (606.9 KiB)  TX bytes:17873045 (17.0 MiB)

eth0.2    Link encap:Ethernet  HWaddr 94:83:C4:15:09:44
          inet addr:192.168.1.198  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:63164 errors:0 dropped:198 overruns:0 frame:0
          TX packets:37019 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:70909104 (67.6 MiB)  TX bytes:10575629 (10.0 MiB)

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:140 errors:0 dropped:0 overruns:0 frame:0
          TX packets:140 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:14880 (14.5 KiB)  TX bytes:14880 (14.5 KiB)

ra0       Link encap:Ethernet  HWaddr 94:83:C4:15:09:47
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7499 errors:1688 dropped:0 overruns:0 frame:0
          TX packets:3387 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1558904 (1.4 MiB)  TX bytes:1945859 (1.8 MiB)
          Interrupt:25

rax0      Link encap:Ethernet  HWaddr 94:83:C4:15:09:46
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:53889 errors:0 dropped:0 overruns:0 frame:0
          TX packets:69384 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13502569 (12.8 MiB)  TX bytes:62211030 (59.3 MiB)

wg0       Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:192.168.99.2  P-t-P:192.168.99.2  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP  MTU:1420  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29 errors:0 dropped:3246 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:4292 (4.1 KiB)

wg command output after connect - it is blank before connect

root@GL-MT1300:/etc/config# wg
interface: wg0
  public key: t9ZtL...Xw=
  private key: (hidden)
  listening port: 64373

peer: OQt6o....ouHM=
  endpoint: 98.155.123.123:51820
  allowed ips: 0.0.0.0/0
  transfer: 0 B received, 7.52 KiB sent
  persistent keepalive: every 25 seconds

/etc/config/network/:

root@GL-MT1300:/etc/config# cat network

config interface 'loopback'
        option ifname 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fdfb:99d3:73d0::/48'

config interface 'lan'
        option type 'bridge'
        option ifname 'eth0.1'
        option proto 'static'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option hostname 'GL-MT1300-944'
        option ipaddr '192.168.8.1'

config interface 'wan'
        option ifname 'eth0.2'
        option proto 'dhcp'
        option hostname 'GL-MT1300-944'
        option ipv6 '0'
        option metric '10'

config interface 'wan6'
        option ifname 'eth0.2'
        option proto 'dhcpv6'
        option disabled '1'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '0 1 2 3 6t'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '4 6t'

config interface 'guest'
        option ifname 'guest'
        option type 'bridge'
        option proto 'static'
        option ipaddr '192.168.9.1'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option bridge_empty '1'

config device 'wan_dev'
        option name 'eth0.2'
        option macaddr '94:83:c4:15:09:44'

config device 'lan_dev'
        option name 'eth0.1'
        option macaddr '94:83:c4:15:09:45'

/etc/config/wireguard/:

root@GL-MT1300:/etc/config# cat wireguard

config proxy
        option access 'DROP'
        option main_server 'home'
        option host '98.155.165.243'
        option enable '0'

config peers 'wg_peer_299'
        option name 'home'
        option address '192.168.99.2/32'
        option listen_port '64373'
        option private_key 'EOmKm9...kyy91NovjYaRQ3jHc='
        option dns '1.1.1.1'
        option end_point 'mydomain.com:51820'
        option public_key 'OQt6oI5peIv...pjR/pLsouHM='
        option allowed_ips '0.0.0.0/0'
        option persistent_keepalive '25'

alzhao · 2022-02-25T08:53:35.499Z

What is your Wireguard server? Your own server or commercial one?

I know some commercial vpn service providers can manage keys so pls make sure your key is valid.

When you disconnect and connect, does it work?

Before firmware 3.211 wireguard has a bug that could crash/disconnect when network has problems.

pseudosavant · 2022-02-25T17:58:26.909Z

It is my own Wireguard server running in a DigitalOcean droplet on a fully updated latest Ubuntu LTS OS. The configuration, for any of the peers, hasn’t changed in at least a year. It does have the 3.211 firmware on it already.

This configuration was working fine for two weeks. I didn’t change anything on the MT1300 or the WG ‘server’.

alzhao · 2022-02-26T04:58:51.495Z

Strange.

You didn’t do anything before it stoped working? e.g. upgrading the firmware.

As you have reconfiged everything it does not seems a wrong configuration.

Is there any change in the network environement?

Have you tried generate a new wireguard config and try?

pseudosavant · 2022-02-27T17:02:04.506Z

Nothing. I’ve never updated the firmware. It shipped with the latest.

I haven’t tried creating another wireguard peer config but considering this config works everywhere else, I doubt that is the issue. I don’t have easy access to change the Pi4 WG config right now.

My initial experience with the MT1300 was so good I was planning on upgrading my parent’s router to one of the better gl.inet models to replace their router and the Pi4. Configuration with goodcloud would be so much more convenient. I’m not going to do that if WG won’t work though.

The only other thing different going on on my network right now is my gigabit cable modem I use for my 500mbps service stopped connecting with my router’s (TP-Link Archer C7 v2, OpenWRT 19.07) switch at 1000mbps. The link speed is only 100mbps, even with a different cable. Everything works fine, I’m just not getting the max speeds I could get.

That issue probably pre-dates getting the MT1300 though. I just noticed it when I ran some speed tests to check the WAN/LAN throughput of the MT1300.

alzhao · 2022-02-28T09:50:02.316Z

pseudosavant:

I haven’t tried creating another wireguard peer config but considering this config works everywhere else, I doubt that is the issue.

A config should work everywhere. But not the same time. I believe that you didn’t use the same config at the same time though.

Oroville · 2022-02-28T12:22:21.049Z

Bro use zerotier on that bad boy much better i just installed it on the 1800 then on my phone setup the subnet route on the zerotier configuration page now i can access any device on my network without being connected with wireguard and also i can wakeup my nas and pc when connected to the network also any questions just ask

pseudosavant · 2022-02-28T23:39:32.535Z

Yes, I’m aware that each WG profile/config can only be used by one client at a time. I was always only trying to connect from one client at a time.

pseudosavant · 2022-02-28T23:40:50.951Z

I bought this device specifically to enable any wifi device (e.g. Roku, Xbox, etc) to connect over VPN. Not just the Windows, Android, and iOS ones.