Add Bandwidth Limiting (Mbps) for Outgoing Traffic to Prevent Network Saturation

[zigazajc007]

Pangolin currently uses a VPN to tunnel traffic to user-defined destinations. While this is useful, it presents a potential risk when it comes to network saturation or DDoS scenarios. For example, if a site behind Pangolin is under attack and Pangolin is forwarding traffic at full speed (e.g., 1 Gbps), it can saturate the receiver’s internet connection — especially in home or small office environments.

Use Case:

In my case, I have a 1 Gbps home connection. If Pangolin forwards DDoS-level traffic at full speed to my site/network, it can completely overwhelm my connection, taking down all services. However, if there was an option to cap the maximum Mbps Pangolin can send to my site, I could mitigate the damage by setting a limit (e.g., 500 Mbps), ensuring that my network remains at least partially operational.

Proposed Feature:

Add a configuration option in web UI to limit the maximum bandwidth (in Mbps) Pangolin can send to a target.

Ideally, the limit should be configurable per resource (If not possible than per site).

Optional: support both upload and download bandwidth limits independently.

Benefits:

Helps protect small or residential networks from being overwhelmed.

Adds an extra layer of DDoS mitigation, even if the upstream VPS fails to mitigate.

Increases confidence in deploying Pangolin in environments with limited network resources.

Conclusion:

This feature would be a valuable enhancement to Pangolin, especially for users hosting services behind limited-capacity internet connections. It would make deployments more robust and resilient against unexpected traffic spikes or attacks.

[oschwartz10612]

Like the idea! Could be easy to implement I think.