Closed bmullan closed 4 years ago
In my view, what you are calling end-points are what the industry calls VxLAN Virtual Tunnel End Points or VTEP
Actually the "endpoint" here is the Wireguard endpoint, not VTEP. VTEP is automatically assigned by the program from a pool. (In fact, VTEP address is chosen from the 169.254.0.0/16 block by default, to deliberately disallow routing on this layer.)
The reason I choose "endpoint" is to maintain CLI-similarity with Wireguard's official tools.
This is related to the Closed Issue #8 that you've already corrected: https://github.com/m13253/VxWireguard-Generator/issues/8
In the current VxWireguard-Generator README there are examples of the vwgen command to set what you call "endpoints" in the examples:
In my view, what you are calling end-points are what the industry calls VxLAN Virtual Tunnel End Points or VTEP
You previously corrected this for the command vwgen showconf output to correctly identify the VTEP IP of a Node's VxLAN connection.
I'd like to suggest changing the "vwgen set" command syntax to use something like "VTEP" or "VTEP_IP" instead of the term "endpoint" to enhance the consistancy of the syntax. This would make sure that the person installing/configuring things understands that the command is configuring the VxLAN Virtual Tunnel End Poiont (VTEP) of that Node's VxLAN tunnel.