This error won't be fixed as the new Python/XML implementation of OpenVPN has been merged into current and will appear in the next rolling release.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 17 2019
Aug 16 2019
Maybe you could comment on this @zx2c4 ?
I think we should use it as a chance to improve it. The nesting does not do anyone any favors, tcpdump applies to all interface type, so a single level "monitor interface $intf" command is going to be easier to use.
Aug 15 2019
This is actually invalid. There is no way with the current CLI design to specify the local address node with an optional subnet-mask leaf node.
[e]ach network interface has a private key [...]
@hagbard It's not stated that you MUST use a new private key for each interface. But it states that
[e]ach network interface has a private key [...]
https://www.wireguard.com/#simple-network-interface ⇒ Cryptokey Routing
to set a private key for each interface only makes sense when you are allowed to use different keys for different interfaces. If there would be any withdraw in using multiple keys they would have just omitted the "privateKey" in the config file and set i globally. Since they didn't do that I can't imagine there is one. But I would be interested in learning what withdraws you see that the developers don't see.