GSoC TCP/IP webpage edit patch

[Joshua Branson]

From 6fe963a6ed30de1b3162bf4a767478b6a161fb1c Mon Sep 17 00:00:00 2001
From: Joshua Branson <***@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

[Joan Lledó]

Hi,

Post by Joshua Branson
However lwip does not provide device drivers for ethernet or wireless

chips.

Mmm, that's true for wi-fi, but Ethernet is supported[1] and device drivers
are provided by netdde.

------------------------
[1]
https://git.savannah.gnu.org/cgit/hurd/hurd.git/tree/lwip/port/netif/hurdethif.c
Missatge de Joshua Branson <***@fastmail.com> del dia ds., 5 de maig
2018 a les 4:04:

[Joshua Branson]

Post by Joshua Branson
Hi,

Post by Joshua Branson
However lwip does not provide device drivers for ethernet or wireless

chips.
Mmm, that's true for wi-fi, but Ethernet is supported[1] and device drivers
are provided by netdde.

Ahh ok. I'll apply a corrected version in a moment.

At the moment I can't get ikiwiki to render the git repo into html. So
I can't really verify that the links I make point to the right URI.

Post by Joshua Branson
------------------------
[1]
https://git.savannah.gnu.org/cgit/hurd/hurd.git/tree/lwip/port/netif/hurdethif.c

[Joshua Branson]

From 4dd72f771e28ce482027a3ff05c0b2a86b3cd7b5 Mon Sep 17 00:00:00 2001
From: Joshua Branson <***@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 | 9 ++++++++-
1 file changed, 8 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..b95a0d61 100644
--- a/community/gsoc/project_ideas/tcp_ip_stack.mdwn
+++ b/community/gsoc/project_ideas/tcp_ip_stack.mdwn
@@ -12,7 +12,14 @@ 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. If you are only using an ethernet connection, then it is possible to use
+lwip as a complete replacement for pfinet. However, lwip uses the netdde device
+drivers for wireless chips, which are old drivers from an old version of linux. To use
+lwip for a wifi connection on more modern hardware, one would also need modern
+device drivers to access the internet. The promising approach to this is using
+a rump kernel. This is essentially the New Driver Framework google summer of
+code project idea.

A true hurdish network stack will use a set of [[hurd/translator]] processes,
each implementing a different protocol layer. This way not only the

[Joan Lledó]

Hello,

However, lwip uses the netdde device drivers for wireless chips,
which are old drivers from an old version of linux

Does netdde provide drivers for any wireless card? I don't remember.
Anyway, there's no difference between lwip and pfinet here, both need
netdde for reaching a NIC, and I guess they could use their Ethernet module
for working with a wireless driver provided netdde has one, but I'm not
sure of this.

[Samuel Thibault]

Hello,

Thanks for the patch, I have pushed it.

About wireless drivers, there used to be some pcmcia (pc-card) drivers,
but that's very old :) netdde doesn't include the wireless stack (even
if linux 2.6.26 used for netdde did have wireless drivers indeed).
Better go with rump anyway.

Samuel

[Joshua Branson]

Post by Joan Lledó
Hello,
Thanks for the patch, I have pushed it.
About wireless drivers, there used to be some pcmcia (pc-card) drivers,
but that's very old :) netdde doesn't include the wireless stack (even
if linux 2.6.26 used for netdde did have wireless drivers indeed).
Better go with rump anyway.
Samuel

awesome!