github-starred/frp

Fork 0

mirror of https://github.com/fatedier/frp.git synced 2026-05-15 08:05:49 -06:00

[GH-ISSUE #1117] UDP first pack only #874

New issue

Closed

opened 2026-05-05 12:33:19 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 12:33:19 -06:00

Owner

Originally created by @elvizlai on GitHub (Mar 8, 2019).
Original GitHub issue: https://github.com/fatedier/frp/issues/1117

What version of frp are you using (./frpc -v or ./frps -v)?
0.24.1

What operating system and processor architecture are you using (go env)?
centos 7

Configures you used:
client

[udptest]
type = udp
local_ip = 10.10.10.2
local_port = 2001
use_encryption = false
use_compression = false
remote_port = 2001

server

proxy_bind_addr = 127.0.0.1

Steps to reproduce the issue:

start frpc and frps, tcp conn is ok.
on client side, run nc -l -u 2001 to receive udp pack
on server side, run nc -v -u 127.0.0.1 2001 to send udp pack
every time client side can rev only first pack. then is MUST restart nc -l -u 2001.

Describe the results you received:
ONLY first pack received.

Describe the results you expected:
should receive every pack

Originally created by @elvizlai on GitHub (Mar 8, 2019). Original GitHub issue: https://github.com/fatedier/frp/issues/1117 **What version of frp are you using (./frpc -v or ./frps -v)?** 0.24.1 **What operating system and processor architecture are you using (`go env`)?** centos 7 **Configures you used:** client ``` [udptest] type = udp local_ip = 10.10.10.2 local_port = 2001 use_encryption = false use_compression = false remote_port = 2001 ``` server ``` proxy_bind_addr = 127.0.0.1 ``` **Steps to reproduce the issue:** 1. start frpc and frps, tcp conn is ok. 2. on client side, run `nc -l -u 2001` to receive udp pack 3. on server side, run `nc -v -u 127.0.0.1 2001` to send udp pack 4. every time client side can rev only first pack. then is MUST restart `nc -l -u 2001`. ![jietu20190308-173630](https://user-images.githubusercontent.com/501861/54020752-7f362e80-41c9-11e9-9ddd-eeda8c3e2480.jpg) **Describe the results you received:** ONLY first pack received. **Describe the results you expected:** should receive every pack

gitea-mirror

2026-05-05 12:33:19 -06:00

closed this issue
added the
WaitingForInfo
label

gitea-mirror commented

2026-05-05 12:33:22 -06:00

Author

Owner

@fatedier commented on GitHub (Mar 8, 2019):

Can't reproduce this in my environment.

@fatedier commented on GitHub (Mar 8, 2019): Can't reproduce this in my environment.

gitea-mirror commented

2026-05-05 12:33:23 -06:00

Author

Owner

@fatedier commented on GitHub (Mar 8, 2019):

You can set log_level = trace to watch each udp package got by frpc.

@fatedier commented on GitHub (Mar 8, 2019): You can set `log_level = trace` to watch each udp package got by frpc.

gitea-mirror commented

2026-05-05 12:33:24 -06:00

Author

Owner

@elvizlai commented on GitHub (Mar 8, 2019):

@fatedier every pack is received from frpc, but the client received only first pack, very wired...

get udp package from workConn: YWJjZDEyMzQK

@elvizlai commented on GitHub (Mar 8, 2019): @fatedier every pack is received from frpc, but the client received only first pack, very wired... ``` get udp package from workConn: YWJjZDEyMzQK ```

gitea-mirror commented

2026-05-05 12:33:24 -06:00

Author

Owner

@fatedier commented on GitHub (Mar 8, 2019):

Use tcpdump to trace more info.

@fatedier commented on GitHub (Mar 8, 2019): Use `tcpdump` to trace more info.

gitea-mirror commented

2026-05-05 12:33:25 -06:00

Author

Owner

@elvizlai commented on GitHub (Mar 9, 2019):

if using UDP, do not run frpc in docker bridge network, should use host.

@elvizlai commented on GitHub (Mar 9, 2019): if using UDP, do not run frpc in docker bridge network, should use host.