tapdev
.Yes, I now think the same. =)
Sorry, but I didn't implement this logic at begin (if tapdev
).
I have not time to figure it out and not break anything. Could you make a repatch yourself with the necessary conditions please?
Add somethink like
if (!tapdev) {
if (!ip4config && !ip6config) helper_failed (proxy, "IPv4 or IPv6 configuration");
}
Yes, in our case it works (the network is about 100 nodes). We configuring an IP configuration of this NM OpenVPN connection like a normal Ethernet connection (dhcp, static, routes, dns, etc).
I'm not 100% sure. But I think it might work correctly. Because, according to my idea, NetworkManager
no longer implement any special logic for the created tap-device
and works with it as with a standard ethernet-device
(i hope).
Sometimes OpenVPN servers are configured as ethernet-only virtual networks (ethernet bridging over tap). This reduces the requirement to negotiate between the client and redirected networks, allowing the client to configure his tap network interface as flexibly as it configures it by physically connecting to it (eg, eth0). It is also possible that the client does not need an ip-address and/or an ip-protocol.
p5-vbnekit (72f2ee1c) at 16 Sep 12:32
Added more flexibility for ethernet-bridges.