[GH-ISSUE #2940] [Feature Request] Dashboard里希望支持显示frpc的内网地址和转发的服务器地址

gitea-mirror commented

2026-05-05 13:30:44 -06:00

Owner

Copy link

Originally created by @mbj2014 on GitHub (May 16, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2940

Describe the feature request

frps仅通过密码来管理接入，无法真正识别接入者。

在Dashboard里，只能看到标签信息，但没有frpc的内网服务器地址和转发服务地址。

如果可以在每个标签的信息里，可以显示frpc的内网服务器地址、机器名、MAC和转发服务地址等信息，就容易在Dashboard里看到接入者是什么机器了。

Describe alternatives you've considered

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @mbj2014 on GitHub (May 16, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/2940 ### Describe the feature request frps仅通过密码来管理接入，无法真正识别接入者。在Dashboard里，只能看到标签信息，但没有frpc的内网服务器地址和转发服务地址。如果可以在每个标签的信息里，可以显示frpc的内网服务器地址、机器名、MAC和转发服务地址等信息，就容易在Dashboard里看到接入者是什么机器了。 ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:30:44 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:30:47 -06:00

Author

Owner

Copy link

@MooreFoss commented on GitHub (May 20, 2022):

同意

@MooreFoss commented on GitHub (May 20, 2022): 同意

gitea-mirror commented

2026-05-05 13:30:47 -06:00

Author

Owner

Copy link

@chijiao commented on GitHub (May 29, 2022):

应该可以自己编译增加功能吧

@chijiao commented on GitHub (May 29, 2022): 应该可以自己编译增加功能吧

gitea-mirror commented

2026-05-05 13:30:48 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jun 29, 2022):

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

@github-actions[bot] commented on GitHub (Jun 29, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified