Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

控制台的统计数据输出可能存在问题 #29

Open
ywgATustcbbs opened this issue Jun 5, 2024 · 4 comments
Open

控制台的统计数据输出可能存在问题 #29

ywgATustcbbs opened this issue Jun 5, 2024 · 4 comments

Comments

@ywgATustcbbs
Copy link

与客户端通信一直正常,但统计信息里却没有任何流量信息。只有一个客户端连接进来,开启了端口跳跃

kcptube version 20240602
Error Found in Configuration File(s): No
Servers: 1
Relays: 0
Clients: 0
kcptube is running in server mode
[2024-06-05 22:21:03 +0800] Summary of server.conf
receive (raw): 0 Byte/s, receive (inner): 0 Byte/s, send (inner): 0 Byte/s, send (raw): 0 Byte/s, fec recover: 0
mux_tunnels: receive (tcp): 0 Byte/s, receive (udp): 0 Byte/s, send (tcp): 0 Byte/s, send (udp): 0 Byte/s

[2024-06-05 22:22:03 +0800] Summary of server.conf
receive (raw): 0 Byte/s, receive (inner): 0 Byte/s, send (inner): 0 Byte/s, send (raw): 0 Byte/s, fec recover: 0
mux_tunnels: receive (tcp): 0 Byte/s, receive (udp): 0 Byte/s, send (tcp): 0 Byte/s, send (udp): 0 Byte/s

[2024-06-05 22:23:03 +0800] Summary of server.conf
receive (raw): 0 Byte/s, receive (inner): 0 Byte/s, send (inner): 0 Byte/s, send (raw): 0 Byte/s, fec recover: 0
mux_tunnels: receive (tcp): 0 Byte/s, receive (udp): 0 Byte/s, send (tcp): 0 Byte/s, send (udp): 0 Byte/s

[2024-06-05 22:24:03 +0800] Summary of server.conf
receive (raw): 0 Byte/s, receive (inner): 0 Byte/s, send (inner): 0 Byte/s, send (raw): 0 Byte/s, fec recover: 0
mux_tunnels: receive (tcp): 0 Byte/s, receive (udp): 0 Byte/s, send (tcp): 0 Byte/s, send (udp): 0 Byte/s

[2024-06-05 22:25:03 +0800] Summary of server.conf
receive (raw): 0 Byte/s, receive (inner): 0 Byte/s, send (inner): 0 Byte/s, send (raw): 0 Byte/s, fec recover: 0
mux_tunnels: receive (tcp): 0 Byte/s, receive (udp): 0 Byte/s, send (tcp): 0 Byte/s, send (udp): 0 Byte/s

[2024-06-05 22:26:03 +0800] Summary of server.conf
receive (raw): 0 Byte/s, receive (inner): 0 Byte/s, send (inner): 0 Byte/s, send (raw): 0 Byte/s, fec recover: 0
mux_tunnels: receive (tcp): 0 Byte/s, receive (udp): 0 Byte/s, send (tcp): 0 Byte/s, send (udp): 0 Byte/s

[2024-06-05 22:27:03 +0800] Summary of server.conf
receive (raw): 572 Bytes/s, receive (inner): 34 Bytes/s, send (inner): 317 Bytes/s, send (raw): 1060 Bytes/s, fec recover: 0
KCP#2315679149 average latency: 63 ms
KCP#4048496981 average latency: 47 ms
mux_tunnels: receive (tcp): 0 Byte/s, receive (udp): 0 Byte/s, send (tcp): 0 Byte/s, send (udp): 0 Byte/s

[2024-06-05 22:28:03 +0800] Summary of server.conf
receive (raw): 0 Byte/s, receive (inner): 0 Byte/s, send (inner): 0 Byte/s, send (raw): 0 Byte/s, fec recover: 0
KCP#2315679149 average latency: 63 ms
KCP#4048496981 average latency: 47 ms
mux_tunnels: receive (tcp): 0 Byte/s, receive (udp): 0 Byte/s, send (tcp): 0 Byte/s, send (udp): 0 Byte/s

[2024-06-05 22:29:03 +0800] Summary of server.conf
receive (raw): 682 Bytes/s, receive (inner): 25 Bytes/s, send (inner): 118 Bytes/s, send (raw): 3349 Bytes/s, fec recover: 0
KCP#2315679149 average latency: 63 ms
KCP#2212510674 average latency: 47 ms
KCP#4048496981 average latency: 47 ms
mux_tunnels: receive (tcp): 0 Byte/s, receive (udp): 0 Byte/s, send (tcp): 0 Byte/s, send (udp): 0 Byte/s

[2024-06-05 22:30:03 +0800] Summary of server.conf
receive (raw): 572 Bytes/s, receive (inner): 34 Bytes/s, send (inner): 317 Bytes/s, send (raw): 1060 Bytes/s, fec recover: 1
KCP#2212510674 average latency: 47 ms
KCP#3286824258 average latency: 48 ms
KCP#1253317755 average latency: 47 ms
mux_tunnels: receive (tcp): 0 Byte/s, receive (udp): 0 Byte/s, send (tcp): 0 Byte/s, send (udp): 0 Byte/s

[2024-06-05 22:31:03 +0800] Summary of server.conf
receive (raw): 0 Byte/s, receive (inner): 0 Byte/s, send (inner): 0 Byte/s, send (raw): 0 Byte/s, fec recover: 0
KCP#2212510674 average latency: 47 ms
KCP#3286824258 average latency: 48 ms
KCP#1253317755 average latency: 47 ms
mux_tunnels: receive (tcp): 0 Byte/s, receive (udp): 0 Byte/s, send (tcp): 0 Byte/s, send (udp): 0 Byte/s

