[GH-ISSUE #4614] [Feature Request] 想通过frp实现udp双向通信 但是配置一直没成功，能否帮忙看下原因

gitea-mirror commented

2026-05-05 14:20:17 -06:00

Owner

Copy link

Originally created by @Curtaingit on GitHub (Dec 31, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4614

Describe the feature request

frp版本 V0.60.0

服务器配置 frps.toml
bindPort = 7111

客户端1配置 frpc.toml
serverAddr = "60.191.121.45"
serverPort = 7111

proxies
name = "client1"
type = "udp"
localIP = "127.0.0.1"
localPort = 6678
remotePort = 6678

客户端2配置 frpc.toml
serverAddr = "60.191.121.45"
serverPort = 7111

proxies
name = "client1"
type = "udp"
localIP = "127.0.0.1"
localPort = 6677
remotePort = 6677

客户端应用程序逻辑

客户端1 接收端口为6678 发送数据到60.191.121.45的6677
客户端2 接收端口为6677 发送数据到60.191.121.45的6678

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 @Curtaingit on GitHub (Dec 31, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4614 ### Describe the feature request frp版本 V0.60.0 服务器配置 frps.toml bindPort = 7111 客户端1配置 frpc.toml serverAddr = "60.191.121.45" serverPort = 7111 [[proxies]] name = "client1" type = "udp" localIP = "127.0.0.1" localPort = 6678 remotePort = 6678 客户端2配置 frpc.toml serverAddr = "60.191.121.45" serverPort = 7111 [[proxies]] name = "client1" type = "udp" localIP = "127.0.0.1" localPort = 6677 remotePort = 6677 客户端应用程序逻辑客户端1 接收端口为6678 发送数据到60.191.121.45的6677 客户端2 接收端口为6677 发送数据到60.191.121.45的6678 ### 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 - [X] Others

gitea-mirror

2026-05-05 14:20:17 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:20:20 -06:00

Author

Owner

Copy link

@UR-l commented on GitHub (Dec 31, 2024):

客户端1接收端口6677的消息，客户端2往60.191.121.45的6677端口发消息

@UR-l commented on GitHub (Dec 31, 2024): 客户端1接收端口6677的消息，客户端2往60.191.121.45的6677端口发消息

gitea-mirror commented

2026-05-05 14:20:22 -06:00

Author

Owner

Copy link

@Curtaingit commented on GitHub (Dec 31, 2024):

客户端1接收端口6677的消息，客户端2往60.191.121.45的6677端口发消息

不行设备端程序限制只支持 6677接收然后回数据到6678

@Curtaingit commented on GitHub (Dec 31, 2024): > 客户端1接收端口6677的消息，客户端2往60.191.121.45的6677端口发消息不行设备端程序限制只支持 6677接收然后回数据到6678

gitea-mirror commented

2026-05-05 14:20:23 -06:00

Author

Owner

Copy link

@Curtaingit commented on GitHub (Dec 31, 2024):

现在客户端1发送没问题客户端2可以收到，但是客户端1没法接收客户端2的发出的数据

@Curtaingit commented on GitHub (Dec 31, 2024): 现在客户端1发送没问题客户端2可以收到，但是客户端1没法接收客户端2的发出的数据

gitea-mirror commented

2026-05-05 14:20:23 -06:00

Author

Owner

Copy link

@xqzr commented on GitHub (Jan 1, 2025):

可能需要多个 serverAddr

@xqzr commented on GitHub (Jan 1, 2025): 可能需要多个 `serverAddr`

gitea-mirror commented

2026-05-05 14:20:24 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jan 16, 2025):

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

@github-actions[bot] commented on GitHub (Jan 16, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

No Branch/Tag specified