[[!meta copyright="Copyright © 2000, 2008, 2013 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] The `pfinet` server is a hacked Linux internet implementation with a glue layer translating between the Hurd [[RPC]]s and the middle layer of the Linux implementation. # Bugs ## Those Listed on [[Open_Issues]] ## [[IPv6]] ## IRC, freenode, #hurd, 2013-04-03 youpi: there are indeed historical bugs with small packets and tcp_nodelay in linux 2.0/2.2 tcp/ip oh http://jl-icase.home.comcast.net/~jl-icase/LinuxTCP2.html # Reimplementation, [[!GNU_Savannah_task 5469]] ## [[community/gsoc/project_ideas/tcp_ip_stack]] ## IRC, freenode, #hurd, 2013-04-03 [[!tag open_issue_hurd]] I was thinking about just using liblwip this afternoon, btw what is it ? hm, why not i would still prefer using code from netbsd especially now with the rump kernel project making it even easier well, whatever is easy to maintain up to date actually netbsd's focus on general portability normally makes it easy to maintain the author of the rump project was able to make netbsd code run in browsers :) and he actually showed clients using the networking stack on windows, remotely (not in the same process) so that's very close to what we want indeed though liblwip is exactly the same portability focus :) apparently, for embedded systems but bsd's code is probably better yes i think so, more general purpose, larger user base I used it for the stubdomains in Xen (it = lwip) ok