[GH-ISSUE #4225] Always uses maximum bandwidth #3330

Closed
opened 2026-05-05 14:08:52 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @lixeon on GitHub (May 19, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4225

Bug Description

FRP always uses maximum bandwidth, even when only an SSH port is open, causing slow connections.

frpc Version

v0.58.0

frps Version

v0.58.0

System Architecture

linux/amd64

Configurations

bindPort = 123
auth.token = "123"

Logs

nethogs

3025 root /var/www/frp/frps eth0 859.425 803.646 KB/sec

Steps to reproduce

...

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @lixeon on GitHub (May 19, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4225 ### Bug Description FRP always uses maximum bandwidth, even when only an SSH port is open, causing slow connections. ### frpc Version v0.58.0 ### frps Version v0.58.0 ### System Architecture linux/amd64 ### Configurations bindPort = 123 auth.token = "123" ### Logs # nethogs 3025 root /var/www/frp/frps eth0 859.425 803.646 KB/sec ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [X] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 14:08:52 -06:00
Author
Owner

@lixeon commented on GitHub (May 19, 2024):

the client back to v0.51.3, issue fixed.

893586 root /var/www/frp/frpc enp97s 0.307 0.136 KB/se

<!-- gh-comment-id:2119049542 --> @lixeon commented on GitHub (May 19, 2024): the client back to v0.51.3, issue fixed. 893586 root /var/www/frp/frpc enp97s 0.307 0.136 KB/se
Author
Owner

@github-actions[bot] commented on GitHub (Jun 10, 2024):

Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

<!-- gh-comment-id:2156930054 --> @github-actions[bot] commented on GitHub (Jun 10, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#3330
No description provided.