@olsen
The "amigazation" and access to inner workings of packets and connections is very nice. I have never had need for PPPoE, but PPP I use quite a bit, "tethering" (?), or lately on MiniMig using nullmodem or bluetooth link, and my experience is that stability is a heck lot more important than speed.
Zeroconf is nice (never needed it), but what I miss is media players capable of playing content streamed over multicast, which means support for PIM-SM, SDM, SSM...
As for IPv6, I think it's probably best to use
KAME, since that is what "all the others" in the BSD camp are using already. And as you probably know, it's not just a matter of "switching to IPv6", there's also the issue of running dual stack and deal with various transition technologies. What I hear more and more from ISPs is that they want to just push IPv6 to the end user and use NAT64/DNS64 to make IPv4 only services available - the implication of this is dropping native IPv4 on the customer side, but for a vast majority of users this is perfectly fine, since all major operating systems have been IPv6 ready for half a decade or more now. It's by far the easiest transition, is already implemented and proven to work well, and is also being deployed in a growing number of places (often for wireless networks with large number of clients)
Current estimate for IPv4 exhaustion is summer next year, we ("amiga land") are already a decade late in terms of what should have been done, and at least half a decade behind just about any other platform. Other hobbyist OSes already have projects for this, but none of the Amiga ones as far as I know. I'm just saying, the "switch" (as in "no more IPv4 address for you!") to IPv6 is predicted to become quite brutal in general, but many pretend that it's kinda like a Y2K problem that is all just hype, people have all kinds of weird theories as for why they think that it will never take off. For totally unprepared and happily ignorant Amiga users I suspect it will become quite entertaining... not only will there have to be a new IP stack, all the networking software will need to be rebuildt as well. Oh joy!

If I were completely free to make the software open, I could just dump the thing and leave it to its own devices.
And what guarantees are there that you wont do the same when selling it? I mean, seriously, it's not like it would be the first time in history of Amiga that this happens. I'll admit that your promises count alot more than most others, though.
My suspicion is that it would stay largely untouched and unloved. The whole premise that once a package is open sourced great things are inevitably going to happen to it is too optimistic.
That's totally beside the point, what is the point is that whoever willing then have a much better chance to fix whatever is bugging him/her without needing to contact some author who's no longer around, doesn't care anymore, no longer has the sources, has changed email address etc. as is the typical case for most 68k Amiga software. The point is to have the sources around so that there at least is a _chance_ to fix things when needed, by not having sources available you more or less guarantee that it will eventually be abandonware with dubious legal status, various incompatible dodgy binary patches etc. - all the stuff we hate about AmigaOS already.
I fix things in open source software all the time, but only rarely bother to contribute these fixes back upstream, as they're more quick work-arounds for my particual situations than anything else - I'm after all not a programmer. If there are stright out bugs, I do report them, but I don't think I'm at all qualified to suggest what the proper fix is, however quite alot of these bugs I can avoid simply by building the software with options to exclude the buggy part of the code, for example. Also, with open source software I can consult with programmers who are not involved with the code at all, to hear their oppinion on what might be wrong at a specific part of code - these things happen all the time and is what open source software is about.
Some funny things are possible with a 68k TCP/IP stack that runs inside the emulation rather than interfaces to the host's TCP/IP stack by means of a proxy.
Sure, but this is not something "most users" bother with.
The code that's hard-wired to WinUAE will stay AmiTCP V3 compatible until the bitter end.
Uhm, I dont get this part. The reason to stay AmiTCP V3 compatible is that this is what all software today use. Create an IPv6 stack tomorrow, it will still be the case. Nothing prevents an IPv6 capable bsdsocket.device in UAE. But on an emulator it is not so desperatly needed, due to perfectly functional IPv6 support in host OS. I run eUAE on Linux alot and the emulated Amiga can access filesystems I have made available over SSH, WebDAV, NFS, SMB, LUFS... over IPv6 as well as IPv4. And I prefer using hosts web browsers than messing around with mostly dysfunctional Amiga web browsers.
Anyways, WinUAE recently got A2065 emulation (iirc) - so anyone who want to play around with that can do so, but i really don't think there are many.
It's not as if you have to keep up with a boatload of code changes to keep this TCP/IP stack implementation reasonably robust and sound. One man can do it.
OK, I'm almost tempted to register in order to give you hell, then :laughing:
Btw - on a related note, people have been moaning about wireless stack for about half a decade as well now, feel free to port wpa_supplicant, opensea, open1x or make your own ... hohum... AirShow too. I can keep you busy there with testing and bug reports for years, really. And funny things are often needed to be changed in the IP stack as well when you start playing with wireless, the OSI model is after all just that - a model, in real life the layers typically become much more entangled

PS: Thanks for Term, although I admit I most often end up using VLTjr that doesn't suck up all that much RAM. I once started looking at how to strip off all the unneeded fluff in Term, but like so much I start doing on amiga, it never got far.