smoltcp
smoltcp copied to clipboard
smoltcp-rs
a smol tcp/ip stack
When calling `interface_mtu` for the IEEE802154 medium, a value of 123 is returned, instead of 125 or 127 (when including the IEEE80254 checksum field). I just noticed it now, because...
Currently running the `server` example fails: ``` [dirbaio@mars smoltcp]$ cargo run --example server -- --tap tap0 Compiling smoltcp v0.8.0 (/home/dirbaio/akiles/smoltcp) Finished dev [unoptimized + debuginfo] target(s) in 2.39s Running `target/debug/examples/server...
[RFC 4861 7.3.2] defines several states a Neighbor Cache entry can be in. Neighbor Cache entries should be updated to include these states and the use of the Neighbor Cache...
``` xiewenyudeMBP:shadowsocks-rust xiewenyu$ cargo build --target aarch64-apple-ios --features "local-tun local-redir armv8 neon" Compiling smoltcp v0.8.0 Compiling shadowsocks v1.13.2 (/Users/xiewenyu/Desktop/rust-project/shadowsocks-rust/crates/shadowsocks) error[E0425]: cannot find value `BIOCSETIF` in this scope --> /Users/xiewenyu/.cargo/registry/src/github.com-1ecc6299db9ec823/smoltcp-0.8.0/src/phy/sys/bpf.rs:79:29 |...
**Steps:** 1. Send a packet to a device running smoltcp with an IP source address X. 2. Device: respond to the packet (maybe you're doing UDP echo, as a simple...
When I boot a dev board running `[email protected]` and ping it, I see the following defmt output on the host: ``` DEBUG address 192.168.1.1 not in neighbor cache, sending ARP...
Add up/down methods to Device and Interface for placing the underlying device in a up or down state. This interface will also be handy when adding support for MLDv2.
In a similar spirit, I would also like to implement support for IP fragmentation. The logic behind fragmentation is pretty straightforward, but the way to implement it less so. So...
Right now the way lifetimes are handled requires some very unobvious contortions. Here's the ionpak code: https://github.com/m-labs/ionpak/blob/4347ddc5379594b299e1fa6c294449e01cc27b78/firmware/src/main.rs#L158-L192
We don't have a clock with the 4 us resolution as RFC 793 wants, but it's likely fine to use the 1 ms resolution clock too.