Hi GRAVITL TEAM,
A quick query,
If my servers are...
# netmakerc
cool-army-24422
10/17/2022, 5:49 AMHi GRAVITL TEAM,
A quick query,
If my servers are already assigned with private IP while creation, and we are again bringing them into some other network through Netmaker. The PEERS are going into ERROR state.
Will this PRIVATE IP assignment when creation of server will give any issue like this?
[for example servers in
Hetzner Cloud, which is using WireGuard protocol as well for internal networking]
cool-army-24422
10/17/2022, 8:50 AM*Newly added to the network *
root@PRIVATE-IP-PEER:~# netclient pull -n test-net -vvvv
[netclient] 2022-10-17 08:45:57 [common.go-389] informPortChange(): network: test-net UDP hole punching enabled for node PRIVATE-IP-PEER
[netclient] 2022-10-17 08:46:00 [common.go-165] InitWireguard(): waiting for interface...
[netclient] 2022-10-17 08:46:00 [common.go-193] InitWireguard(): interface ready - netclient.. ENGAGE
[netclient] 2022-10-17 08:46:00 [commands.go-110] Pull(): pulled network config for test-net
[netclient] 2022-10-17 08:46:00 [commands.go-116] Pull(): reset network test-net and peer configs
Previously added to the network
root@VPN-PEER:~# netclient pull -n test-net -vvvv
[netclient] 2022-10-17 08:35:24 [common.go-415] informPortChange(): network: test-net UDP hole punching enabled for node VPN-PEER
[netclient] 2022-10-17 08:35:26 [common.go-165] InitWireguard(): waiting for interface...
[netclient] 2022-10-17 08:35:26 [common.go-193] InitWireguard(): interface ready - netclient.. ENGAGE
[netclient] 2022-10-17 08:35:26 [commands.go-113] Pull(): pulled network config for test-net
[netclient] 2022-10-17 08:35:26 [register.go-53] RegisterWithServer(): register at https://api.netmaker.###.dk:443/api/server/register
[netclient] 2022-10-17 08:35:26 [register.go-97] RegisterWithServer(): network: test-net certificates/key saved
[netclient] 2022-10-17 08:35:26 [commands.go-139] Pull(): reset network test-net and peer configs
cool-army-24422
10/17/2022, 8:50 AMHow to fix this issue?
cool-army-24422
10/17/2022, 9:35 AMAll the HEALTHY nodes are connected 3 weeks ago, and ERROR node today I added to the network.
seems like could not connect to broker
Is it netclient issue because other nodes are getting the updates from broker...initial 5 minutes everything is working fine
cool-army-24422
10/17/2022, 10:58 AMthe PEER is in error state but the handshake is still there.
*Sorry for flooding out with different observations 😌 *
j
jolly-london-20127
10/17/2022, 9:09 PMHi Abhishek, is the error node running 0.16.1? If you added today and freshly installed netclient on the server, this is likely the issue
c
cool-army-24422
10/18/2022, 4:18 AMis the error node running 0.16.1 -- No, Server is configured with 0.16.0
If you added today and freshly installed netclient on the server -- Yes
j
jolly-london-20127
10/20/2022, 1:14 PM@bored-solstice-58967
b
bored-solstice-58967
10/20/2022, 1:37 PMwhat is the version of the netclient you used on this node to join the network?
c
cool-army-24422
10/20/2022, 3:13 PMThanks @bored-solstice-58967 @jolly-london-20127 for the support.
Issue is because of different versions in netmaker and netclient.
j
jolly-london-20127
10/20/2022, 3:14 PMour fault for not making this release 0.17.0. The change really warrants a new version because of how incompatible it is with the older version
c
cool-army-24422
10/20/2022, 3:29 PMHi @jolly-london-20127
Is it possible somewhere we can mention this point and so that others should be aware.
It's only in UI node is shown as ERROR state but all the backend functionality is working smoothly.
j
jolly-london-20127
10/20/2022, 3:30 PMOn your netclient, when the version is wrong, you will get logs saying "client version mismatch", but agreed we should do this
jolly-london-20127
10/20/2022, 3:31 PM@curved-easter-21537 Please add a UI kitemaker item to make version show as Red in the UI if there is a mismatch, and a tooltips saying it's on the wrong version.
c
curved-easter-21537
10/20/2022, 3:32 PMok ill throw a ticket in for it
curved-easter-21537
10/20/2022, 3:32 PMto have