Catherine
Catherine
Once you figure out a design we might lift it into smoltcp, but right now I feel like it's not the right direction for this project to delve into.
I don't think this works. For example, an Ethernet port has an `EthernetInterface` on top of it, and a PPP link has a `PppInterface` on top of it. Now you...
> we can have IpInterface to hold Option, Option, Option, etc., without using trait objects. Each of these interfaces would use a single Device encapsulating several physical links via iface_id....
* I've realized that using an EthernetInterface for loopback is, of course, a wrong approach, and we should have a LoopbackInterface for that. This precludes your approach since a LoopbackInterface...
Okay, I understand your proposal more clearly now. I will reconsider it.
I have reconsidered it and, indeed, it makes perfect sense. Also, we can just have a `ManagedSlice>>` to avoid using `Box`.
I agree that checking for `TP_STATUS_CSUMNOTREADY` would be a proper solution. Unfortunately we can't integrate it with the rest of smoltcp at the moment, I believe, since checksum capabilities are...
What do you think about checking for `TP_STATUS_CSUMNOTREADY` and if it is set, recalculating the checksum?
I'm wondering if maybe a dynamically scoped flag would be more fitting there, to give caller control over printing. (And for `with_path` as well.)
I'm sorry, reimplementing on top of *what*?