<GitHub26>
[smoltcp] whitequark commented on pull request #178 b8c2b90: Why did you do this? smoltcp intentionally pops up errors to the very top of the stack, such that if you receive malformed packets and nothing works, you do not have to wonder as to what is the cause. https://github.com/m-labs/smoltcp/pull/178#discussion_r184833347
cr1901_modern has quit [Read error: Connection reset by peer]
<GitHub94>
[smoltcp] podhrmic commented on pull request #190 9f89675: Can you elaborate? If the packet is not fragmented, the check goes on as before. If it is fragmented, I skip this check (and verify the length upon assembly). https://github.com/m-labs/smoltcp/pull/190#discussion_r184864516