So I coulnd t keep my fingers from
# client
f
So I coulnd't keep my fingers from upgrading from 0.17.1 to 0.18.3... Upgrade went fine but all nodes was removed (not sure if that's intentional?). Anywho, no issue to just add them again with the latest netclient. in 0.17.1 I had disabled dynamic ports on some of the nodes. But when trying to set a specific listening port on a node, I find no way to disable dynamic endpoint... How do I do this now? 😄
j
Oof yeah...we're still working out the upgrade logic. So, old clients will not show up in the UI until they are upgraded locally.
As far as port management goes, you'll notice a new section for "Hosts"
This represents the client across all networks. You only have one interface now for all networks, so port management is at the Host level.
The main benefit of the hosts construct is we can now add and remove machines from networks via UI/API/CLI. The machine just has to be registered with the server, and you can control which networks it is in.
f
Alright, so changing the port in the host section should "disable" the dynamic port switch?
j
it should, if not we've got a bug to fix in the new version
f
I think I'll start from scratch... the old nodes seem to be lurking in netmaker, but not showing anywhere. I haven't managed to get the nodes to just start working after upgrading to the 0.18.3 netclient, but had to join again... maybe that's why I'm having issues? Btw, If I was to upgrade from 0.18.3 -> 0.18.4... would that be a simple adjustment in the docker-compose.yml? I'm guessing the nm-upgrade.sh is only meant for upgrading from 0.17?
j
Yeah the script is just for 17 to 18
Yeah the script is just for 17 to 18
f
Alright! I'll start fresh and let you know if changing the node port works 🙂
Hmm... started fresh and cannot get any node to work... is there new ports that needs to be enabled in iptables for the netmaker server?