Title
a
ambitious-gold-80784
12/01/2022, 12:23 AMis it possible to have certain netmaker clients connect via their local network interface but still use public IP's for other clients?
j
jolly-london-20127
12/01/2022, 1:26 AMThat’s how it works at the moment but is not very sophisticated. It will check to see if another client shares a public IP and if so, use the local address
a
ambitious-gold-80784
12/01/2022, 12:20 PMah I see so it will check if the client has a shared public IP between them and try the local? that makes sense
I had some compute instances running in the cloud with separate public IP's but wanted them to connect to their local peers in the same VPC via the local interface. It would still need to use the public IP for other clients outside the VPC though
j
jolly-london-20127
12/01/2022, 1:06 PMYes I see, in that case it would not use a local connection currently. If you have any suggestions on how to implement, we're planning to refactor the way local connections work in the coming weeks!
a
ambitious-gold-80784
12/01/2022, 1:50 PMI think checking if the local address is in the same subnet as other clients local address could be something to look into for the refactor
j
jolly-london-20127
12/01/2022, 1:59 PMthat's sort of our idea. In general we plan to:
1. collect all interfaces on each device
2. check on each device if there is a matching subnet
3. test if the peer is reachable over that subnet
The issue is mostly, if you have several reachable interfaces on a device, which one to use? Right now we're thinking do a simple latency test and do the lowest latency.
a
ambitious-gold-80784
12/01/2022, 2:02 PMthat makes sense to me. Good point about multiple interfaces, might be worth having a config option to specify which interface to use for local connections to deal with those cases with multiple options