-
Notifications
You must be signed in to change notification settings - Fork 31
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
problem with jumbo frames / MTU #179
Labels
bug
Something isn't working
Comments
grubFX
changed the title
problem with jumbro frames / MTU
problem with jumbo frames / MTU
Jan 28, 2024
I can confirm that I have the same problem. I can reproduce the panic in the BMC with unicast or broadcast ping using a 9000 byte buffer and no fragmentation. Windows: It has happened every time I am building v2.1.0-RC2 to compare the behaviour.
Console output after receiving a jumbo ping:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The BMC on my TuringPI2 becomes unresponsive as soon as jumbo frames are enabled on my network. I kept seeing ~10 to a maximum of ~40 seconds of pings that would go through before I can't see it onthe network anymore. On some tries I managed to login, but it still crashed after roughly the same amount of time.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It would ba nice if the BMC also worked on a network with jumbo frames enabled.
Versions
tested on bmc version=2.0.5
Additional context
As an easy workaround I disabled jumbo frames on my network and rebooted the TuringPi2 board, which worked. But as soon as I turn on jumbo frames on my network again the BMC crashes.
The text was updated successfully, but these errors were encountered: