mkresin:

Which board are you using? Which LEDE revision?

jiangyaohui:

my board is cf-e320n-v2, revision is r4433-680a5c5

mkresin:

Please try a recent snapshot first. r4433-680a5c5 is > 2 month old. Might be that the issue is already fixed.

jiangyaohui:

I update the latest code to r4768-89f8a01, this bug exist also.

chunkeey:

Hmm, there's a problem with your procedure.

In order to specify the size of a ping package, you have to use "-s" and not the "-l" parameter.

-l 65500 would mean that you "shotgun" all those packages and ping's manpage
(https://linux.die.net/man/8/ping) has the following to say about the parameter: "If preload is specified, ping sends that many packets not waiting for reply."

So, can you retry with ping 192.168.1.1 -s 65500?
If it still fails, can you look at which point/size the package start to disappear?

arjendekorte:

Note the OP indicated:

PC execute command "ping 192.168.1.1 -l 65500 -t" fail or timeout.

I assume he's using Windows to send the ping command and in that case, the command is correct. In fact, I just tried this with my router and it does what is expected. In my case, the pings are answered by the router though.

jiangyaohui:

Christian Lamparter:
I use Windows to send the ping command, the command is same as Linux "ping 192.168.1.1 -s 65500";
ping the size 56710 OK;
ping the size 56720 timeout sometimes;
ping the size 65500 timeout always;

jiangyaohui:

Does anyone pay attention to this bug? It looks like jumbo frames error, qualcomm's QSDK not this bug