I m strongly considering downgrading to
# netmakerl
loud-planet-71485
04/04/2023, 9:28 AMI'm strongly considering downgrading to v0.17 on the server and manually installing netclient (https://apt.netmaker.org/pool/main/) and removing the source from APT
j
jolly-london-20127
04/04/2023, 9:46 AMare you able to share some information on the ipv6 addresses? we have a hotfix coming today for the "local endpoint detection" but not sure if it will solve your issue
jolly-london-20127
04/04/2023, 9:47 AMhow it's supposed to work is:
- clients report their local addresses to the server
- server sends local addresses for peers to clients
- peers attempt to ping the local addresses for other peers, and then choose the fastest successful connection
l
loud-planet-71485
04/04/2023, 10:19 AMRe IPv6: unfortunately not, I've already downgraded server and clients
loud-planet-71485
04/04/2023, 10:20 AMBut per a ipinfo.io lookup, those were all bogon IPs
loud-planet-71485
04/04/2023, 10:21 AMthe other issue was that clients were connecting to each other on port 51821, which was not dynamic and would not change after a netclient restart
j
jolly-london-20127
04/04/2023, 10:22 AMthe netclient should only be using addresses sent to the server by the clients. Can you check to see if the bogon ip address is attached to an interface on the relevant client?
l
loud-planet-71485
04/04/2023, 10:22 AMinterface name on clients also went from
nm-<network_name>netmakerloud-planet-71485
04/04/2023, 10:22 AMit could be a v6 address on other interfaces
loud-planet-71485
04/04/2023, 10:22 AMyes
loud-planet-71485
04/04/2023, 10:24 AMhmm yeah it could be the tailscale v6 address
j
jolly-london-20127
04/04/2023, 10:31 AMdo you know if you're using the latest clients? we actually deployed a hotfixed binary yesterday that should have made the ipv6 stuff a bit less problematic
jolly-london-20127
04/04/2023, 10:33 AMRE your other issues; there is supposed to be just 1 interface now called "netmaker"; it contains peers for all networks. And the "dynamic port" bit was modified in favor of a STUN implementation which uses a static port. So the client should always uses either 51821 (pure wireguard) or 51722 (proxy).
l
loud-planet-71485
04/04/2023, 10:40 AMthat's a deal breaker for me unfortunately... I've observed behavior where changing the port increases throughput significantly... I do not know why
j
jolly-london-20127
04/04/2023, 10:42 AMyou should be able to manually change the port in the UI, it just won't randomly select a port
jolly-london-20127
04/04/2023, 11:18 AMi dont suppose you checked the netclient version ("sudo netclient version"). The hotfix was given the version v0.18.5.2, but the client may have automatically reverted to v0.18.5, since the version was different from the server