ZebMcKayhan
Very Senior Member
not that I'm aware of. you will have to capure it from the terminal window... still not working eah?
//Zeb
Wireguard Session Manager - Discussion (2nd) thread
- Thread starter Martineau
- Start date
//Zeb
Martineau
Part of the Furniture
The SSH client is the best method to record the info to a file, ....although you can cut'n'paste etc. but that can be tedious.. although you can copy either the 'screen' or 'session'
e.g. I use
XShell6 (it's free for home use) so you start the logging.....then when you have issued the commands you wish to capture, simply 'stop' the log, and it will ask you where to save the log, then you can click on 'Open Log Folder'
It's not perfect (for retaining menu/table column formatting etc.) but when performing a lengthy verbose debugging session it saves me a lot of time!
Last edited:
Stingray123
Occasional Visitor
Ah, that gives me some answers for the unexpected results I was seeing when trying to import before. I think your new import change will be helpful for the less experienced like me.
Thank you Martineau and ZebMcKayhan for all your efforts going into Session Manager!
@Martineau, I'm looking for some direction here. During the last updates to
I had (and have)
It all looked like that:
I noted that you recently removed the requirement to have at least one client per interface in order to be able to route IPSets, so I removed the dummies and it all looked cleaner.
Now, late in the weekend with the last update I think I've seen the routing re-arranged as follows:
It all works now (there is little to nothing one can't do with the -route-up/down and -up/down scripts.)
I can see that not having 2 WAN routes to the
The question remains what was the leading factor to the change? And why the change from the earlier priority definition for routing clients running on different protocols?
dev and main branches the RPDB build principles have changed, I believe. I had (and have)
wgm working well (and very well) over the last several months. I built the routing tables based on your early view at http://www.snbforums.com/threads/se...discussion-2nd-thread-75129.70787/post-695607.It all looked like that:
Code:
asmin@RT-AX86U:/tmp/mnt/asus/conf# ip rule
0: from all lookup local
220: from all lookup 220
9810: from all fwmark 0xd2 lookup 210
9890: from all fwmark 0x8000/0x8000 lookup main
9892: from all fwmark 0x7010/0x7010 lookup 124
9893: from all fwmark 0x4010/0x4010 lookup 123
9894: from all fwmark 0x2010/0x2010 lookup 122
9895: from all fwmark 0x1010/0x1010 lookup 121
9911: from 192.168.1.246 lookup 121
9911: from 192.168.1.230 lookup 121
9990: from all fwmark 0x8000/0x8000 lookup main
9992: from all fwmark 0x7000/0x7000 lookup ovpnc4
9994: from all fwmark 0x2000/0x2000 lookup ovpnc2
9995: from all fwmark 0x1000/0x1000 lookup ovpnc1
10210: from 192.168.1.237 lookup ovpnc1
10211: from 192.168.1.253 lookup ovpnc1
10212: from 192.168.1.238 lookup ovpnc1
32766: from all lookup main
32767: from all lookup defaultI noted that you recently removed the requirement to have at least one client per interface in order to be able to route IPSets, so I removed the dummies and it all looked cleaner.
Now, late in the weekend with the last update I think I've seen the routing re-arranged as follows:
Code:
asmin@RT-AX86U:/tmp/mnt/asus/conf# ip rule
0: from all lookup local
220: from all lookup 220
9810: from all fwmark 0xd2 lookup 210
9911: from 192.168.1.246 lookup 121
9911: from 192.168.1.230 lookup 121
9990: from all fwmark 0x8000/0x8000 lookup main
9991: from all fwmark 0x1010/0x1010 lookup 121
9992: from all fwmark 0x7000/0x7000 lookup ovpnc4
9992: from all fwmark 0x2010/0x2010 lookup 122
9993: from all fwmark 0x4010/0x4010 lookup 123
9994: from all fwmark 0x2000/0x2000 lookup ovpnc2
9994: from all fwmark 0x7010/0x7010 lookup 124
9995: from all fwmark 0x1000/0x1000 lookup ovpnc1
10210: from 192.168.1.237 lookup ovpnc1
10211: from 192.168.1.253 lookup ovpnc1
10212: from 192.168.1.238 lookup ovpnc1
32766: from all lookup main
32767: from all lookup defaultIt all works now (there is little to nothing one can't do with the -route-up/down and -up/down scripts.)
I can see that not having 2 WAN routes to the
main table makes sense.The question remains what was the leading factor to the change? And why the change from the earlier priority definition for routing clients running on different protocols?
Martineau
Part of the Furniture
Initially with
wireguard_manager, I didn't want to have different fwmarks for both my original OpenVPN and WireGuard design.There are users that apparently use both OpenVPN and WireGuard 'clients' concurrently for daily use, but ideally, I would hope that after the initial feasibility testing of WireGuard 'clients' they would deem it acceptable to agree that WireGuard (when configured and UP) should take priority - should the decision to drop OpenVPN clients entirely wasn't chosen i.e. use one or the other.
As you have deliberately chosen/assigned custom WireGuard fwmarks, can you be 100% sure that the lower bit in your wg11 fwmark 0x1010 isn't used by the ASUS/Broadcom?
When I chose 0x1000 for ovpnc1, at the time this was deemed to be a good choice given some of the lower 24 bits were definitely used/reserved by ASUS so best to stay clear to avoid any weird behaviour/clash.
I'm not saying single bit fwmark 0x1000 (and 0x2000, 0x4000) is still 100% safe, but if not, then I (and by association so too @Xentrk) have successfully blagged our way forward and enjoyed a rewarding good run over the last 4-5 years!
At the moment I don't have an RT-AX86U etc. so I don't know if wireguard_manager will be around much longer given WireGuard's formal inclusion in the official firmware for that model et al., nor indeed @RMerlin's future plans for VPN Director.
Abject apologies if I have broken/inconvenienced your fwmark WireGuard environment.
Last edited:
ZebMcKayhan
Very Senior Member
Hello,
I have managed to compile a "wireguard-kernel_1.0.20210606-k51_1_aarch64-3.10.ipk". I currently don't have any AX88U router to test it on so it is completely untested. if any AX88U owner have the guts to test it: PM me and I will send a download link with some instructions.
//Zeb
Prerequisites is of course you have a working wgm setup today.
I have managed to compile a "wireguard-kernel_1.0.20210606-k51_1_aarch64-3.10.ipk". I currently don't have any AX88U router to test it on so it is completely untested. if any AX88U owner have the guts to test it: PM me and I will send a download link with some instructions.
//Zeb
Prerequisites is of course you have a working wgm setup today.
Last edited:
ZebMcKayhan
Very Senior Member
Looking good, Again!
as I didnt wanna mess up existing configs (I can only generate 5, when I generate the 6:th the first one gets disabled, on the other hand they seem to live forever) so I modified the keys of an existing one, just to get the import:
named it IntegritySE.conf
Code:
E:Option ==> import IntegritySE
[✔] Config IntegritySE import as wg13 successIntegritySE.conf gets renamed to IntegritySE.conf_imported and wg13.conf is the result of the import.
Code:
E:Option ==> peer wg13 del
Deleting 'client' Peer (wg13)
Press y to CONFIRM or press [Enter] to SKIP.
y
'client' Peer wg13 DELETEDwg13.conf is removed.
Code:
mv IntegritySE.conf_imported IntegritySE.conftesting full name import
Code:
E:Option ==> import IntegritySE.conf
[✔] Config IntegritySE import as wg13 success
Code:
mv IntegritySE.conf_imported IntegritySE.conftesting name= option:
Code:
E:Option ==> import IntegritySE name=wg15
[✔] Config IntegritySE import as wg15 successtesting different ending:
Code:
mv IntegritySE.conf_imported IntegritySE.Whatever
Code:
E:Option ==> import IntegritySE.Whatever
***ERROR: WireGuard 'client' Peer (/opt/etc/wireguard.d/IntegritySE.Whatever) config NOT found?....skipping import Peer 'IntegritySE.Whatever' requesttesting additional . :
Code:
mv IntegritySE.Whatever Integrity.SE.conf
Code:
E:Option ==> import Integrity.SE
[✔] Config Integrity.SE import as wg13 successseems rock-solid! great work!
so as long as the file has a .conf ending there shouldnt be any problem.
//Zeb
Edit: also tried IntegritySE without .conf but it wouldnt import... so make sure the filename is xxxxxxxx.conf and it will work!
Last edited:
Martineau
Part of the Furniture
Thanks for taking the time to post your detailed and methodical/comprehensive tests...Quality Assurance engineering background perhaps?
ZebMcKayhan
Very Senior Member
Ooh, the shame!!
Most QA people I've worked with are sitting doing fish-leg diagram, 8d reports, fmea, iso9000-whatever certifications. They don't care if the product works or not as long as the paper trailing looks good.
Electronics design engineer actually and I wouldn't say close enough (I usually don't get along with the QA guys/girls). Hopefully my experience is not representative....
Sir, it is I that should be thankful. Thanks for a great script!
//Zeb
By the way, I also tested to import a config where the Adress and DNS were commented and it works just as good. Wgm seem to disregard these hashes. You are one step ahead, again...
Last edited:
@Martineau, something totally cosmetic. Is it possible to tag route table 121 as wgvpnc1?
I see the file but it is read only.
/etc/iproute2/rt_tables
Something like this in your old post possible?
www.snbforums.com
I see the file but it is read only.
/etc/iproute2/rt_tables
Something like this in your old post possible?
Port Forward while using VPN Client
Router: ASUS RT-AC87U Firmware: 378.56_2 I am currently using the VPN Client on my router to selective tunnel traffic to/from some of the LAN clients. In other words, I have "Redirect Internet traffic" set to "Policy Rules"... ..and I have rules for some of the LAN clients where I specify...
www.snbforums.com
Martineau
Part of the Furniture
Yes.@Martineau, something totally cosmetic. Is it possible to tag route table 121 as wgvpnc1?
I see the file but it is read only.
/etc/iproute2/rt_tables
Something like this in your old post possible?
Port Forward while using VPN Client
Router: ASUS RT-AC87U Firmware: 378.56_2 I am currently using the VPN Client on my router to selective tunnel traffic to/from some of the LAN clients. In other words, I have "Redirect Internet traffic" set to "Policy Rules"... ..and I have rules for some of the LAN clients where I specify...
e.g. Clone '/etc/iproute2/rt_tables' to '/jffs/configs/rt_tables' then when you have modified ''/jffs/configs/rt_tables'' use the following in the appropriate script ( I use
init-start) to mount your custom name table.
Code:
if [ -f /jffs/configs/rt_tables ]; then
# Use custom table
logger -st "($(basename $0))" "Custom RPDB name table /jffs/configs/rt_tables replaces /etc/iproute2/rt_tables"
mount -o bind /jffs/configs/rt_tables /etc/iproute2/rt_tables # Override 'ovpncX' with 'TalkTalk', NewYork etc.
# df
# umount /rom/etc/iproute2/rt_tables
fidf, then use umount prior to making more edits before remounting.
Code:
df
Filesystem 1K-blocks Used Available Use% Mounted on
ubi:rootfs_ubifs 79016 66148 12868 84% /
devtmpfs 220048 4 220044 0% /dev
tmpfs 220160 420 219740 0% /var
tmpfs 220160 1660 218500 1% /tmp/mnt
mtd:bootfs 4480 3364 1116 75% /bootfs
tmpfs 220160 1660 218500 1% /tmp/mnt
mtd:data 8192 636 7556 8% /data
tmpfs 220160 1660 218500 1% /tmp
/dev/mtdblock9 48128 6188 41940 13% /jffs
/dev/sda1 14779860 3458076 10570988 25% /tmp/mnt/RT-AC86U
Code:
cat /etc/iproute2/rt_tables
100 wan0
111 ovpnc1
112 ovpnc2
113 ovpnc3
114 ovpnc4
115 ovpnc5
200 wan1
Code:
cat /jffs/configs/rt_tables
100 wan0
111 ovpnc1
112 ovpnc2
113 ovpnc3
114 ovpnc4
115 ovpnc5
200 wan1
# Custom Wireguard - Martineau
121 wgvpnc1
122 wgvpnc2
123 wgvpnc3
124 wgvpnc4
125 wgvpnc5
Code:
mount -o bind /jffs/configs/rt_tables /etc/iproute2/rt_tables
df
Filesystem 1K-blocks Used Available Use% Mounted on
ubi:rootfs_ubifs 79016 66148 12868 84% /
devtmpfs 220048 4 220044 0% /dev
tmpfs 220160 420 219740 0% /var
tmpfs 220160 1656 218504 1% /tmp/mnt
mtd:bootfs 4480 3364 1116 75% /bootfs
tmpfs 220160 1656 218504 1% /tmp/mnt
mtd:data 8192 636 7556 8% /data
tmpfs 220160 1656 218504 1% /tmp
/dev/mtdblock9 48128 6196 41932 13% /jffs
/dev/sda1 14779860 3458076 10570988 25% /tmp/mnt/RT-AC86U
/dev/mtdblock9 48128 6196 41932 13% /rom/etc/iproute2/rt_tables
Code:
cat /etc/iproute2/rt_tables
100 wan0
111 ovpnc1
112 ovpnc2
113 ovpnc3
114 ovpnc4
115 ovpnc5
200 wan1
# Custom Wireguard - Martineau
121 wgvpnc1
122 wgvpnc2
123 wgvpnc3
124 wgvpnc4
125 wgvpnc5
Code:
ip route show table 121
0.0.0.0/1 dev wg11 scope link
128.0.0.0/1 dev wg11 scope link
192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.1
ip route show table wgvpnc1
0.0.0.0/1 dev wg11 scope link
128.0.0.0/1 dev wg11 scope link
192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.1
Last edited:
Martineau
Part of the Furniture
I decided to ensure that the WireGuard configuration file used by the
wireguard_manager import feature would adhere to the WIreGuard naming standard as expected by wg-quick e.g. xxxxxx.confThe intention was that transferring a working xxxxxx.conf file between platforms would eliminate any typos confusion and keep the process honest etc.
If IntegritySE does allow their created config 'IntegritySE' to be used (or retrieved) as-is without the .conf suffix then I'll still prefer to enforce the .conf naming practice.
Last edited:
Very nice. It works well.
Just added the script into init-start. I suppose this is required so that the custom rt-tables get mounted again during the next reboot. I resists to reboot the router for now. Trying to get more uptime.
Martineau
Part of the Furniture
Correct, and exactly how I recommend.Very nice. It works well.
Just added the script into init-start. I suppose this is required so that the custom rt-tables get mounted again during the next reboot.
I'm not sure how the future firmware implementation will make it human-friendly (if at all), but currently the custom WireGuard routing table alias could be anything e.g. 'NewYork' etc., unless your scripts need/expect to have a formal 'wgvpnc' prefix.
Last edited:
Thanks again. Yes, there is one part of the script I can change from ...table 12$WGVPN_ID to ...table wgvpnc$WGVPN_ID. Actually I have get used to your numbering and I can keep it as is.
ZebMcKayhan
Very Senior Member
no, they dont... they are only .conf named. I dont know how all others are though but I agree that wgm should require the .conf to make sure we are trying to import something compatible.
what happens if you import the Wireguard.db by mistake (in the same folder)?? probably some friendly message telling you that this did not go as expected, or maybe a more severe import of some random data? or worse?
Android Wireguard app requires the import file to be .conf or .zip (just a zipped .conf file??). if I try to import i.e. a .jpg file it says "error, must be a .conf or .zip file".
so perhaps the error message for importing is a tad confusing:
Code:
***ERROR: WireGuard 'client' Peer (/opt/etc/wireguard.d/IntegritySE.Whatever) config NOT found?....skipping import Peer 'IntegritySE.Whatever' requestMaybee it should be:
Code:
***ERROR: WireGuard 'client' Peer (/opt/etc/wireguard.d/IntegritySE.Whatever.conf) NOT found?....skipping import Peer 'IntegritySE.Whatever' request//Zeb
Last edited:
Martineau
Part of the Furniture
Code:
e = Exit Script [?]
E:Option ==> import WireGuard.db
***ERROR: WireGuard 'client' Peer (/opt/etc/wireguard.d/WireGuard.db) config NOT found?....skipping import Peer 'WireGuard.db' requeste.g. issue:
Code:
e = Exit Script [?]
E:Option ==> import ?
Available Peer Configs for import:
SGS8.conf
mlvd-us53.conf
ubimo.confMaybe indeed
ZebMcKayhan
Very Senior Member
Yes :\ I've confirmed that there was a issue with the killswitch in 4.11 and have permanently disabled it in 4.12b2 for now. But I still have the same issue when I start wg11 Internet dies, I can't reach 'anything'. As soon as I stop it, Internet works again. I don't have this issue with OpenVPN on the router or when I try the exact same Wireguard key in another device.
And I can't see anything wrong in the imported Wireguard key in WGM. The only difference I see is that I DNS and Address is disabled with # in front of them.
I'm not familiar with Linux and iptables at all, so the wgm diag doesn't say anything to me. But I did sent it to @Martineau
I'm on Merlin fw RT-AC86U_386.3_2 for my Asus RT-AC86U
WAN on the Router:
I have tried different DNS (Cloudflare and my VPN Provider) and automatic from ISP
Disabled Rebind protection and DNSSEC
LAN on the router:
DNSFilter is enabled and Global set to Router
Restarted router within the gui and also tried a hard restart.
Disabled Skynet and Diversion just in case.
But yea... the issue remains...
ZebMcKayhan
Very Senior Member
ok, lets hope @Martineau finds anything that could be fixed.
if you, from the terminal issue "wg show" (not inside wgm) do you see any traffic (rx/tx) bytes or are they both 00?
if the peer is working and you have at least any rx/tx bytes you could check if it is DNS related by pinging an ip that does not need to be resolved (like www.google.com):
Code:
ping 142.250.74.36and see if you get any replies... if you do, the connection works you just cant resolve names (which usually appears as not being able to access anything).
some VPN ISP blocks access to other DNS servers than their own, which is included in the .conf file. I dont know how this is with OVPN, but using the DNS from the original .conf file might be required. DNS in @Odkrys scripts works differently depending if you use default routing or policy routing.
when you had this working did you use default or policy routing? did you use the DNS from the original .conf file and moved into wg scripts?
wgm usually overrides WAN DNS from the router GUI from the one you specify inside wgm. The DNS should be changed inside wgm by:
Code:
peer wg11 dns=9.9.9.9
Code:
restart wg11make a note of your original DNS from the .conf file and try to swap back and forth. but this all ofcource requires the peer to work, meaning you have some rx/tx bytes and can ping ipadresses.
//Zeb
Similar threads
Similar threads
Similar threads
-
New Addon - ChatAI - have a chat session with Googles Gemini AI Bot- Started by JGrana
- Replies: 2
-
connmon Making config changes invokes password manager in MacOS
- Started by Jeff-
- Replies: 4
-
VPNMON VPNMON-R3 - Early, early alpha discussion, progress & screenshots- Started by Viktor Jaep
- Replies: 17