Dave Cottlehuber

I'm interested to know what the use case here is - what is missing from the current setup where IPs are pushed down to zt, that people want to use...

Interesting but what’s the use case? Can you clarify how having a qrcode would be used in practice during a server or laptop boot sequence?

changing existing API is hard, but perhaps its possible to add an additional API that addresses this.

No, there's no error messages that I see running a `gmake -j debug` flavoured build. This only occurs on FreeBSD ofc. I'll throw some printfs in and see what happens....

ok I think we can see why the auth fails :D but do the numbers here mean anything to you? if (remoteAddr.ipScope() == InetAddress::IP_SCOPE_LOOPBACK) { ``` zt1flo98dm17np8 authCheck: /status remoteAddr.ipScope()...

ifconfig output if that's relevant ``` lo0: flags=1008049 metric 0 mtu 16384 options=680003 inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 groups: lo nd6...

interesting: ``` $ doas ngrep -qid lo0 -W byline port 9993 interface: lo0 (127.0.0.0/255.0.0.0) filter: (ip or ip6) and ( port 9993 ) T 127.0.0.1:10178 -> 127.0.0.1:9993 [AP] GET /status...

That specific pattern didn't work, in the end I used `::` and rely on the per-node authsecret and local firewall rules for security. Is that sufficient? It's certainly not ideal...

This basically broke new zerotier installs on all FreeBSD and TrueNAS systems, you can't add nodes unless find this issue. Any chance this could get addressed for [1.14](https://github.com/zerotier/ZeroTierOne/milestone/6)? The fix...

OK it aint pretty, but it *does* fix the issue... over to you c++ gurus to make it pretty/correct: ```diff diff --git a/node/InetAddress.cpp b/node/InetAddress.cpp index da1c7294..7a786e49 100644 --- a/node/InetAddress.cpp +++...