https://netmaker.org logo
Hello, I had 17.1 running for a few months pretty well and i'm having issues with 18.5, this is a Linux standard deployment with docker compose, NOT in K8S, yet I intend to use Netmaker as the network link between my different sites. Everything works well, then whenever I start K3S (flanel CNI) it brings up a new NIC, which somehow gets picked up by netclient with : "determined new endpoint for peer" then as the IP you have the K8S node / Flanel IP 10.42.0.X , which then breaks wireguard/netclient/connectivity. I did not have this issue in 0.17.1 Any way to disable this "determined new endepoint" feature ? (it's already supposed to be static in the host property) or am I looking the wrong way ?
h

handsome-branch-95683

04/11/2023, 5:20 PM
Hello, I had 17.1 running for a few months pretty well and i'm having issues with 18.5, this is a Linux standard deployment with docker compose, NOT in K8S, yet I intend to use Netmaker as the network link between my different sites. Everything works well, then whenever I start K3S (flanel CNI) it brings up a new NIC, which somehow gets picked up by netclient with : "determined new endpoint for peer" then as the IP you have the K8S node / Flanel IP 10.42.0.X , which then breaks wireguard/netclient/connectivity. I did not have this issue in 0.17.1 Any way to disable this "determined new endepoint" feature ? (it's already supposed to be static in the host property) or am I looking the wrong way ?