surfshark not working...

Technical Support for Routers
1

Tried surfshark, getting the following error when connecting... pls advise!

"Sun Oct 6 20:40:45 2024 daemon.notice netifd: Interface 'wgclient' is now down
Sun Oct 6 20:40:45 2024 daemon.notice netifd: Interface 'wgclient' is setting up now
Sun Oct 6 20:40:46 2024 daemon.notice netifd: wgclient (11638): Key is not the correct length or format: `<insert_your_private_key_here>='
Sun Oct 6 20:40:46 2024 daemon.notice netifd: wgclient (11638): Configuration parsing error
Sun Oct 6 20:40:46 2024 daemon.info ModemManager[11675]: hotplug: add network interface wgclient: event processed
Sun Oct 6 20:40:51 2024 daemon.info ModemManager[11887]: hotplug: remove network interface wgclient: event processed"

2

The error is already shown in the logs, the private key isn't correctly formatted.

Can you post your WireGuard config - maybe even with the private key, if you can revoke it?

3

thank you for the response. i upgraded the firmware to 4.7.0. tried inputting username/password, always got an error as invalid - apparently not. so i downloaded conf files from surfshark key pairs, got the following erros in the log:
Mon Oct 7 14:32:48 2024 daemon.notice netifd: Interface 'wgclient' is setting up now
Mon Oct 7 14:34:34 2024 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-GIVEUP SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Mon Oct 7 14:34:34 2024 daemon.err eco[6418]: Error: argument "mptcp_wgclient" is wrong: table id value is invalid
Mon Oct 7 14:34:34 2024 daemon.notice netifd: Interface 'wgclient' is now down
Mon Oct 7 14:34:34 2024 daemon.notice netifd: Interface 'wgclient' is setting up now
Mon Oct 7 14:34:34 2024 user.notice firewall: Reloading firewall due to ifdown of wgclient ()

no clue what is missing... pls advise. tks.

4

...and here's the sample conf i uploaded in wgclient:

#
# Use this configuration with WireGuard client
#
[Interface]
Address = 10.14.0.2/16
PrivateKey = mCE1C3+GnibITTl0qQ6TBPuQVcBLL8ZMUjQRs6Auw2A=
DNS = 162.252.172.57, 149.154.159.92
[Peer]
PublicKey = bD/m2mdKxJXG2wTkLsmWpiW8xZwkDdrrrwC44auOhQg=
AllowedIPs = 0.0.0.0/0
Endpoint = 93.152.212.64:51820
5

If you download wireguard config from surfshark manually you need to replace your private key.
Otherwise it will be like below and will not work.

image
image807×360 6.9 KB

1 Like
6

I just tested my surfshark account and it just works OK. The username and password are those used to login surfshark web portal.

image
image871×733 41.2 KB

7

thank you. i keep getting an error when trying to connect using the above conf. it seems wgclient network interface was always automatically created instead of using a network interface i manually created following the surfshark instructions, but failed. not sure if there's a missing piece or the interface i created was wrong (not transmitting packets). pls help.

8

The Surfshark instructions won't work, the wgclient on GL firmware will take care of everything.
So you only need to import the config and it should work without issues.

9

Thanks. What version of firmware are you using?

10

Pls make sure you have normal Internet, double check your username and password,
don't use in Egypt, UAE and Russia
and it should be OK.

11

i've rolled back to 4.6.4 and installed all the luci-proto extensions except one (requires kmod-batman... which is not available), still getting an error during wgclient setup. looked into network interface, still says protocol not supported for wgclient - what software am i missing to install?

12

Why do you try to adjust the protocol in luci, this won't work …

Just follow the manual for Surfshark here: How to get configuration files from WireGuard service providers - GL.iNet Router Docs 4

13

tried all that... didn't work. created a network interface called WG0 as instructed, but never gets used when connecting. the system automatically creates a new interface called wgclient. but when i checked this interface it says protocol not supported and there's a link pointing to install luci-proto extensions with 27 in the list...
and here's the log:
Tue Oct 8 05:16:56 2024 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-GIVEUP SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Tue Oct 8 05:16:57 2024 daemon.info ModemManager[17221]: hotplug: remove network interface wgclient: event processed
Tue Oct 8 05:16:57 2024 daemon.notice netifd: Interface 'wgclient' is now down
Tue Oct 8 05:16:57 2024 daemon.notice netifd: Interface 'wgclient' is setting up now
Tue Oct 8 05:16:57 2024 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Tue Oct 8 05:16:57 2024 daemon.info ModemManager[17286]: hotplug: add network interface wgclient: event processed
Tue Oct 8 05:18:08 2024 daemon.info ModemManager[18228]: hotplug: remove network interface wgclient: event processed

14

image
image1585×137 15.7 KB

15

As I said above: Don‘t try to create interfaces. Just download the WireGuard config and import it via the GL GUI.

WireGuard inside the GL firmware works a bit different than on OpenWrt standard.

No additional interfaces needed - and they won't work anyway.

16

the screen shot shows the interface automatically created by the system, but it's not working because of missing protocol extensions. i've added the extensions and rebooted. still doesn't work. here's the log:
Tue Oct 8 06:39:34 2024 user.notice ModemManager: hotplug: event reported: action=remove, name=wgclient, subsystem=net
Tue Oct 8 06:39:34 2024 daemon.notice netifd: Interface 'wgclient' is now down
Tue Oct 8 06:39:34 2024 daemon.notice netifd: Interface 'wgclient' is setting up now
Tue Oct 8 06:39:34 2024 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Tue Oct 8 06:39:34 2024 user.notice ModemManager: hotplug: add network interface wgclient: event processed
Tue Oct 8 06:39:34 2024 user.notice ModemManager: hotplug: event reported: action=add, name=wgclient, subsystem=net
Tue Oct 8 06:40:24 2024 daemon.err eco[8968]: Error: argument "mptcp_wgclient" is wrong: table id value is invalid
Tue Oct 8 06:40:24 2024 user.notice ModemManager: hotplug: remove network interface wgclient: event processed
Tue Oct 8 06:40:24 2024 user.notice ModemManager: hotplug: event reported: action=remove, name=wgclient, subsystem=net
Tue Oct 8 06:40:24 2024 daemon.notice netifd: Interface 'wgclient' is now down
Tue Oct 8 06:40:24 2024 user.notice firewall: Reloading firewall due to ifdown of wgclient ()

17

Something is odd here, but I guess it is odd on Surfsharks side.
I am curious about the mptcp_wgclient because WireGuard is UDP by default.

Is there any weird switch on Surfsharks side, like multi-hop, TCP only mode or something like that?

18

no odd switch i can see in surfsharks