Hello, I noticed that the tcp/ip webpage for the Hurd does not mention that we already have a port of the lwip tcp/ip stack. This patch briefly explains it.
>From 6fe963a6ed30de1b3162bf4a767478b6a161fb1c Mon Sep 17 00:00:00 2001 From: Joshua Branson <jbra...@fastmail.com> Date: Thu, 3 May 2018 09:53:04 -0400 Subject: [PATCH] * community/gsoc/project_ideas/tcp_ip_stack.mdwn
I mentioned that lwip was recently ported to the hurd. --- community/gsoc/project_ideas/tcp_ip_stack.mdwn | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/community/gsoc/project_ideas/tcp_ip_stack.mdwn b/community/gsoc/project_ideas/tcp_ip_stack.mdwn index 6410dee0..61831668 100644 --- a/community/gsoc/project_ideas/tcp_ip_stack.mdwn +++ b/community/gsoc/project_ideas/tcp_ip_stack.mdwn @@ -12,7 +12,10 @@ is included in the section entitled The Hurd presently uses a [[TCP/IP_stack|hurd/translator/pfinet]] based on code from an old Linux version. This works, but lacks some rather important features (like PPP/PPPoE), and the -design is not hurdish at all. +design is not hurdish at all. Recently lwip, which is an userspace tcp/ip library, +was ported to the Hurd. It is possible to use lwip as a complete replacement for pfinit. +However lwip does not provide device drivers for ethernet or wireless chips. +To use lwip on real hardware, one would also need device drivers to access the internet. A true hurdish network stack will use a set of [[hurd/translator]] processes, each implementing a different protocol layer. This way not only the -- 2.17.0
Thanks, Joshua
