Thursday November 28 2013 10:03, Benny Pedersen wrote to you:
AL>> Both of my systems are on the same IPv4 address, and only one of AL>> the supports IPv6.
Ah, that is an interseting configuration that I did not foresee when I 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.
If this situation is permanent, rather than just a experiment, I suggest that instead of separate host names for IPv4 and IPv6, you use separate host names for the different systems. Example: Use bnbbbs.net for 320/119 and phoenix.bnbbbs.net for 320/219. Attach just an A record to bnbbbbs.net and both the A and AAAA records to phoenix.bnbbbs.net
The only snag is that in that case, you'd have to make the ipv6 part listen on port 24555 instead of 24554.
A third solution would be to add an extra node number - say 320/319 for the IPv6 experiment and list it with an INO4 flag to signal no IPv4.
But the "grand" solution of course is to enable IPv6 for your other system as well...;-)
