[GH-ISSUE #2358] A functional appeal. #1875

New issue

Closed

opened 2026-05-05 13:12:47 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

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

Owner

Originally created by @SusuDOS on GitHub (Apr 16, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2358

A functional appeal: whether such a scenario can be considered. That is, computers a and B that have already run FRP clients need to use a to access B, but this function cannot be realized at present.
For example, a:

custom <-> visitor,this is a config of custom!

[common]
server_ addr = 43.248..
server_ port = 20514
token=0228bc66-23c6-4210-992c-ab5e1cb9
[p2p_ rdp]
type = stcp
sk = 329416525
local_ ip = 127.0.0.1
local_ port = 3389
For example, B:

custom <-> visitor,this is a config of custom!

[common]
server_ addr = 43.248..
server_ port = 20514
token=0228bc66-23c6-4210-992c-ab5e1cb9
[p2p_ rdp]
type = stcp
sk = 329416525
local_ ip = 127.0.0.1
local_ port = 3389
For example, a-visit:

custom <-> visitor,this is a config of visit

[common]
server_ addr = 43.248..
server_ port = 20514
token=0228bc66-23c6-4210-992c-ab5e1cb9
[rdp_ visitor]
type = stcp
role = visitor
server_ name = p2p_ rdp
sk = 329416
bind_ addr = 127.0.0.1
bind_ port = 13389
At this time, a will report an error.

Originally created by @SusuDOS on GitHub (Apr 16, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2358 A functional appeal: whether such a scenario can be considered. That is, computers a and B that have already run FRP clients need to use a to access B, but this function cannot be realized at present. For example, a: # custom <-> visitor,this is a config of custom! [common] server_ addr = 43.248.*.* server_ port = 20514 token=0228bc66-23c6-4210-992c-ab5e1cb9 [p2p_ rdp] type = stcp sk = 329416525 local_ ip = 127.0.0.1 local_ port = 3389 For example, B: # custom <-> visitor,this is a config of custom! [common] server_ addr = 43.248.*.* server_ port = 20514 token=0228bc66-23c6-4210-992c-ab5e1cb9 [p2p_ rdp] type = stcp sk = 329416525 local_ ip = 127.0.0.1 local_ port = 3389 For example, a-visit: # custom <-> visitor,this is a config of visit [common] server_ addr = 43.248.*.* server_ port = 20514 token=0228bc66-23c6-4210-992c-ab5e1cb9 [rdp_ visitor] type = stcp role = visitor server_ name = p2p_ rdp sk = 329416 bind_ addr = 127.0.0.1 bind_ port = 13389 At this time, a will report an error.

gitea-mirror

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

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:12:50 -06:00

Author

Owner

@SusuDOS commented on GitHub (Apr 16, 2021):

Using different service names can achieve similar functions, but it is possible that the service has the same name. Using different key values to judge the server name may be more user-friendly.

@SusuDOS commented on GitHub (Apr 16, 2021): Using different service names can achieve similar functions, but it is possible that the service has the same name. Using different key values to judge the server name may be more user-friendly.

gitea-mirror commented

2026-05-05 13:12:50 -06:00

Author

Owner

@fatedier commented on GitHub (Apr 21, 2021):

What's the feature do you want? Can you show me a example configures?

@fatedier commented on GitHub (Apr 21, 2021): What's the feature do you want? Can you show me a example configures?

gitea-mirror commented

2026-05-05 13:12:51 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 6, 2021):

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

@github-actions[bot] commented on GitHub (Jun 6, 2021): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.