[GH-ISSUE #299] extend plugin architecture to support dynamic route refresh loop #134

New issue

Open

opened 2026-03-04 01:35:03 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 01:35:03 +03:00

Owner

Originally created by @lts-rad on GitHub (Mar 21, 2024).
Original GitHub issue: https://github.com/spr-networks/super/issues/299

today SPR will dynamically refresh a route to a device since it can be connected to the network in several ways:

wired ethernet
wired ethernet VLAN
wifi
wireguard VPN

we can extend the plugin architecture so that plugins can also declare routes for devices

further more, we can extend device identity to include custom attributes from plugins also

together, this will let people connect devices to SPR in new ways without UI plugins needing to reinvent the wheel, so to speak.

One thing to get right is IP management. A VPN like tailscale uses CGNAT. don't want plugins breaking routing for everyone else or hijacking traffic heading upstream

Originally created by @lts-rad on GitHub (Mar 21, 2024). Original GitHub issue: https://github.com/spr-networks/super/issues/299 today SPR will dynamically refresh a route to a device since it can be connected to the network in several ways: - wired ethernet - wired ethernet VLAN - wifi - wireguard VPN we can extend the plugin architecture so that plugins can also declare routes for devices further more, we can extend device identity to include custom attributes from plugins also together, this will let people connect devices to SPR in new ways without UI plugins needing to reinvent the wheel, so to speak. One thing to get right is IP management. A VPN like tailscale uses CGNAT. don't want plugins breaking routing for everyone else or hijacking traffic heading upstream