Menu
What's new
By:
Filters Better Search

Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. A

    Wireguard Session Manager - Discussion (3rd) thread

    Working as hoped, can add and remove passthru devices in any order and all work as desired. Thanks again for all your effort is getting this to work.
  2. A

    Wireguard Session Manager - Discussion (3rd) thread

    Hi @Martineau Not sure if this is intended, but I can only have one device passthru rule working at a time. So if I add then I see Added to ip and ip -6 rules as expected, but if I then add then while the command completes without error and peer wg11 shows Selective Routing RPDB...
  3. A

    Wireguard Session Manager - Discussion (3rd) thread

    Client v4.16.19 nailed it. Code removed for both ipv4 and ipv6. :D:D
  4. A

    Wireguard Session Manager - Discussion (3rd) thread

    I have updated and the revised client 4.16.18 is showing however after removing the passthu the ip / ip -6 rules are not being removed. What am I missing / can I do?
  5. A

    Wireguard Session Manager - Discussion (3rd) thread

    I have updated and rebooted (just in case) and wg_server is now v4.16.13 The grep errors from specified IPs rather than a device name are now all gone, however I am still having issues if I remove a passthru rule So if I load the rule as then whether I try the rules are not removed (if I run...
  6. A

    Wireguard Session Manager - Discussion (3rd) thread

    After changing to peer wg21 passthru add wg11 10.50.1.3/32 aa36:7ef1:2add:aa88:100::3/128 I still got the error - this may be as I separated IPv4 and IPv6 using a [space] rather than a , so I will delete, reboot and try again. UPDATE: changing to peer wg21 passthru add wg11...
  7. A

    Wireguard Session Manager - Discussion (3rd) thread

    if i want to add ipv4 and ipv6 for a device, can I add them together or one at a time - does it matter?
  8. A

    Wireguard Session Manager - Discussion (3rd) thread

    I removed pho21 and laptop from passthru (and the associated rules) but when I add I now get even though E:Option ==> 8 Peers (Auto start: Auto=P - Policy, Auto=S - Site-to-Site) Server Auto Subnet Port Annotate wg21 N...
  9. A

    Wireguard Session Manager - Discussion (3rd) thread

    if I run wgm I see where can I see wg_server ? After a reboot (wg11 is set to Policy Mode=P) and wg21 is not set to Auto ip rule 0: from all lookup local 9911: from 192.168.3.1 lookup 121 9991: from all fwmark 0x1000/0x1000 lookup 121 32766: from all lookup main 32767: from all...
  10. A

    Wireguard Session Manager - Discussion (3rd) thread

    just updated ip rule 0: from all lookup local 9810: from all fwmark 0xd2 lookup 210 9911: from 192.168.3.1 lookup 121 9981: from 10.50.1.1/24 lookup 121 9981: from 10.50.1.1/24 lookup 121 9981: from 10.50.1.1/24 lookup 121 9981: from 10.50.1.1/24 lookup 121 9981: from...
  11. A

    Wireguard Session Manager - Discussion (3rd) thread

    ...and we are back Also while rebuilding wg11.conf (adding the user defined DNS) I noted that it is now retaining the vpn IPv6 DNS Before [Interface] PrivateKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx= Address = <vpn_ipv4>/19, <vpn_ipv6>/64 DNS = <vpn_DNS4>, <vpn_DNS6> run After [Interface]...
  12. A

    Wireguard Session Manager - Discussion (3rd) thread

    Somewhere in the middle of adding, removing, modifying, etc I have manged to type the wrong command and SNAFU! Please bear with me while I remove and rebuild my server, client and devices. Normal service will be resumed....
  13. A

    Wireguard Session Manager - Discussion (3rd) thread

    The issue is on ipv4 and ipv6 and manually adding as above doesn't help (I edited as laptop is the second device) - the first (non-specified) device still gets sent through passthrough
  14. A

    Wireguard Session Manager - Discussion (3rd) thread

    Firstly, thank you and @ZebMcKayhan for bearing with me as I keep trying to see where I can break this. Passthru now works :), but not quite as expected :(- though given @ZebMcKayhan's comments on trying to cover all perms and comms this may well be a result of my particular setup (running...
  15. A

    Wireguard Session Manager - Discussion (3rd) thread

    I don't follow what it is that you 'would not consider this to be a bug' I can add all of wg11 or specific devices using the rules you provided and the 'road-warrior' devices work as expected (the only IPs and DNS they expose are those of the VPN provider). If I use the latest beta, this does...
  16. A

    Wireguard Session Manager - Discussion (3rd) thread

    @ZebMcKayhan I am assuming your comments above are directed at @Martineau, but it does remind me that I still need to check my road-warrior to LAN connectivity once passthru is setup - not an issue for my phone, but with a laptop I may want to RDP to another desktop on the lan. In theory I can...
  17. A

    Wireguard Session Manager - Discussion (3rd) thread

    passthru is not quite there, see above. Once it is done I have all I need for now, but happy to run more tests (family permitting) if you don't have any more dual stack volunteers.
  18. A

    Wireguard Session Manager - Discussion (3rd) thread

    I removed the rules from @ZebMcKayhan in #91, ran the update, restarted wg11, wg21 and the device on my phone; do I need to delete and re-create the latter? IPv4 is working, but IPv6 is showing the wg21 IPv6 addresses and DNS, not the wg11 (Azire) ones. start wg21 debug .... [#] ifconfig wg21...
  19. A

    Wireguard Session Manager - Discussion (3rd) thread

    Many thanks - works perfectly - I had added the outgoing (wg21 to VPN) rules, which did not work - adding the 'use main fixed it * IPv4 & IPv6 No DNS leaks No webrtc leaks (of IP) Diversion ad blocking working
View older results
Top