hsheth2/gonet

A TCP/IP network stack written in Go.

gonet's Issues

PoC or production ready?

Is this project intended to become a production ready implementation? Or is it mainly designed to be a proof-of-concept to illustrate the ideas in the paper?

Reading the code, I can see a number of possible issues and omissions. I am not sure whether to report these and/or try to fix and whether that is something you are interested in?

The reason I ask is that I have been working on a TCP implementation myself in golang. Mine is not as complete as yours. It's structured quite differently too. I'm trying to decide whether to abandon my efforts and contribute you your stack, but before I decide I want to ensure our goals are aligned enough.

My goal is to have a TCP implementation, with simplicity and correctness being the priorities. performance is an important but secondary goal for me. As well as running TCP over ipv4 as you have, I also want it to be abstracted enough to be able to run over things other than ipv4 and ipv6.

One example goal for me is tunnelling TCP over UDP, to allow application level TCP like behaviour, but with easier NAT traversal, and without requiring authority on the system to managed tun/tap devices etc.

build failure

running Make fails during tap_setup.sh because "git clone https://[email protected]/primesteam/tapip.git" requires a password.

License

I could not find the license. Maybe add a LICENSE fil