You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+86-1Lines changed: 86 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,7 +163,13 @@ Response:
163
163
164
164
#### 4. mDNS Service Discovery
165
165
166
-
Blox devices advertise both peerIDs via mDNS TXT records on the local network (service type `_fulatower._tcp`).
166
+
Blox devices advertise themselves on the local network via mDNS (multicast DNS), allowing mobile apps and other clients to discover devices without knowing their IP addresses.
167
+
168
+
**Service type:**`_fulatower._tcp`
169
+
170
+
**Instance naming:** Each device registers with a unique instance name derived from its kubo peerID: `fulatower_<last 5 chars of peerID>`. For example, a device with kubo peerID `12D3KooWAbCdEfGh12345` registers as `fulatower_12345`. If the peerID is not yet available (e.g. first boot before configuration), the device registers as `fulatower_NEW`. This ensures multiple blox devices on the same LAN are all discoverable without overwriting each other.
171
+
172
+
**TXT records:**
167
173
168
174
| TXT Key | Value | Description |
169
175
|---------|-------|-------------|
@@ -175,6 +181,85 @@ Blox devices advertise both peerIDs via mDNS TXT records on the local network (s
175
181
176
182
If the config file is missing or identity derivation fails, `bloxPeerIdString` falls back to reading from kubo's config file via `GetKuboPeerID()`. Fields default to `"NA"` when unavailable.
177
183
184
+
**Discovering devices from the command line:**
185
+
186
+
Using `dns-sd` (macOS):
187
+
```bash
188
+
dns-sd -B _fulatower._tcp local.
189
+
```
190
+
191
+
Example output:
192
+
```
193
+
Browsing for _fulatower._tcp.local.
194
+
DATE: ---Mon 17 Feb 2026---
195
+
Timestamp A/R Flags if Domain Service Type Instance Name
**Multi-device coexistence:** When multiple blox devices are on the same network, each registers with its own unique instance name. A browsing client will see all devices and can identify them by their TXT records (peerID, hardwareID, pool name). The service type `_fulatower._tcp` remains the same across all devices for compatibility — only the instance name varies.
262
+
178
263
#### 5. Go Code (`wifi.GetKuboPeerID()`)
179
264
180
265
For internal Go code that needs the kubo peerID, use the standalone utility function:
0 commit comments