[2024-06-05 22:32:03 +0800] Summary of server.conf
receive (raw): 0 Byte/s, receive (inner): 0 Byte/s, send (inner): 0 Byte/s, send (raw): 0 Byte/s, fec recover: 0
KCP#3286824258 average latency: 48 ms
KCP#1253317755 average latency: 47 ms
mux_tunnels: receive (tcp): 0 Byte/s, receive (udp): 0 Byte/s, send (tcp): 0 Byte/s, send (udp): 0 Byte/s

[2024-06-05 22:33:03 +0800] Summary of server.conf
receive (raw): 0 Byte/s, receive (inner): 0 Byte/s, send (inner): 0 Byte/s, send (raw): 0 Byte/s, fec recover: 0
mux_tunnels: receive (tcp): 0 Byte/s, receive (udp): 0 Byte/s, send (tcp): 0 Byte/s, send (udp): 0 Byte/s

[2024-06-05 22:34:03 +0800] Summary of server.conf
receive (raw): 0 Byte/s, receive (inner): 0 Byte/s, send (inner): 0 Byte/s, send (raw): 0 Byte/s, fec recover: 0
mux_tunnels: receive (tcp): 0 Byte/s, receive (udp): 0 Byte/s, send (tcp): 0 Byte/s, send (udp): 0 Byte/s

[2024-06-05 22:35:03 +0800] Summary of server.conf
receive (raw): 0 Byte/s, receive (inner): 0 Byte/s, send (inner): 0 Byte/s, send (raw): 0 Byte/s, fec recover: 0
mux_tunnels: receive (tcp): 0 Byte/s, receive (udp): 0 Byte/s, send (tcp): 0 Byte/s, send (udp): 0 Byte/s

@cnbatch
Copy link
Owner

cnbatch commented Aug 3, 2024

已针对这个情况发了新版本,试一试?

@ywgATustcbbs
Copy link
Author

ywgATustcbbs commented Aug 6, 2024

简单测试了一下,依然可能存在问题。

os win10
网络 本地loopback
应用场景 游戏(project zomboid)
详情
游戏客户端连接到(127.0.0.1:16666)
kcptube 客户端监听127.0.0.1:16666,转发127.0.0.1:30000
kcptube 服务端监听127.0.0.1:30000,转发127.0.0.1:16261
游戏服务端(独立服务器)监听127.0.0.1:16261

问题
游戏地图加载和怪物等信息同步流量不应该是每分钟不到1KB,这很不合理,特意在地图上移动了比较远的距离以使得游戏加载传输地图数据。
而且后面同样有传输速率为0的情况(至少测试到 2024-08-06 17:10:48 这个时间,前面有很长一段时间没有流量,但实际应该有)
此外,建议无论有没有添加log_file,均默认在控制台输出网络信息

日志

client-log.txt

server-log.txt

@cnbatch
Copy link
Owner

cnbatch commented Aug 6, 2024

简单测试了一下,依然可能存在问题。

os win10 网络 本地loopback 应用场景 游戏(project zomboid) 详情 游戏客户端连接到(127.0.0.1:16666) kcptube 客户端监听127.0.0.1:16666,转发127.0.0.1:30000 kcptube 服务端监听127.0.0.1:30000,转发127.0.0.1:16261 游戏服务端(独立服务器)监听127.0.0.1:16261

问题 游戏地图加载和怪物等信息同步流量不应该是每分钟不到1KB,这很不合理,特意在地图上移动了比较远的距离以使得游戏加载传输地图数据。 而且后面同样有传输速率为0的情况(至少测试到 2024-08-06 17:10:48 这个时间,前面有很长一段时间没有流量,但实际应该有) 此外,建议无论有没有添加log_file,均默认在控制台输出网络信息

日志

client-log.txt

server-log.txt

从 17:06:48 到 17:11:48 这段时间,游戏是否正在运行且传输数据?

从 Log 来看,既然连 KCP#XXXXXXX average latency 都不存在,那就是日志在输出的时候并不存在任何连接。那么速率为 0 倒也不奇怪。

@ywgATustcbbs
Copy link
Author

简单测试了一下,依然可能存在问题。
os win10 网络 本地loopback 应用场景 游戏(project zomboid) 详情 游戏客户端连接到(127.0.0.1:16666) kcptube 客户端监听127.0.0.1:16666,转发127.0.0.1:30000 kcptube 服务端监听127.0.0.1:30000,转发127.0.0.1:16261 游戏服务端(独立服务器)监听127.0.0.1:16261
问题 游戏地图加载和怪物等信息同步流量不应该是每分钟不到1KB,这很不合理,特意在地图上移动了比较远的距离以使得游戏加载传输地图数据。 而且后面同样有传输速率为0的情况(至少测试到 2024-08-06 17:10:48 这个时间,前面有很长一段时间没有流量,但实际应该有) 此外,建议无论有没有添加log_file,均默认在控制台输出网络信息
日志
client-log.txt
server-log.txt

从 17:06:48 到 17:11:48 这段时间,游戏是否正在运行且传输数据?

从 Log 来看,既然连 KCP#XXXXXXX average latency 都不存在,那就是日志在输出的时候并不存在任何连接。那么速率为 0 倒也不奇怪。

我确定这个时间在游戏里跑图,结束跑图后是立即把日志另存了一份的,最多是最后有几十秒退出游戏保存日志时间没有实际通信的。所以我才会觉得没有通信很奇怪。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants