mirror of
https://github.com/torlando-tech/pyxis.git
synced 2026-09-25 22:23:37 +00:00
torlando-techandClaude Opus 4.7
2504fefa66
Three changes, motivated by debugging "Sideband + pyxis on the same WiFi don't hear each other's announces": 1. Always call \`mld6_joingroup_netif()\` in addition to \`setsockopt IPV6_JOIN_GROUP\`. On ESP-IDF lwIP, the setsockopt path returns success but doesn't reliably push the multicast hash into the WiFi MAC filter — incoming multicast frames get silently dropped at L2. Calling the netif's mld6 API directly programs the chip filter. Joining twice on the netif is refcount-safe. 2. Set IPV6_MULTICAST_LOOP=1 so pyxis receives its own multicast echoes. ESP-IDF lwIP defaults this off, which makes upstream's "carrier lost / multicast echo timeout" warning fire even on a functioning network. With LOOP=1, the initial-echo path actually works on isolated test setups too. Logged as DEBUG if the platform doesn't support the option. 3. Add a periodic \`AutoInterface: stats announce_tx=N tx_fail=N disc_rx=N disc_self=N data_rx=N peers=N\` heartbeat (every 10s). Without this it's hard to tell whether pyxis isn't sending, isn't receiving, or is sending+receiving but rejecting the tokens. Discovery-RX from non-self addresses with bad tokens now also logs once with the hex prefix so token-mismatch cases are visible (group_id drift, scope-suffix encoding mismatches). Added _initial_echo_received update on first self-echo so the firewall warning at startup_grace fires correctly. After this, pyxis's own multicast loopback works (disc_self=N matches announce_tx=N within 10s). Cross-LAN multicast against rnsd / Sideband still doesn't make it through, which is an ESP32 WiFi multicast TX limitation — pyxis's frames aren't reaching the AP. Not a fix here; the diagnostics make the boundary visible. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Pyxis
An LXMF and LXST client firmware for T-Deck, built on a highly modified fork of microReticulum
Very much WIP, don't expect stability :)
Features
Reticulum transport over:
- RNode-compatible LoRa
- AutoInterface (local wifi)
- TCP Client
- BLE Interface (barely working if at all)
Other features:
- GPS-synced time
- One really annoying beep when you get a new message (user toggle)
- View the announce stream
- Choose a propagation node (and sync with it) (fixed in v0.2.1)
- Set auto announce timer
- Light up keyboard (user toggle)
Will crash in about 5 minutes of normal use (sorry)I had 5d uptime on v0.2.0 with BLE disabled- Make LXST voice calls (codec2 only, quality sounds horrible coming out the other end in Columba, needs work)
Why "Pyxis"
Pyxis, latin for "compass," is a constellation in the southern sky depicting a mariner's compass. Small but essential, the compass ensures every message finds its destination - even when the path is uncertain.