rcourtman 573851a388 Fix temperature monitoring on standalone Proxmox nodes (addresses #571) ...

Root cause: The systemd service hardening blocked AF_NETLINK sockets,
preventing IP address discovery on standalone nodes. The proxy could
only discover hostnames, causing node_not_cluster_member rejections
when users configured Pulse with IP addresses.

Changes:
1. Add AF_NETLINK to RestrictAddressFamilies in all systemd services
   - pulse-sensor-proxy.service
   - install-sensor-proxy.sh (both modes)
   - pulse-sensor-cleanup.service

2. Replace shell-based 'ip addr' with Go native net.Interfaces() API
   - More reliable and doesn't require external commands
   - Works even with strict systemd restrictions
   - Properly filters loopback, link-local, and down interfaces

3. Improve error logging and user guidance
   - Warn when no IP addresses can be discovered
   - Provide clear instructions about allowed_nodes workaround
   - Include address counts in logs for debugging

This fix ensures standalone Proxmox nodes can properly validate
temperature requests by IP address without requiring manual
allowed_nodes configuration.

2025-11-13 13:02:15 +00:00

..

pulse-sensor-cleanup.path

feat: add automatic SSH key cleanup when nodes are removed

2025-10-18 07:03:05 +00:00

pulse-sensor-cleanup.service

Fix temperature monitoring on standalone Proxmox nodes (addresses #571)

2025-11-13 13:02:15 +00:00

pulse-update.service

Fix settings security tab navigation

2025-10-11 23:29:47 +00:00

pulse-update.timer

Fix settings security tab navigation

2025-10-11 23:29:47 +00:00