-
Hello, Host1 tap0 is 192.168.0.1 What I don't understand is "how to make the system understand that all hosts collectively claim the 192.168.0.0 /24 subnet (or /16 /18 etc, we may expand the IP pool in the future)". In the config file the "claims" option seems to be reserved for a specific host to claim a specific subnet. In peerVPN (https://peervpn.net/tutorial/) this is done easily through the ifconfig4 command which takes a subnet: Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hi there, for this use case you need to use TAP mode (as your are doing right now). In this mode, VpnCloud does not care about IPs at all, it works on the level of MAC addresses and lets the Linux kernel do the IP stuff. |
Beta Was this translation helpful? Give feedback.
-
Perfect, many thanks. |
Beta Was this translation helpful? Give feedback.
Hi there,
for this use case you need to use TAP mode (as your are doing right now). In this mode, VpnCloud does not care about IPs at all, it works on the level of MAC addresses and lets the Linux kernel do the IP stuff.
The "claims" option in the config file is used in TUN mode and does not apply to your case.
You should be able to use TAP mode and configure your subnet using the "ip" option like this: "ip: 1192.168.0.1/24".