github-starred/frp
2
0
Fork 0
mirror of https://github.com/fatedier/frp.git synced 2026-05-15 08:05:49 -06:00
Code Issues 40 Projects Packages Wiki Activity Actions 1

[GH-ISSUE #3972] RDP远程桌面无法连接，tls的clint hello报文没有被转发 #3149

New issue
Closed
opened 2026-05-05 14:02:19 -06:00 by gitea-mirror · 11 comments
gitea-mirror commented 2026-05-05 14:02:19 -06:00
Owner
Copy link

Originally created by @Loyolichoo on GitHub (Feb 2, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/3972

Bug Description

配置转发本地7501（frpc的webServer端口），然后远程访问是可以正常打开的。但是转发本地3389端口的时候，就会卡在无限连接上。于是对本地的loopback网口进行了抓包，同时在服务器的远程口进行抓包。发现在转发过程中，服务器抓到的tls的Client Hello报文并没有在本地的loopback网口抓到。请教一下接下来该如何继续进行定位。
原始报文：
image
本地回环抓到的报文：
image

frpc Version

0.54.0

frps Version

0.54.0

System Architecture

linux/amd64, windows/amd64

Configurations

frpc:

serverAddr = "*"
serverPort = 7801
transport.protocol = "quic"
log.to = "frpc.log"
log.level = "trace"
log.maxDays = 30
auth.token = "*"
webServer.port = 7501

[[proxies]]
name = "RDP-TCP"
type = "tcp"
#localIP = "127.0.0.1"
localPort = 3389
remotePort = 13389

[[proxies]]
name = "RDP-UDP"
type = "udp"
#localIP = "127.0.0.1"
localPort = 3389
remotePort = 13389

frps:

bindPort = 7801
quicBindPort = 7801
log.to = "frps.log"
log.level = "trace"
log.maxDays = 30
auth.token = "*"

Logs

frps:

2024/02/03 01:32:09 [I] [root.go:105] frps uses config file: /home/lc/opt/etc/frp/frps_3389.toml
2024/02/03 01:32:09 [I] [service.go:225] frps tcp listen on 0.0.0.0:7801
2024/02/03 01:32:09 [I] [service.go:249] frps quic listen on 0.0.0.0:7801
2024/02/03 01:32:09 [I] [root.go:114] frps started successfully
2024/02/03 01:32:13 [I] [service.go:563] [19065ba0f1dea30e] client login info: ip [111.201.29.102:9234] version [0.54.0] hostname [] os [windows] arch [amd64]
2024/02/03 01:32:13 [D] [control.go:432] [19065ba0f1dea30e] receive heartbeat
2024/02/03 01:32:13 [I] [udp.go:103] [19065ba0f1dea30e] [RDP-UDP] udp proxy listen port [13389]
2024/02/03 01:32:13 [I] [control.go:401] [19065ba0f1dea30e] new proxy [RDP-UDP] type [udp] success
2024/02/03 01:32:13 [I] [tcp.go:82] [19065ba0f1dea30e] [RDP-TCP] tcp proxy listen port [13389]
2024/02/03 01:32:13 [I] [control.go:401] [19065ba0f1dea30e] new proxy [RDP-TCP] type [tcp] success
2024/02/03 01:32:13 [D] [control.go:243] [19065ba0f1dea30e] new work connection registered
2024/02/03 01:32:14 [D] [control.go:272] [19065ba0f1dea30e] get work connection from pool
2024/02/03 01:32:14 [D] [proxy.go:131] [19065ba0f1dea30e] [RDP-UDP] get a new work connection: [111.201.29.102:9234]
2024/02/03 01:32:14 [T] [udp.go:117] [19065ba0f1dea30e] [RDP-UDP] loop waiting message from udp workConn
2024/02/03 01:32:14 [D] [control.go:243] [19065ba0f1dea30e] new work connection registered
2024/02/03 01:32:18 [I] [proxy.go:204] [19065ba0f1dea30e] [RDP-TCP] get a user connection [111.201.29.102:9247]
2024/02/03 01:32:18 [D] [control.go:272] [19065ba0f1dea30e] get work connection from pool
2024/02/03 01:32:18 [D] [proxy.go:131] [19065ba0f1dea30e] [RDP-TCP] get a new work connection: [111.201.29.102:9234]
2024/02/03 01:32:18 [T] [proxy.go:240] [19065ba0f1dea30e] [RDP-TCP] handler user tcp connection, use_encryption: false, use_compression: false
2024/02/03 01:32:18 [D] [proxy.go:261] [19065ba0f1dea30e] [RDP-TCP] join connections, workConn(l[10.0.16.4:7801] r[111.201.29.102:9234]) userConn(l[10.0.16.4:13389] r[111.201.29.102:9247])
2024/02/03 01:32:18 [D] [control.go:243] [19065ba0f1dea30e] new work connection registered
2024/02/03 01:32:29 [D] [proxy.go:271] [19065ba0f1dea30e] [RDP-TCP] join connections closed

frpc:

2024/02/03 01:32:14 [I] [root.go:142] start frpc service for config file [.\frpc_3389.toml]
2024/02/03 01:32:14 [I] [service.go:287] try to connect to server...
2024/02/03 01:32:14 [I] [service.go:279] [19065ba0f1dea30e] login to server success, get run id [19065ba0f1dea30e]
2024/02/03 01:32:14 [D] [control.go:244] [19065ba0f1dea30e] send heartbeat to server
2024/02/03 01:32:14 [I] [proxy_manager.go:173] [19065ba0f1dea30e] proxy added: [RDP-TCP RDP-UDP]
2024/02/03 01:32:14 [I] [service.go:177] admin server listen on 127.0.0.1:7501
2024/02/03 01:32:14 [T] [proxy_wrapper.go:200] [19065ba0f1dea30e] [RDP-UDP] change status from [new] to [wait start]
2024/02/03 01:32:14 [T] [proxy_wrapper.go:200] [19065ba0f1dea30e] [RDP-TCP] change status from [new] to [wait start]
2024/02/03 01:32:14 [D] [control.go:195] [19065ba0f1dea30e] receive heartbeat from server
2024/02/03 01:32:14 [I] [control.go:170] [19065ba0f1dea30e] [RDP-UDP] start proxy success
2024/02/03 01:32:14 [I] [control.go:170] [19065ba0f1dea30e] [RDP-TCP] start proxy success
2024/02/03 01:32:14 [D] [proxy_wrapper.go:260] [19065ba0f1dea30e] [RDP-UDP] start a new work connection, localAddr: [::]:50090 remoteAddr: *:7801
2024/02/03 01:32:14 [I] [udp.go:93] [19065ba0f1dea30e] [RDP-UDP] incoming a new work connection for udp proxy, *:7801
2024/02/03 01:32:19 [D] [proxy_wrapper.go:260] [19065ba0f1dea30e] [RDP-TCP] start a new work connection, localAddr: [::]:50090 remoteAddr: *:7801
2024/02/03 01:32:19 [T] [proxy.go:144] [19065ba0f1dea30e] [RDP-TCP] handle tcp work connection, useEncryption: false, useCompression: false
2024/02/03 01:32:19 [D] [proxy.go:208] [19065ba0f1dea30e] [RDP-TCP] join connections, localConn(l[127.0.0.1:12733] r[127.0.0.1:3389]) workConn(l[[::]:50090] r[*:7801])
2024/02/03 01:32:29 [D] [proxy.go:220] [19065ba0f1dea30e] [RDP-TCP] join connections closed
2024/02/03 01:32:29 [T] [proxy.go:222] [19065ba0f1dea30e] [RDP-TCP] join connections errors: [read tcp 127.0.0.1:12733->127.0.0.1:3389: use of closed network connection]
2024/02/03 01:32:44 [D] [control.go:244] [19065ba0f1dea30e] send heartbeat to server
2024/02/03 01:32:44 [D] [control.go:195] [19065ba0f1dea30e] receive heartbeat from server
2024/02/03 01:32:44 [T] [udp.go:150] [19065ba0f1dea30e] [RDP-UDP] send ping message to udp workConn
2024/02/03 01:33:14 [D] [control.go:244] [19065ba0f1dea30e] send heartbeat to server
2024/02/03 01:33:14 [D] [control.go:195] [19065ba0f1dea30e] receive heartbeat from server
2024/02/03 01:33:14 [T] [udp.go:150] [19065ba0f1dea30e] [RDP-UDP] send ping message to udp workConn
2024/02/03 01:33:44 [D] [control.go:244] [19065ba0f1dea30e] send heartbeat to server
2024/02/03 01:33:44 [D] [control.go:195] [19065ba0f1dea30e] receive heartbeat from server
2024/02/03 01:33:44 [T] [udp.go:150] [19065ba0f1dea30e] [RDP-UDP] send ping message to udp workConn

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 @Loyolichoo on GitHub (Feb 2, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/3972 ### Bug Description 配置转发本地7501（frpc的webServer端口），然后远程访问是可以正常打开的。但是转发本地3389端口的时候，就会卡在无限连接上。于是对本地的loopback网口进行了抓包，同时在服务器的远程口进行抓包。发现在转发过程中，服务器抓到的tls的Client Hello报文并没有在本地的loopback网口抓到。请教一下接下来该如何继续进行定位。 原始报文： ![image](https://github.com/fatedier/frp/assets/18119338/dee69281-1091-405e-92d0-3293561d7895) 本地回环抓到的报文： ![image](https://github.com/fatedier/frp/assets/18119338/a953d50b-dfb0-4f2b-a91b-b9d6f61fbc68) ### frpc Version 0.54.0 ### frps Version 0.54.0 ### System Architecture linux/amd64, windows/amd64 ### Configurations frpc: ``` serverAddr = "*" serverPort = 7801 transport.protocol = "quic" log.to = "frpc.log" log.level = "trace" log.maxDays = 30 auth.token = "*" webServer.port = 7501 [[proxies]] name = "RDP-TCP" type = "tcp" #localIP = "127.0.0.1" localPort = 3389 remotePort = 13389 [[proxies]] name = "RDP-UDP" type = "udp" #localIP = "127.0.0.1" localPort = 3389 remotePort = 13389 ``` frps: ``` bindPort = 7801 quicBindPort = 7801 log.to = "frps.log" log.level = "trace" log.maxDays = 30 auth.token = "*" ``` ### Logs frps: ``` 2024/02/03 01:32:09 [I] [root.go:105] frps uses config file: /home/lc/opt/etc/frp/frps_3389.toml 2024/02/03 01:32:09 [I] [service.go:225] frps tcp listen on 0.0.0.0:7801 2024/02/03 01:32:09 [I] [service.go:249] frps quic listen on 0.0.0.0:7801 2024/02/03 01:32:09 [I] [root.go:114] frps started successfully 2024/02/03 01:32:13 [I] [service.go:563] [19065ba0f1dea30e] client login info: ip [111.201.29.102:9234] version [0.54.0] hostname [] os [windows] arch [amd64] 2024/02/03 01:32:13 [D] [control.go:432] [19065ba0f1dea30e] receive heartbeat 2024/02/03 01:32:13 [I] [udp.go:103] [19065ba0f1dea30e] [RDP-UDP] udp proxy listen port [13389] 2024/02/03 01:32:13 [I] [control.go:401] [19065ba0f1dea30e] new proxy [RDP-UDP] type [udp] success 2024/02/03 01:32:13 [I] [tcp.go:82] [19065ba0f1dea30e] [RDP-TCP] tcp proxy listen port [13389] 2024/02/03 01:32:13 [I] [control.go:401] [19065ba0f1dea30e] new proxy [RDP-TCP] type [tcp] success 2024/02/03 01:32:13 [D] [control.go:243] [19065ba0f1dea30e] new work connection registered 2024/02/03 01:32:14 [D] [control.go:272] [19065ba0f1dea30e] get work connection from pool 2024/02/03 01:32:14 [D] [proxy.go:131] [19065ba0f1dea30e] [RDP-UDP] get a new work connection: [111.201.29.102:9234] 2024/02/03 01:32:14 [T] [udp.go:117] [19065ba0f1dea30e] [RDP-UDP] loop waiting message from udp workConn 2024/02/03 01:32:14 [D] [control.go:243] [19065ba0f1dea30e] new work connection registered 2024/02/03 01:32:18 [I] [proxy.go:204] [19065ba0f1dea30e] [RDP-TCP] get a user connection [111.201.29.102:9247] 2024/02/03 01:32:18 [D] [control.go:272] [19065ba0f1dea30e] get work connection from pool 2024/02/03 01:32:18 [D] [proxy.go:131] [19065ba0f1dea30e] [RDP-TCP] get a new work connection: [111.201.29.102:9234] 2024/02/03 01:32:18 [T] [proxy.go:240] [19065ba0f1dea30e] [RDP-TCP] handler user tcp connection, use_encryption: false, use_compression: false 2024/02/03 01:32:18 [D] [proxy.go:261] [19065ba0f1dea30e] [RDP-TCP] join connections, workConn(l[10.0.16.4:7801] r[111.201.29.102:9234]) userConn(l[10.0.16.4:13389] r[111.201.29.102:9247]) 2024/02/03 01:32:18 [D] [control.go:243] [19065ba0f1dea30e] new work connection registered 2024/02/03 01:32:29 [D] [proxy.go:271] [19065ba0f1dea30e] [RDP-TCP] join connections closed ``` frpc: ``` 2024/02/03 01:32:14 [I] [root.go:142] start frpc service for config file [.\frpc_3389.toml] 2024/02/03 01:32:14 [I] [service.go:287] try to connect to server... 2024/02/03 01:32:14 [I] [service.go:279] [19065ba0f1dea30e] login to server success, get run id [19065ba0f1dea30e] 2024/02/03 01:32:14 [D] [control.go:244] [19065ba0f1dea30e] send heartbeat to server 2024/02/03 01:32:14 [I] [proxy_manager.go:173] [19065ba0f1dea30e] proxy added: [RDP-TCP RDP-UDP] 2024/02/03 01:32:14 [I] [service.go:177] admin server listen on 127.0.0.1:7501 2024/02/03 01:32:14 [T] [proxy_wrapper.go:200] [19065ba0f1dea30e] [RDP-UDP] change status from [new] to [wait start] 2024/02/03 01:32:14 [T] [proxy_wrapper.go:200] [19065ba0f1dea30e] [RDP-TCP] change status from [new] to [wait start] 2024/02/03 01:32:14 [D] [control.go:195] [19065ba0f1dea30e] receive heartbeat from server 2024/02/03 01:32:14 [I] [control.go:170] [19065ba0f1dea30e] [RDP-UDP] start proxy success 2024/02/03 01:32:14 [I] [control.go:170] [19065ba0f1dea30e] [RDP-TCP] start proxy success 2024/02/03 01:32:14 [D] [proxy_wrapper.go:260] [19065ba0f1dea30e] [RDP-UDP] start a new work connection, localAddr: [::]:50090 remoteAddr: *:7801 2024/02/03 01:32:14 [I] [udp.go:93] [19065ba0f1dea30e] [RDP-UDP] incoming a new work connection for udp proxy, *:7801 2024/02/03 01:32:19 [D] [proxy_wrapper.go:260] [19065ba0f1dea30e] [RDP-TCP] start a new work connection, localAddr: [::]:50090 remoteAddr: *:7801 2024/02/03 01:32:19 [T] [proxy.go:144] [19065ba0f1dea30e] [RDP-TCP] handle tcp work connection, useEncryption: false, useCompression: false 2024/02/03 01:32:19 [D] [proxy.go:208] [19065ba0f1dea30e] [RDP-TCP] join connections, localConn(l[127.0.0.1:12733] r[127.0.0.1:3389]) workConn(l[[::]:50090] r[*:7801]) 2024/02/03 01:32:29 [D] [proxy.go:220] [19065ba0f1dea30e] [RDP-TCP] join connections closed 2024/02/03 01:32:29 [T] [proxy.go:222] [19065ba0f1dea30e] [RDP-TCP] join connections errors: [read tcp 127.0.0.1:12733->127.0.0.1:3389: use of closed network connection] 2024/02/03 01:32:44 [D] [control.go:244] [19065ba0f1dea30e] send heartbeat to server 2024/02/03 01:32:44 [D] [control.go:195] [19065ba0f1dea30e] receive heartbeat from server 2024/02/03 01:32:44 [T] [udp.go:150] [19065ba0f1dea30e] [RDP-UDP] send ping message to udp workConn 2024/02/03 01:33:14 [D] [control.go:244] [19065ba0f1dea30e] send heartbeat to server 2024/02/03 01:33:14 [D] [control.go:195] [19065ba0f1dea30e] receive heartbeat from server 2024/02/03 01:33:14 [T] [udp.go:150] [19065ba0f1dea30e] [RDP-UDP] send ping message to udp workConn 2024/02/03 01:33:44 [D] [control.go:244] [19065ba0f1dea30e] send heartbeat to server 2024/02/03 01:33:44 [D] [control.go:195] [19065ba0f1dea30e] receive heartbeat from server 2024/02/03 01:33:44 [T] [udp.go:150] [19065ba0f1dea30e] [RDP-UDP] send ping message to udp workConn ``` ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [X] 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:02:19 -06:00
gitea-mirror commented 2026-05-05 14:02:22 -06:00
Author
Owner
Copy link

@kingwilliam commented on GitHub (Feb 5, 2024):

rdp-tcp : 3389
rdp-udp : 3391

<!-- gh-comment-id:1928299465 --> @kingwilliam commented on GitHub (Feb 5, 2024): rdp-tcp : 3389 **rdp-udp : 3391**
gitea-mirror commented 2026-05-05 14:02:23 -06:00
Author
Owner
Copy link

@Loyolichoo commented on GitHub (Feb 6, 2024):

rdp-tcp : 3389 rdp-udp : 3391

感谢分享。尝试了下这个修改，没有看到效果，客户端抓包看了一下，没有UDP报文产生，应该是前面TLS握手过程没有完成，还不会开始跑UDP流量。然后用互联网直连的方式抓包验证了一下，我目前使用的这个版本的RDP的UDP使用的端口号还是3389。

<!-- gh-comment-id:1928715500 --> @Loyolichoo commented on GitHub (Feb 6, 2024): > rdp-tcp : 3389 **rdp-udp : 3391** 感谢分享。尝试了下这个修改，没有看到效果，客户端抓包看了一下，没有UDP报文产生，应该是前面TLS握手过程没有完成，还不会开始跑UDP流量。然后用互联网直连的方式抓包验证了一下，我目前使用的这个版本的RDP的UDP使用的端口号还是3389。
gitea-mirror commented 2026-05-05 14:02:25 -06:00
Author
Owner
Copy link

@xqzr commented on GitHub (Feb 8, 2024):

#transport.protocol = "quic"
<!-- gh-comment-id:1934464901 --> @xqzr commented on GitHub (Feb 8, 2024): ```toml #transport.protocol = "quic" ```
gitea-mirror commented 2026-05-05 14:02:26 -06:00
Author
Owner
Copy link

@Loyolichoo commented on GitHub (Feb 11, 2024):

#transport.protocol = "quic"

试了一下，效果还是一样的

<!-- gh-comment-id:1937663460 --> @Loyolichoo commented on GitHub (Feb 11, 2024): > ```toml > #transport.protocol = "quic" > ``` 试了一下，效果还是一样的
gitea-mirror commented 2026-05-05 14:02:27 -06:00
Author
Owner
Copy link

@xqzr commented on GitHub (Feb 11, 2024):

在 frpc 捕获 7801 端口

<!-- gh-comment-id:1937809860 --> @xqzr commented on GitHub (Feb 11, 2024): 在 frpc 捕获 `7801` 端口
gitea-mirror commented 2026-05-05 14:02:27 -06:00
Author
Owner
Copy link

@Loyolichoo commented on GitHub (Feb 21, 2024):

在 frpc 捕获 7801 端口

没太明白捕获7801端口是什么意思。如果是指客户端配置的话，现在客户端与服务器通信的已经是7801端口了。如果是指用wireshark抓包的话，我尝试修改服务器跟客户端的配置，去掉quic和auth口令鉴权，最简化配置，服务器只保留日志相关，以及在frpc的配置文件中使用tls.enable = false，然后在网口抓包7801。但最终抓到的依旧是tls报文，不过我对比了回环抓包的报文，发现在mstsc客户端输入完frpc设备的密码，点确认之后，frps是有向frpc发送tls报文的，但是此时在回环接口上抓包就没有抓到这个报文

<!-- gh-comment-id:1957444884 --> @Loyolichoo commented on GitHub (Feb 21, 2024): > 在 frpc 捕获 `7801` 端口 没太明白捕获`7801`端口是什么意思。如果是指客户端配置的话，现在客户端与服务器通信的已经是7801端口了。如果是指用wireshark抓包的话，我尝试修改服务器跟客户端的配置，去掉quic和auth口令鉴权，最简化配置，服务器只保留日志相关，以及在frpc的配置文件中使用`tls.enable = false`，然后在网口抓包7801。但最终抓到的依旧是tls报文，不过我对比了回环抓包的报文，发现在mstsc客户端输入完frpc设备的密码，点确认之后，frps是有向frpc发送tls报文的，但是此时在回环接口上抓包就没有抓到这个报文
gitea-mirror commented 2026-05-05 14:02:28 -06:00
Author
Owner
Copy link

@xqzr commented on GitHub (Feb 21, 2024):

在 frpc 捕获 7801 端口

在frpc的配置文件中使用tls.enable = false，然后在网口抓包7801。但最终抓到的依旧是tls报文

52f66b05e6/conf/frpc_full_example.toml (L102)

<!-- gh-comment-id:1958142202 --> @xqzr commented on GitHub (Feb 21, 2024): > > 在 frpc 捕获 `7801` 端口 > > 在frpc的配置文件中使用`tls.enable = false`，然后在网口抓包7801。但最终抓到的依旧是tls报文 https://github.com/fatedier/frp/blob/52f66b05e624233105924906f67f10347a5ed0de/conf/frpc_full_example.toml#L102
gitea-mirror commented 2026-05-05 14:02:28 -06:00
Author
Owner
Copy link

@Loyolichoo commented on GitHub (Feb 25, 2024):

在 frpc 捕获 7801 端口

在frpc的配置文件中使用tls.enable = false，然后在网口抓包7801。但最终抓到的依旧是tls报文

52f66b05e6/conf/frpc_full_example.toml (L102)
这个配置是有效果的。重新抓了包，情况是这样的：第一轮鉴权的传输是正常的，到了RDP客户端输完密码回车的时候出问题了，此时RDP客户端向frps的13389端口发送了tls的client hello报文，而frps把RDP客户端请求的tls报文，也就是tcp的载荷完全一模一样得转发给了frpc客户端，frpc这端收到的tcp报文出来tcp头不一样，剩下的tcp载荷和RDP请求的报文完全一样。不知道frp的frps和frpc之间的交互协议是否有序列化的处理，至少我在前面的报文里没有看到有这种一模一样的载荷出现。而且这个报文没有在loopback口的3389端口上抓到，应该是被frpc丢掉了。

<!-- gh-comment-id:1963009427 --> @Loyolichoo commented on GitHub (Feb 25, 2024): > > > 在 frpc 捕获 `7801` 端口 > > > > > > 在frpc的配置文件中使用`tls.enable = false`，然后在网口抓包7801。但最终抓到的依旧是tls报文 > > https://github.com/fatedier/frp/blob/52f66b05e624233105924906f67f10347a5ed0de/conf/frpc_full_example.toml#L102 这个配置是有效果的。重新抓了包，情况是这样的：第一轮鉴权的传输是正常的，到了RDP客户端输完密码回车的时候出问题了，此时RDP客户端向frps的13389端口发送了tls的client hello报文，而frps把RDP客户端请求的tls报文，也就是tcp的载荷完全一模一样得转发给了frpc客户端，frpc这端收到的tcp报文出来tcp头不一样，剩下的tcp载荷和RDP请求的报文完全一样。不知道frp的frps和frpc之间的交互协议是否有序列化的处理，至少我在前面的报文里没有看到有这种一模一样的载荷出现。而且这个报文没有在loopback口的3389端口上抓到，应该是被frpc丢掉了。
gitea-mirror commented 2026-05-05 14:02:28 -06:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Mar 18, 2024):

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

<!-- gh-comment-id:2002684893 --> @github-actions[bot] commented on GitHub (Mar 18, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
gitea-mirror commented 2026-05-05 14:02:29 -06:00
Author
Owner
Copy link

@iwdm-cc commented on GitHub (Jun 28, 2024):

@Loyolichoo 你好，方便给一个可用的支持udp的远程桌面的配置参考吗？ 我一直配置不成功。
frpc Version
0.58.1

frps Version
0.58.1

frpc.toml

`serverAddr = "xxxx"
serverPort = 7001
transport.protocol = "kcp"
transport.tls.enable = true

proxies
name = "test-http"
type = "tcp"
localIP = "127.0.0.1"
localPort = 3389
remotePort = 6000

proxies
name = "zc-udp"
type = "udp"
localIP = "127.0.0.1"
localPort = 3389
remotePort = 6000`

frps.toml

bindPort = 7001 kcpBindPort = 7001

<!-- gh-comment-id:2196129533 --> @iwdm-cc commented on GitHub (Jun 28, 2024): @Loyolichoo 你好，方便给一个可用的支持udp的远程桌面的配置参考吗？ 我一直配置不成功。 frpc Version 0.58.1 frps Version 0.58.1 ## frpc.toml `serverAddr = "xxxx" serverPort = 7001 transport.protocol = "kcp" transport.tls.enable = true [[proxies]] name = "test-http" type = "tcp" localIP = "127.0.0.1" localPort = 3389 remotePort = 6000 [[proxies]] name = "zc-udp" type = "udp" localIP = "127.0.0.1" localPort = 3389 remotePort = 6000` ## frps.toml `bindPort = 7001 kcpBindPort = 7001`
gitea-mirror commented 2026-05-05 14:02:29 -06:00
Author
Owner
Copy link

@xqzr commented on GitHub (Jun 28, 2024):

@Loyolichoo 你好，方便给一个可用的支持udp的远程桌面的配置参考吗？ 我一直配置不成功。 frpc Version 0.58.1

frps Version 0.58.1

frpc.toml

`serverAddr = "xxxx" serverPort = 7001 transport.protocol = "kcp" transport.tls.enable = true

proxies name = "test-http" type = "tcp" localIP = "127.0.0.1" localPort = 3389 remotePort = 6000

proxies name = "zc-udp" type = "udp" localIP = "127.0.0.1" localPort = 3389 remotePort = 6000`

frps.toml

bindPort = 7001 kcpBindPort = 7001

放行 UDP 6000

<!-- gh-comment-id:2196367825 --> @xqzr commented on GitHub (Jun 28, 2024): > @Loyolichoo 你好，方便给一个可用的支持udp的远程桌面的配置参考吗？ 我一直配置不成功。 frpc Version 0.58.1 > > frps Version 0.58.1 > > ## frpc.toml > `serverAddr = "xxxx" serverPort = 7001 transport.protocol = "kcp" transport.tls.enable = true > > [[proxies]] name = "test-http" type = "tcp" localIP = "127.0.0.1" localPort = 3389 remotePort = 6000 > > [[proxies]] name = "zc-udp" type = "udp" localIP = "127.0.0.1" localPort = 3389 remotePort = 6000` > > ## frps.toml > `bindPort = 7001 kcpBindPort = 7001` 放行 UDP 6000
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev
new
master
copilot/review-pull-request-5198
v0.68.1
v0.68.0
v0.67.0
v0.66.0
v0.65.0
v0.64.0
v0.63.0
v0.62.1
v0.62.0
v0.61.2
v0.61.1
v0.61.0
v0.60.0
v0.59.0
v0.58.1
v0.58.0
v0.57.0
v0.56.0
v0.55.1
v0.55.0
v0.54.0
v0.53.2
v0.53.1
v0.53.0
v0.52.3
v0.52.2
v0.52.1
v0.52.0
v0.51.3
v0.51.2
v0.51.1
v0.51.0
v0.50.0
v0.49.0
v0.48.0
v0.47.0
v0.46.1
v0.46.0
v0.45.0
v0.44.0
v0.43.0
v0.42.0
v0.41.0
v0.40.0
v0.39.1
v0.39.0
v0.38.0
v0.37.1
v0.37.0
v0.36.2
v0.36.1
v0.36.0
v0.35.1
v0.35.0
v0.34.3
v0.34.2
v0.34.1
v0.34.0
v0.33.0
v0.32.1
v0.32.0
v0.31.2
v0.31.1
v0.31.0
v0.30.0
v0.29.1
v0.29.0
v0.28.2
v0.28.1
v0.28.0
v0.27.1
v0.27.0
v0.26.0
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.1
v0.24.0
v0.23.3
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.0
v0.19.1
v0.19.0
v0.18.0
v0.17.0
v0.16.1
v0.16.0
v0.15.1
v0.15.0
v0.14.1
v0.14.0
v0.13.0
v0.12.0
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.1
v0.8.0
v0.7.0
v0.6.0
v0.5.0
v0.3.0
v0.2.0
v0.1.0
Labels
Clear labels   
In Progress

   
WIP

   
WaitingForInfo

   
bug

   
doc

   
duplicate

   
easy

   
enhancement

   
future

   
help wanted

   
invalid

   
lifecycle/stale

   
need-issue-template

   
need-usage-help

   
no plan

   
proposal

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
todo
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#3149
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?