BrianZill
BrianZill
Now that we've replaced our home-grown Port16 type with u16, and the associated Ipv4Endpoint struct with std::net::SocketAddrV4, we should have an easier time of interfacing our code with Rust standard...
This PR changes the `TcpSegment` struct so that the `data` field is now `Option` instead of `Buffer`. This struct is used in issuing transmission requests to the runtime. Before this...
Currently, the TcpSegment structure has a "data" field of type Buffer, which is used to specify the packet payload data to be sent. This field is not optional, so even...
Description ======== The standard socket API normally accepts `INADDR_ANY` (the all-zeroes address) as the wildcard (or "unspecified") address, meaning it matches all addresses. We don't appear to currently support this....
Description ======== First the good: catnip's Ephemeral Port allocator uses the correct (RFC 6335 designated) range. And it allocates them in a random fashion (recommended to thwart certain types of...
This is about code clarity. Currently, the stack has several structures referred to as "options" that are really configuration parameters. This can be confusing, as some protocols (particularly TCP) have...
The stack currently only supports a single network interface, which is expected to have a single MAC address and a single IPv4 address. Even if we decide we only care...
Description ======== In the top-level src/lib.rs, the do_receive routine attempts to filter out packets sent to "bad" hardware addresses. Currently, this only allows for a single local ethernet address, and...
Currently, getting from a Queue Descriptor to an Established connection takes two separate hash table lookups. These lookups occur for several different fast-path API calls, and presumably could be reduced...
There is a well-known undesirable interaction between TCP's "delayed ACK" mechanism and Nagle's Algorithm that can cause unnecessary delays in request-response protocols. (Basically, a sender with a small amount of...