• My turn for testing IPv6...

    From RJ Clay@1:120/544 to Andrew Leary on Sat Aug 15 10:23:03 2015
    * Replying to a msg in IPV6 (IPv6 Discussions)

    Hi Andrew!

    09 Aug 15 13:54, I wrote to you:

    02 Aug 15 16:35, you wrote to me:
    02 Aug 15 13:48, you wrote to me:

    Excellant! Now just need to test outbound FTN IPv6 connects,
    and how to do that with the programs I have available... (MBSE
    BBS, BinkD, Qico.)

    MBSE will use IPv6 first, and then fall back to IPv4 if
    necessary, assuming that the hostname has both A and AAAA
    records.

    What else might be needed for that? Because on a Debian 8 install
    of v1.04, a poll attempt to your system went via IPv4. (I'll check
    the settings I was using, and follow up as necessary in the MBSE
    echo...)

    I tried your 1:320/219 node as well and it still went out via IPv4. Is it really MBSE that "will use IPv6 first"? Or it perhaps related to OS settings? The new system hosting 1:120/545 is a 64bit system on Debian 8.


    It is not
    currently possible to specify a literal IPv6 address in the
    hostname field of a node record (I'm working on changing that.)

    I'll be updating the install to the new version (v1.06) at
    1:120/545 when I have a chance so I can test that.

    I can ping6 your system with no issue so I'll be testing that.





    Jame

    --- GoldED+/LNX 1.1.5-b20110213
    * Origin: ftn.rocasa.net (1:120/544)
  • From RJ Clay@1:120/544 to Andrew Leary on Sat Aug 15 11:14:06 2015
    Hi Andrew!

    15 Aug 15 10:23, I wrote to you:

    09 Aug 15 13:54, I wrote to you:
    02 Aug 15 16:35, you wrote to me:

    MBSE will use IPv6 first, and then fall back to IPv4 if
    necessary, assuming that the hostname has both A and AAAA
    records.

    What else might be needed for that? Because on a Debian 8
    install of v1.04, a poll attempt to your system went via IPv4.
    (I'll check the settings I was using, and follow up as necessary
    in the MBSE echo...)

    I tried your 1:320/219 node as well and it still went out via IPv4.
    Is it really MBSE that "will use IPv6 first"? Or it perhaps related to
    OS settings? The new system hosting 1:120/545 is a 64bit system on
    Debian 8.

    Turned out to be an OS setting, at least on my system; I'd forgotten that I'd set it to default to IPv4 connections (/etc/gai.conf) when I first set the system up at home (so I could work on it; that's not where it's now deployed) because I still do not have reliable IPv6 connectivity there.





    Jame



    --- GoldED+/LNX 1.1.5-b20110213
    * Origin: ftn.rocasa.net (1:120/544)