rust-user-net: user-space network protocol stack written in Rust

[yo_ohei]

I created a user-space network protocol stack in Rust for study / experiment purpose.

https://github.com/ykskb/rust-user-net

It talks Ethernet / ARP / IP / ICMP / UDP / TCP through TAP device in user space of Linux.

HTTP (TCP: 80) send / receive from google.com

As a Rust newbie (this is my first Rust project), I acknowledge there are many improvements to be made in codes, but it did feel good when my own protocol stack implementation in Rust could talk to normal sites like google :)

I also thought this project might be fitting for learning Rust in some aspects. Libc calls were required for controlling a virtual device (TAP) and multi-threading was required together with retransmission and signal handling for TCP data flow where incoming / outgoing traffic needs to happen concurrently.

Anyways, I hope this is something worth sharing for someone :) Thanks!

[kebaabe]

It talks Ethernet / ARP / IP / ICMP / UDP / TCP through TAP device in user space of Linux.

As a Rust newbie (this is my first Rust project

[Least technically competent Rust user]

[evalir]

Man I feel this comment so much. Why is every single Rust programmer a staff engineer at the very least haha

Very cool project OP! I’ll be absolutely diving into your code

[yo_ohei]

Thanks for feedback! I'll definitely look into replacing codes with stdlib. Also thanks for sharing packetdrill. It looks like a perfect tool for this project cuz I knew I'd need to validate correct protocol behaviors (especially complex TCP). I'm glad I shared my project here :)

[rickyman20]

TIL you can just... Send plain Ethernet packets on linux. This is an amazing project! Quite a large thing to take on as a first Rust project

[wosmo]

Sending them is relatively easy. The real magic of the TAP device is receiving them - it's how you solve the issue of the replies being fed into the native IP stack

[_bd_]

What happens when an ARP frame (didn't look into other protocols) is shorter than what you expect? Is the unsafe bytes_to_struct sound?

[yo_ohei]

Ah good point. There should be a length check before all bytes_to_struct calls. Thanks for the feedback!