The unet CLI's join handler used the joiner's --network value as the
local network name, so an unspecified --network fell back to the
literal 'unet'. The inviter typically uses a different name (e.g.
ucoord_<venue>), so the two sides ended up keyed differently and any
upper layer subscribing to the network-named unetmsg channel never
saw each other.
The inviter now passes enroll_info={ network } to enroll_start so
the inviter's network name rides along in enroll_meta. The joiner
prefers data.enroll_meta?.network when present, falling back to its
own --network value for backwards compatibility with older inviters.
Signed-off-by: John Crispin <john@phrozen.org>
include $(TOPDIR)/rules.mk
PKG_NAME:=unetd
+PKG_RELEASE:=2
PKG_SOURCE_PROTO:=git
PKG_SOURCE_URL=$(PROJECT_GIT)/project/unetd.git
PKG_SOURCE_DATE:=2026-05-22
let req = {
network,
timeout: named.timeout,
+ enroll_info: { network },
};
if (named["access-key"]) {
function network_join_peer_update(model, ctx, msg)
{
let joinreq = ctx.data.enroll;
- let name = joinreq.name;
let data = network_handle_enroll_update(model, ctx, msg);
if (!data)
return;
+ let name = data.enroll_meta?.network ?? joinreq.name;
+
let iface = {
proto: "unet",
metric: joinreq.metric,