general
- q
quiet-continent-24852
03/28/2022, 2:31 PMwe're about release v0.12.2 which will include netclient verbosity - q
quiet-continent-24852
03/28/2022, 2:32 PMbut for the time, no, sorry - s
straight-lock-3524
03/28/2022, 2:32 PM@User so the netmaker server probably runs behind nat yes? - f
few-airline-95046
03/28/2022, 2:32 PMYup 🙂 - s
straight-lock-3524
03/28/2022, 2:33 PMdoes it work if you try it with an internal client? - f
few-airline-95046
03/28/2022, 2:33 PMI've port forwarded 1883, 51821-51830 and 50051 to the netmaker VM btw. - s
straight-lock-3524
03/28/2022, 2:34 PMhmm - f
few-airline-95046
03/28/2022, 2:34 PMNope, that's what I tested recently. On a mac on my LAN 🙂 - b
bored-island-21407
03/28/2022, 3:25 PM@User are your server and clients on the same LAN? if so, when you create your network, set "Is Local Network "to on - f
few-airline-95046
03/28/2022, 4:17 PMI have tried connecting the node from WAN as well, but it did not matter, but I can try again, and also with a network with islocal 🙂 - f
few-airline-95046
03/28/2022, 4:25 PMhmm, created a new network and set it to islocal with my LAN range set. but joining the mac node only gets one interface in wg show - f
few-airline-95046
03/28/2022, 4:34 PMoh, looks like it worked when I created a new network, and joined from WAN using mobile hotspot....promising 😄 - m
mammoth-zoo-95458
03/28/2022, 7:07 PMThe endpoint IP doesn't seem to be updated in the node info when roaming, is this expected? To test the NAT traversal feature I disconnected my laptop from my home WIFI and joined my mobile hotspot WIFI. The IP is still the public IP from my home internet connection and I can't ping devices in my home LAN - b
bored-island-21407
03/28/2022, 7:09 PMit will take a little while for the endpoint change to be detected - m
mammoth-zoo-95458
03/28/2022, 7:11 PMthere is no way to force that update? Something like the opposite of netclient pull (push?) - b
bored-island-21407
03/28/2022, 7:12 PMused to be a push; no longer available - m
mammoth-zoo-95458
03/28/2022, 7:27 PMthe ip got updated at some point and NAT traversal seems to work great, thanks! - b
bored-island-21407
03/28/2022, 7:27 PMGreat! - m
mammoth-zoo-95458
03/28/2022, 7:29 PMare you planning to re-add the push feature at some point? - m
mammoth-zoo-95458
03/28/2022, 7:29 PMit would be nice to be able to force an update - b
bored-island-21407
03/28/2022, 7:35 PMit is not in the current plans; the check for public ip changes run once a minute -- it will take a few seconds for the update to propagate to all the other nodes but everything should happen within a couple of minutes - m
mammoth-zoo-95458
03/28/2022, 7:39 PMI see, thanks - m
mammoth-zoo-95458
03/28/2022, 8:34 PMdoes the 1883 port have to be exposed publicly? By default it looks like the contained install opens/exposes many ports to the host and docker adds the iptables rules to allow forwarding. According to the doc, only 80,443,51821-518XX/udp have to be publicly exposed. Is it still accurate or did something change with the latest versions? - f
few-airline-95046
03/28/2022, 8:35 PMUhm, is the access token supposed to be the same between between access keys? 🤔 - f
few-airline-95046
03/28/2022, 8:36 PMJust created a new access key, and it has the exact same access token as the access key I did before that - q
quiet-continent-24852
03/28/2022, 8:48 PMit shouldn't.. unless the key had the exact same name as well - f
few-airline-95046
03/28/2022, 8:50 PMit did not - m
mammoth-zoo-95458
03/28/2022, 8:54 PM@User to my understanding, ports other than 80/443/518XX should not be exposed to the host, right? Right now the docker containers expose 8081,8082,1883 to 0.0.0.0. But this could be avoided by using inter-container networking, no? - f
few-airline-95046
03/28/2022, 8:56 PMugh, nwm me, i'm blind...the access token wasn't identical... Time to go and sleep 😄 - q
quiet-continent-24852
03/28/2022, 8:57 PMyes, that would be more ideal, so long as your proxy is exposed to the host machine