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
FS#963 - chips is qca9531, pc ping device ip fail or timeout with big size, exp: ping 192.168.1.1 -l 65500 #7116
Comments
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 So, can you retry with ping 192.168.1.1 -s 65500? |
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: |
jiangyaohui: Does anyone pay attention to this bug? It looks like jumbo frames error, qualcomm's QSDK not this bug |
jiangyaohui:
this problem is always occurs on.
Steps:
My device is router, chip is QCA9531.
PC ip is 192.168.1.100, router ip is 192.168.1.1.
PC execute command "ping 192.168.1.1 -l 65500 -t" fail or timeout.
The text was updated successfully, but these errors were encountered: