Yancey Wang
Yancey Wang
不知道现在的情况，但是之前测试发现docker根本不能正常支持raw socket
有可能跟gro有关，两个tcp包被合并成了一个，插入的字节可能是udp2raw的包头 https://github.com/wangyu-/udp2raw-tunnel/issues/226
this option requires `root` or `cap_net_admin`.
Looks like it's my bad, I broke the BSD compile in some commit. It might solves the problem, if you change this line in `makefile`: ``` freebsd:git_version ${cc_local} -o ${NAME}_$@...
try to remove `-static`: ``` freebsd:git_version ${cc_local} -o ${NAME}_$@ -I. ${SOURCES} ${PCAP} ${FLAGS} -lrt -ggdb -O2 ${MP} ```
Hi. I was able to reproduce the test. The problem is that, when iperf3 see you are connecting to 127.0.0.1, it sends super large packets (on my side it's >8000)...
A new version is released, in this version UDPspeeder will remind you if a packet is being truncated. Hopefully this version fixed the problem/confusion. https://github.com/wangyu-/UDPspeeder/releases/tag/20210116.0
1. 如果用了`-i`参数，比如`-i 100 -f10:10`, 在发送端同一个FEC group里的20包会被均匀分到100毫秒里发送, 也就是每隔5毫秒发送一个。 接收端在收到任意10个包之后即可恢复原来的数据包。
In `mode 1`, the original packets are sent out immediately, then FEC is done using a copy of original packets. In `mode 0`, the original packets are buffered and not...
>额，最近又试了试，换了vultr，谷歌云。各种不同的系统。防火墙，iptable。nc也通。等等都关注了。没次都是服务端：received syn,sent syn ack back刷屏。我把 -k选项删除了以后，就ready了。我想应该是我的网络环境导致我不能收到aes128cbc加密的tcp吧。要不wangyu大兄弟给换一个加密方式，例如chacha20啥的。 issue题目说的单独工作，事实上可能当时我是看错了。 给大家一个参考。 我看很可能是你两边`-k`不一致，比如中文空格或者引号什么的导致的。