[GH-ISSUE #2203] 映射内网anydesk端口的小问题 #1753

Closed
opened 2026-05-05 13:07:45 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @jearol on GitHub (Jan 19, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2203

版本:0.34.1

客户端配置:
[common]
server_addr = ...
server_port = 7000
token = ******
pool_count = 16

[anydesk-10]
type = tcp
local_ip = 10.0.0.10
local_port = 7070
remote_port = 7070
use_encryption = false
use_compression = true

[anydesk-40]
type = tcp
local_ip = 10.0.0.40
local_port = 7080
remote_port = 7080
use_encryption = false
use_compression = true

服务端配置:
[common]
bind_port = 7000
token = *******
max_pool_count = 16
vhost_http_port = 8080
vhost_https_port = 4433

问题描述:
如果首次连接的是服务端7070端口的话,那么之后无论连接7070还是7080,则都连接到10.0.0.10:7070;
反之首次连接服务端7080端口的话,那么之后无论连接7070还是7080,则都连接到10.0.0.40:7080

没有具体测试多久可以重置连接,每次第二天首次连接的时候就决定了一天能连到.10的机器还是.40的机器
也不清楚是frp的问题还是anydesk的问题

Originally created by @jearol on GitHub (Jan 19, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2203 版本:0.34.1 客户端配置: [common] server_addr = *.*.*.* server_port = 7000 token = ****** pool_count = 16 [anydesk-10] type = tcp local_ip = 10.0.0.10 local_port = 7070 remote_port = 7070 use_encryption = false use_compression = true [anydesk-40] type = tcp local_ip = 10.0.0.40 local_port = 7080 remote_port = 7080 use_encryption = false use_compression = true 服务端配置: [common] bind_port = 7000 token = ******* max_pool_count = 16 vhost_http_port = 8080 vhost_https_port = 4433 问题描述: 如果首次连接的是服务端7070端口的话,那么之后无论连接7070还是7080,则都连接到10.0.0.10:7070; 反之首次连接服务端7080端口的话,那么之后无论连接7070还是7080,则都连接到10.0.0.40:7080 没有具体测试多久可以重置连接,每次第二天首次连接的时候就决定了一天能连到.10的机器还是.40的机器 也不清楚是frp的问题还是anydesk的问题
gitea-mirror 2026-05-05 13:07:45 -06:00
Author
Owner

@yuyulei commented on GitHub (Jan 20, 2021):

最好提供下 frpc,frps 的 debug 日志。

<!-- gh-comment-id:763346759 --> @yuyulei commented on GitHub (Jan 20, 2021): 最好提供下 frpc,frps 的 debug 日志。
Author
Owner

@github-actions[bot] commented on GitHub (Mar 7, 2021):

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

<!-- gh-comment-id:792143668 --> @github-actions[bot] commented on GitHub (Mar 7, 2021): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d 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#1753
No description provided.