Skip to content

Conversation

@jcbnq
Copy link

@jcbnq jcbnq commented Oct 27, 2025

In #492, we finally discovered that a network segment was dropping packets from booster because of an MTU less than 1500. Since booster doesn't implement anything to react to ICMP MTU-related responses from the segment refusing to deliver the large frames, everything ends up being silently dropped. Because the telemetry packets all get bundled together at ~300B each, it only takes about 4 to hit the MTU, and trigger this behaviour.

Rather than implementing full MTU handling, in this PR I've added a configuration setting that allows the user to reduce the default 1500 MTU if they wish to, on a fixed basis.

@jordens
Copy link
Member

jordens commented Oct 27, 2025

It's unlikely that this is the correct (or an acceptable) fix. Could you check whether this is a fixed bug (in booster main or #488 or addressed in a newer smoltcp)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants