Wireguard client not starting up,help please

Installing and Using OpenWrt
1

Hello.
I've configured a wireguard server on a vps, when i use wg client on my pc it connects and everything works, but when i do it on my GL-AR300M16 router with openwrt it doesnt.

The first error i had was this one:

Sun Sep 10 15:23:56 2023 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Sun Sep 10 15:23:57 2023 daemon.notice netifd: Interface 'wgclient' is setting up now
Sun Sep 10 15:23:58 2023 daemon.notice netifd: wgclient (10535): RTNETLINK answers: Permission denied

I solved this one by enabling ipv6 on router.

Now i'm stuck on this error and i can't get out:

Sun Sep 10 15:30:29 2023 daemon.notice netifd: Interface 'wgclient' is setting up now
Sun Sep 10 15:32:21 2023 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=/
Sun Sep 10 15:32:26 2023 daemon.notice netifd: wgclient (24636): [!] Section @forwarding[0] is disabled, ignoring section
Sun Sep 10 15:32:26 2023 daemon.notice netifd: wgclient (24636): [!] Section @forwarding[1] is disabled, ignoring section
Sun Sep 10 15:32:26 2023 daemon.notice netifd: wgclient (24636): [!] Section gls2s option 'reload' is not supported by fw4
Sun Sep 10 15:32:26 2023 daemon.notice netifd: wgclient (24636): [!] Section gls2s specifies unreachable path '/var/etc/gls2s.include', ignoring section
Sun Sep 10 15:32:26 2023 daemon.notice netifd: wgclient (24636): [!] Section glblock option 'reload' is not supported by fw4
Sun Sep 10 15:32:26 2023 daemon.notice netifd: wgclient (24636): [!] Section vpn_server_policy option 'reload' is not supported by fw4
Sun Sep 10 15:32:26 2023 daemon.notice netifd: wgclient (24636): [!] Automatically including '/usr/share/nftables.d/chain-pre/mangle_output/01-process_mark.nft'
Sun Sep 10 15:32:26 2023 daemon.notice netifd: wgclient (24636): [!] Automatically including '/usr/share/nftables.d/chain-post/mangle_output/out_conn_mark_restore.nft'
Sun Sep 10 15:32:28 2023 daemon.notice netifd: wgclient (24636): DROP  all opt -- in * out *  0.0.0.0/0  -> 0.0.0.0/0   match-set GL_MAC_BLOCK src
Sun Sep 10 15:32:29 2023 daemon.notice netifd: wgclient (24636): Failed to parse json data: unexpected character
Sun Sep 10 15:32:29 2023 daemon.notice netifd: wgclient (24636): uci: Entry not found
Sun Sep 10 15:32:29 2023 daemon.notice netifd: wgclient (24636): cat: can't open '/tmp/run/wg_resolved_ip': No such file or directory
Sun Sep 10 15:32:29 2023 daemon.notice netifd: Interface 'wgclient' is now down
Sun Sep 10 15:32:29 2023 daemon.notice netifd: Interface 'wgclient' is setting up now
Sun Sep 10 15:32:31 2023 user.notice mwan3[24817]: Execute ifdown event on interface wgclient (unknown)
Sun Sep 10 15:32:35 2023 user.notice firewall: Reloading firewall due to ifdown of wgclient ()

Keep in mind that the client config connects to the server on PC, is a software problem on the router then. Help me please

2

It looks like you might be using firmware that is not from the official OpenWrt project (i.e. you're using GL.iNet firmware).

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

  1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
  2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
  3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

2 Likes
3

I don't believe nothing i'm not that good in such things... in glinet forum nobody reply...
I only know that "Built based on OpenWrt 22.03.4"

And this one is for my device but i don't want to loose glinet gui
https://firmware-selector.openwrt.org/?version=22.03.5&target=ath79%2Fgeneric&id=glinet_gl-ar300m16

4

It might be based on OpenWRT, but additions they've made (like the WG client 'application') are their own addition. We can't assist with it. You need to get support from GL.iNet.

4 Likes
5

much more functional with the openwrt.org firmware. worth the change. Stability, Forum support, easily customizable and much more.

1 Like
6

Yes but then i don't know how to use it, i mean is there a gui for it to change ssid, connect vpn etc... I don't know im not that good sorry if someone can explain

7

https://www.youtube.com/@OneMarcFifty

8

Somewhere in some file there is an invalid character. Not sure if it helps you somehow, but at least you have an idea what is the problem.

2 Likes