Skip to content

Remove .local / Avahi support#15

Open
VijitSingh97 wants to merge 1 commit into
mainfrom
chore/remove-avahi-local
Open

Remove .local / Avahi support#15
VijitSingh97 wants to merge 1 commit into
mainfrom
chore/remove-avahi-local

Conversation

@VijitSingh97
Copy link
Copy Markdown
Contributor

Why

mDNS/.local resolution is a LAN-only convenience: it only works when the worker rig and the pool/stack host share a single broadcast domain, and it silently fails (or resolves to the wrong host) on routed networks, VPNs, or anything beyond one subnet. It also pulls in the Avahi daemon as a build/runtime dependency for every install.

What changed

  • rigforge.sh
    • Removed the "smart address handling" block that appended .local to short hostnames. The configured P2POOL_NODE_HOSTNAME is now used as-is.
    • Dropped the avahi-daemon (apt), avahi (dnf), and avahi (pacman) packages from the dependency install lists.
  • README.md
    • Updated the hostname guidance: the pool/stack host must be an IP or a DNS-resolvable hostname (for a stable LAN address, set a DHCP reservation or static IP).

Verification

  • shellcheck rigforge.sh introduces no new findings (the two pre-existing info-level notes on main are unchanged).
  • grep -rin 'avahi\|mdns\|\.local' rigforge.sh README.md returns nothing.

Closes #14

🤖 Generated with Claude Code

Drop mDNS/.local hostname resolution: it only helps on a single LAN
segment and silently fails elsewhere. The pool/stack host should be an
IP or DNS-resolvable hostname instead. Removes the .local-appending
'smart address handling' and the avahi packages from the dependency
install lists (apt/dnf/pacman).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove .local / Avahi support (connect by IP or DNS hostname)

1 participant