[GH-ISSUE #58] 🚩 Make container networks a building block on SPR #14

New issue

Closed

opened 2026-03-04 01:34:07 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 01:34:07 +03:00

Owner

Originally created by @lts-rad on GitHub (Sep 2, 2022).
Original GitHub issue: https://github.com/spr-networks/super/issues/58

Problem to solve

Container networks are currently poorly supported on SPR. As a workaround, users have to add rules to allow docker to do its thing or default to the "bridge" (docker0) network.

# Custom docker network workaround
nft insert rule inet filter FORWARD iifname "br*" accept
nft insert rule inet filter INPUT iifname "br*" accept

Feature: Support container network firewall rules & connectivity

Users can define rules for what the container should be able to access. LAN, WAN, LAN_UPSTREAM?, DNS, or specific device groups on the network.

We can listen to docker events and when a network is created or connected-to, its network is registered with SPR and managed.

Feature: Containers as a network sinks

Containers can run Tor, VPNs, and network experiments. We should make it possible to make a container a network sink similar to Site VPN forwarding, or possibly even a network relay where traffic comes back out onto the network after passing through the container.

Originally created by @lts-rad on GitHub (Sep 2, 2022). Original GitHub issue: https://github.com/spr-networks/super/issues/58 ## Problem to solve Container networks are currently poorly supported on SPR. As a workaround, users have to add rules to allow docker to do its thing or default to the "bridge" (docker0) network. ``` # Custom docker network workaround nft insert rule inet filter FORWARD iifname "br*" accept nft insert rule inet filter INPUT iifname "br*" accept ``` ## Feature: Support container network firewall rules & connectivity Users can define rules for what the container should be able to access. LAN, WAN, LAN_UPSTREAM?, DNS, or specific device groups on the network. We can listen to docker events and when a network is created or connected-to, its network is registered with SPR and managed. ## Feature: Containers as a network sinks Containers can run Tor, VPNs, and network experiments. We should make it possible to make a container a network sink similar to Site VPN forwarding, or possibly even a network relay where traffic comes back out onto the network after passing through the container.