3 ms·
I think there's some issues in the config. First of all, at least one of the CIDRs is wrong ("Address = 10.200.200.2/24"). Also by setting AllowedIPs to to 10.2
by 3fe9a03ccd14ca5 7y ago
I think there's some issues in the config. First of all, at least one of the CIDRs is wrong ("Address = 10.200.200.2/24"). Also by setting AllowedIPs to to 10.200.200.0/24 in the client, only traffic to that subnet will actually go through the VPN, not all traffic.
Isn't there also some missing host/RPI system so that the 10.200.200.0/24 can route to the public internet?
If someone has an example of a full VPN configuration I'd love to see them so I can try it out.
- nucleardog 7y ago> First of all, at least one of the CIDRs is wrong ("Address = 10.200.200.2/24"). Also by setting AllowedIPs to to 10.200.200.0/24 in the client, only traffic to that subnet will actually go through the VPN, not all traffic. Not sure what your issue is with the address line. As for the AllowedIPs, that's intentional. From the first lines of the article: > An Linux Laptop that should use the VPN only accessing network services that are exposed to the VPN VPNs aren't just for routing your public traffic through some trusted host.
- 3fe9a03ccd14ca5 7y agoIs 10.200.200.2/24 a valid cidr? Does the system just ignore the trailing 2 and assume it’s a 0?
- jlgaddis 7y ago10.200.200.2/24 is a shorthand form (a.k.a. "CIDR notation") of saying IP address 10.200.200.2 with a 24-bit subnet mask (255.255.255.0).