Heh. I don't mind if someone wants to try porting to IPv6 just for the fun of it, but it would be self-punishing work. The Netrek protocol does embed IPv4 and port numbers, so cascade to changes in the protocol and maybe changes to IPv4 clients to support the host fields shared to all clients. I'm not even sure if we support IPv4 properly. I'd rather play Netrek. ;-) On Thu, Apr 30, 2020 at 10:47:23PM -0700, Darrell Root wrote: > Thank you for the answers regarding the bots James! > > I’m not aware of any service providers blocking IPv4 resulting in an inability > to play Netrek. I don’t have a valid “business justification” for IPv6 support > other than being an IPv6 zealot with high regard for Netrek’s history in > IPv4-land ;-) > > Darrell > > On Apr 30, 2020, at 8:07 PM, James Cameron <[1]quozl at laptop.org> wrote: > > On Thu, Apr 30, 2020 at 05:40:01PM -0700, Darrell Root wrote: > > Netrek-dev: > > 1) My Swift/MacOS Netrek Client version 1.2 was just approved by Apple > AppReview, and is now available as an update in the MacOS App Store. > The only change is that it fixes the “choose team” bug. While MacOS > users will automatically within in a few days, I highly recommend > manually updating in the MacOS AppStore if you are playing in tonight’s > 6PM game on continuum. > > 2) Netrek-dev server bot question: When running a netrek server > with bots, are the bots built in to the server? Or are the bots > separate processes running on the server and talking to the server > over the localhost network? > > Some robots use shared memory to interact with the server. > > Some robots use the network connection, which can be localhost or from > another host, depending on the configuration. > > 3) IPv6: I’m under the impression that nobody has ever played Netrek > over IPv6 because none of the netrek server codebases support IPv6. Is > that correct? Asking for a friend… > > Yes, the code supports IPv4. As far as I can see there's no need to > support IPv6, but if you know of enough service providers blocking > IPv4, let me know. > > Thanks! > > Darrell > > _______________________________________________ > netrek-dev mailing list > [2]netrek-dev at us.netrek.org > [3]http://mailman.us.netrek.org/mailman/listinfo/netrek-dev > > -- > James Cameron > [4]http://quozl.netrek.org/ > _______________________________________________ > netrek-dev mailing list > [5]netrek-dev at us.netrek.org > [6]http://mailman.us.netrek.org/mailman/listinfo/netrek-dev > > References: > > [1] mailto:quozl at laptop.org > [2] mailto:netrek-dev at us.netrek.org > [3] http://mailman.us.netrek.org/mailman/listinfo/netrek-dev > [4] http://quozl.netrek.org/ > [5] mailto:netrek-dev at us.netrek.org > [6] http://mailman.us.netrek.org/mailman/listinfo/netrek-dev > _______________________________________________ > netrek-dev mailing list > netrek-dev at us.netrek.org > http://mailman.us.netrek.org/mailman/listinfo/netrek-dev -- James Cameron http://quozl.netrek.org/