Subj : IPv6
To   : Michiel van der Vlist
From : Andrew Leary
Date : Fri Nov 29 2013 11:22:54

Hello Michiel!

29 Nov 13 12:03, you wrote to me:

 AL>>> Both of my systems are on the same IPv4 address, and only one of
 AL>>> the supports IPv6.

 MV> Ah, that is an interseting configuration that I did not foresee when I
 MV> proposed the INO4 flag...

 AL>>> Using a separate hostname allows me to ensure that all
 AL>>> IPv6 traffic ends up going to the host that supports IPv6.

 MV> If this situation is permanent, rather than just a experiment, I
 MV> suggest that instead of separate host names for IPv4 and IPv6, you use
 MV> separate host names for the different systems. Example: Use bnbbbs.net
 MV> for 320/119 and phoenix.bnbbbs.net for 320/219. Attach just an A
 MV> record to bnbbbbs.net and both the A and AAAA records to
 MV> phoenix.bnbbbs.net

That's not a bad idea...  I'll work on that later.

 MV> The only snag is that in that case, you'd have to make the ipv6 part
 MV> listen on port 24555 instead of 24554.

That should be as simple as changing the port number assignment in 
/etc/services, so that won't be much of an issue.

 MV> A third solution would be to add an extra node number - say 320/319
 MV> for the IPv6 experiment and list it with an INO4 flag to signal no
 MV> IPv4.

 MV> But the "grand" solution of course is to enable IPv6 for your other
 MV> system as well...;-)

1:320/119 still runs under OS/2, which does not, and probably never will, 
support IPv6.

Andrew

--- GoldED+/LNX 1.1.5-b20130111
 * Origin: Phoenix BBS * bnbbbs.net:2323 (1:320/219)

.