Open osevan opened 1 month ago
I may be wrong, but this behaviour actually makes sense.
AllowedIPs is a client setting, it basically tells to the host machine "whenever you have a request for IP X, route it through the Peer Y"
The tool is creating a mesh, when you add a peer, you are not saying "Add a config file" you are saying "This is a peer for this mesh".
When you add AllowedIPs
you are not saying "Add those AllowedIPs
to this file", but you are saying "This peer routes the following IPs, so each peer should forward those requests to it".
Another way of looking at it would be: wg-meshconf add peer rack119 with IP 10.1.0.1/16, which owns and is capable of routing 10.1.0.1/16, 10.2.0.1/16, 10.10.21.1/16, so each peer should send rack119 the requests to those IPs.
you can see in your command line logic existing bugs. you need to execute this line with allowedips inside rack119.conf file instead in rack75.conf, because command above is right i did...
Same for addpeer command both "updatepeer and addpeer" placing allowedips in wrong configs
Thank you very much for wg-mesher.
It works great except this issue with wrong --allowedips line in wrong config
Thanks and Best regards