Correct (well that was the intention) as you may already have issued custom
peer wg1X rule add commands for a 'client' Peer, plus VPN Director only supports 5 clients whereas you can use have 9 wg_manager clients - wg16 thru wg19.OVPN?....WireGuard 'client' Peers most certainly have to be ACTIVE for them to be physically defined/honoured (which occurs during their initialisation), but the VPN Director rules need to be cloned into the SQL database first.
IIRC You have previous form (earliest reported 2020?) about being unable to issue uf [dev] not just for
wg_manager but other ADDons?
Unfortunately, I doubt any new immediate future
wg_manager WebUI developments would benefit you.auto=p for each new import will be available in v4.17bD) without needing to use SSH, although you can't install wg_manager without having skills to use SSH in the first place.! Error loading wireguard kernel module... what router and firmware are you on?
cd /
find -name wireguard.koIf the
wgm alias can't be found then try the full pathsh /jffs/addons/wireguard/wg_manager.she = Exit Script [?]
E:Option ==> ?e = Exit Script [?]
E:Option ==> vx#USE_ENTWARE_KERNEL_MODULEF2 to save the modification; Press 'Y'e = Exit Script [?]
E:Option ==> getmodulese = Exit Script [?]
E:Option ==> loadmodulese = Exit Script [?]
E:Option ==> restart wg21admin@RT-AC86U-D7D8:/tmp/home/root# ip6tables -nvL DNSFILTER -t nat
Chain DNSFILTER (2 references)
pkts bytes target prot opt in out source destinati
on
51 4371 DNAT all * * ::/0 ::/0
to:aaff:a37f:fa75:1::1
admin@RT-AC86U-D7D8:/tmp/home/root# ip6tables -nvL WGDNS1 -t nat
Chain WGDNS1 (2 references)
pkts bytes target prot opt in out source destinati
on
admin@RT-AC86U-D7D8:/tmp/home/root# ip6tables -nvL WGDNS2 -t nat
Chain WGDNS2 (2 references)
pkts bytes target prot opt in out source destinati
on
admin@RT-AC86U-D7D8:/tmp/home/root# iptables -nvL WGDNS1 -t nat
Chain WGDNS1 (2 references)
pkts bytes target prot opt in out source destinati
on
admin@RT-AC86U-D7D8:/tmp/home/root# iptables -nvL WGDNS2 -t nat
Chain WGDNS2 (2 references)
pkts bytes target prot opt in out source destinati
onE:Option ==> start wg12 debug
Requesting WireGuard® VPN Peer start (wg12)
wg_manager-clientwg12: Initialising WireGuard® VPN 'client' Peer (wg1
2) in Policy Mode to us.wireguard.5july.net:42911 (# Integrity USA) DNS=9.9.9
.9,2620:fe::fe
<snip>
[#] ip route add table 122 192.168.1.0/24 proto kernel scope link src 192.168
.1.1 dev br0
[#] ip -6 route add table 122 aaff:a37f:fa75:1::/64 proto kernel metric 256 p
ref medium dev br0
[#] ip -6 route add table 122 fe80::/64 proto kernel metric 256 pref medium d
ev br0
[+] wg12-up.sh
[#] iptables -t mangle -I FORWARD -o wg12 -p tcp -m tcp --tcp-flags SYN,RST S
YN -j TCPMSS --clamp-mss-to-pmtu -m comment --comment WireGuard 'client'
[#] iptables -t mangle -I FORWARD -i wg12 -p tcp -m tcp --tcp-flags SYN,RST S
YN -j TCPMSS --clamp-mss-to-pmtu -m comment --comment WireGuard 'client'
[#] iptables -t mangle -I FORWARD -o wg12 -j MARK --set-xmark 0x01/0x7 -m com
ment --comment WireGuard 'client'
[#] iptables -t mangle -I PREROUTING -i wg12 -j MARK --set-xmark 0x01/0x7 -m
comment --comment WireGuard 'client'
[#] iptables -t nat -I POSTROUTING -s 192.168.1.1/24 -o wg12 -j MASQUERADE -m
comment --comment WireGuard 'client'
[#] iptables -t nat -I PREROUTING -p tcp -m tcp --dport 53 -j WGDNS2 -m comme
nt --comment WireGuard 'client2 DNS'
[#] iptables -t nat -I PREROUTING -p udp -m udp --dport 53 -j WGDNS2 -m comme
nt --comment WireGuard 'client2 DNS'
[#] ip6tables -t mangle -I FORWARD -o wg12 -p tcp -m tcp --tcp-flags SYN,RST
SYN -j TCPMSS --clamp-mss-to-pmtu -m comment --comment WireGuard 'client'
[#] ip6tables -t mangle -I FORWARD -i wg12 -p tcp -m tcp --tcp-flags SYN,RST
SYN -j TCPMSS --clamp-mss-to-pmtu -m comment --comment WireGuard 'client'
[#] ip6tables -t mangle -I FORWARD -o wg12 -j MARK --set-xmark 0x01/0x7 -m co
mment --comment WireGuard 'client'
[#] ip6tables -t mangle -I PREROUTING -i wg12 -j MARK --set-xmark 0x01/0x7 -m
comment --comment WireGuard 'client'
[#] ip6tables -t nat -I POSTROUTING -s aaff:a37f:fa75:1::1/64 -o wg12 -j MASQ
UERADE -m comment --comment WireGuard 'client'
[#] ip6tables -t nat -I PREROUTING -p tcp -m tcp --dport 53 -j WGDNS2 -m comm
ent --comment WireGuard 'client2 DNS'
[#] ip6tables -t nat -I PREROUTING -p udp -m udp --dport 53 -j WGDNS2 -m comm
ent --comment WireGuard 'client2 DNS'
wg_manager-clientwg12: Initialisation complete.sh -x /jffs/addons/wireguard/wg_client wg12 policy > "/opt/tmp/wg12_start" 2>&1OK, the modules (as expected) are included in the firmware.
e = Exit Script [?]
E:Option ==> debuge = Exit Script [?]
E:Debug mode enabledOption ==> loadmodulesE:Option ==> restart wg12
Requesting WireGuard® VPN Peer restart (wg12)
Restarting Wireguard® 'client' Peer (wg12)
wg_manager-clientwg12: WireGuard® VPN 'client' Peer (wg12) to us.wireguard.5july.net:42911 (# Integrity USA) Terminated
wg_manager-clientwg12: Initialising WireGuard® VPN 'client' Peer (wg12) in Policy Mode to us.wireguard.5july.net:42911 (# Integrity USA) DNS=9.9.9.9,2620:fe::fe
PEER_DNS =
TARGET_LOOKUP = 122
VPN_IP = aaff:a37f:fa75:6::1/64
PEERDNS_LIST =
PEER_DNS =
TARGET_LOOKUP = 122
VPN_IP = 192.168.6.0/24
PEERDNS_LIST =
wg_manager-clientwg12: Initialisation complete.create_client_list(){
local PEER_DNS=$PEER_DNS_LIST #Added line for dns fix
local PEERDNS_LIST=${PEER_DNS//,/ }You updated to 386.7 maybee? Looks like some firmware issue with paths (shortcuts and some ssh apps):
/opt/bin/wg_managerebug mode enabledOption ==> loadmodulesI noted this line but i swear i did the mod that u asked me in post #345 and i have just checked and the line #USE_ENTWARE_KERNEL_MODULE is still uncommented!
This is just initialization of the variable, 4 lines down the tag is evaluated and variable changed:
Yes I did. Updated last week. That’s more likely when it stopped working. I will try the full path.
full path works! thank you.
E:Option ==> vx# For Routers that include WireGuard Kernel/User Space tools, allow overriding with supported 3rd-Party/Entware versions
# Use command 'vx' to edit this setting.
USE_ENTWARE_KERNEL_MODULEE:Option ==> getmodules devE:Option ==> loadmodules
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!
