Catherine
Catherine
Something I just remembered that might be very relevant to your work is that having several open sockets in LISTEN state with the same local endpoint is perfectly legal. That's...
Yeah that works.
Hmm, I'm not sure if I like this idea very much, we already have drop magic in Device and that's pretty bad already. But I can give it a look.
Wouldn't bip buffers require paging and use unsafe code? I'm not sure I like having either of those in smoltcp core, since being written in 100% safe Rust and not...
A possible alternative is an API that uses a list of chunks instead of a single chunk, similar to `iovec`.
> Is there really no unsafe code in the existing dependencies? `byteorder` seems to have quite some. > I suspect the [bbqueue](https://docs.rs/bbqueue/0.4.8/bbqueue/) or [spsc-bip-buffer](https://github.com/utaal/spsc-bip-buffer) authors would say they do it...
@klickverbot Is there some source of truth for which RFCs are actually authoritative for TCP? RFC 793 is hopelessly outdated and has errata, RFC 1122 fixes some of that, highlights...
@klickverbot Thanks
The TCP specification dictates a particular algorithm for the PRNG. While not great it's more complex than just the timestamp...
So... why does _smoltcp_ need to support multiple interfaces? It's not only perfectly doable but also IMO more convenient to build routing on *top* of it. That is, packets originating...