[Suggestion] Suggestion to Support TCP/UDP Port Forwarding and Protection

What would you like to be added or improved?

1. Support TCP/UDP port forwarding (public port → internal IP/port).
2. Apply basic security policies for TCP/UDP traffic:
   • IP whitelist/blacklist
   • Connection limits
   • Rate limiting (to prevent brute-force attacks or DDoS)
3. Integrate with Safeline’s existing IP blocking mechanism to enable cross-protocol blocking.
4. Provide a web-based interface for configuring TCP/UDP rules with batch management capabilities.

Why is it needed?

Currently, Safeline only supports HTTP/HTTPS traffic forwarding and protection.
For TCP/UDP services (e.g., SSH, MySQL, Redis, game servers, custom APIs), there is no native support.
Some competitors, such as BT (BaoTa) WAF, already provide TCP/UDP port forwarding capabilities, allowing users to manage both HTTP and non-HTTP traffic from a single interface.
If Safeline could also support TCP/UDP forwarding, it would greatly improve unified management and security control for all types of network traffic.

Start by mapping SafeLine’s existing HTTP/HTTPS forwarding and protection paths, then trace how its IP blocking mechanism is integrated. This issue is broad design work: done would require a decided scope and implementation plan covering TCP/UDP forwarding, traffic policies, cross-protocol blocking, and web-based batch rule management.