Not sure how iptable handles the wireguard to wireguard traffic but this single rule covers ALL what I would call RELAY traffic through the VPS, both wireguard and subnet!! If you do end up using other subnets across routers, then the below rule also covers that.Īdd action=accept chain=forward in-interface=WG-interface out-interface=WG-interface (2) I dont see any allowance for any of the routers using WG to reach subnets on other routers other than via wireguard IP. The only comment I would make is ensure the single peer on the local Routers, to the VPS uses the nomenclature for wireguard as follows: 10.66.66.0/24. (1) Looking at the VPS it is seemingly configured properly as a WG Server for the initial handshake.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |