Skip to content
This repository has been archived by the owner on Apr 14, 2024. It is now read-only.

Jumbo Frames message multiplied in Preflight Check #290

Closed
biggena opened this issue Dec 4, 2019 · 5 comments
Closed

Jumbo Frames message multiplied in Preflight Check #290

biggena opened this issue Dec 4, 2019 · 5 comments
Labels

Comments

@biggena
Copy link

biggena commented Dec 4, 2019

Ostinato version is 1.0, Docker.

When trying to generate frames with increment I have following message for size 1523 (6 messages in one alarm):
image

For size 1524 it is 12 messages in one screen, etc. Each extra byte produces 6 extra messages in this window.
Starting from some number it just doesn't fit the screen, so buttons are invisible:
image

Workaround: I proceed with this warning (despite OK button is not seen on the screen) by pressing "Tab" key and "Enter" when this window appears.

Feature enchancements: Would it be possible to add choice to disable such check permanently in preferences in newer Ostinato versions?

@biggena biggena changed the title Jumbo Frames multiplied message in Preflight Check Jumbo Frames message multiplied in Preflight Check Dec 4, 2019
@pstavirs pstavirs added the bug label Dec 6, 2019
@pstavirs
Copy link
Owner

@biggena : I've fixed the multiple error message issue which was a bug - it should have been reported only once despite however many frames may experience that issue. Regarding a disable check option - how big of a nuisance is it? My worry is that if a user disables that check, he may not realize that some change that he made in the stream may cause other errors without the error check.

@biggena
Copy link
Author

biggena commented Dec 29, 2019

@pstavirs Thank you for fixing, when it will be available in some minor release version?
About option to disable such check - I find quite annoying getting a lot such messages during a testing day, especially when I know that I"m working with Jumbo frames. You can embed such option in Preference, but keep it disabled. Only experienced user will enable it and escape some extra warnings... Thank you.

@pstavirs
Copy link
Owner

@biggena : thanks for the quick reply. Your annoyance is regarding just the jumbo frames error message or other messages also? The reason I ask is if it is just jumbo, I might think of other ways to avoid the errors e.g. by checking interface MTU directly and not reporting the error if the MTU > packet size.

Regarding the new minor release, I need to collect several bugfixes before I can issue a minor release. Release making is very time consuming and needs to be thoroughly tested to make sure no major bugs are introduced - all of it needs to be done on multiple platforms as well, so realistically it will be a couple of months most likely.

@biggena
Copy link
Author

biggena commented Dec 29, 2019

@pstavirs My annoyance was only about permanent jumbo frames warnings, if you can avoid it by checking interface MTU - it will work, great idea!
Thank you and Happy New Year!

@pstavirs
Copy link
Owner

@biggena : I filed #296 to track the jumbo check against interface MTU. Warning - it may take some time to implement that as it will likely need platform specific code for each platform.

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

No branches or pull requests

2 participants