On Aug 17, 2016 06:35pm, Michiel van der Vlist wrote to Allen Prunty:

MvdV> Hello Allen,

MvdV> On Wednesday August 17 2016 13:56, I wrote to you:

Ping-Statistik f?r 2602:306:83c1:a710:ed7c:8816:bcf9:e243:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4 (100% Verlust),

So no cigar yet...

Are you sure the IPv6 address is correct?

MvdV> Can we discuss this in the IPV6 echo?

Moving it there. that's the ipv6 my provider says to use for now... I've got it set to dynamically change.... if you can try to hit at ipv6.livewirebbs.com I would be greatful... check binkp port and telnet if you can.

Allen

... FSX Net to me means... Friendship, Simplicity, and Xcellence
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: LiveWire -=* Louisville, KY USA *=- LiveWireBBS.Com (1:2320/100)

Hello Allen,

On Wednesday August 17 2016 14:37, you wrote to me:

Moving it there. that's the ipv6 my provider says to use for now...
I've got it set to dynamically change.... if you can try to hit at ipv6.livewirebbs.com I would be greatful... check binkp port and
telnet if you can.

binkp works:

+ 20:48 [1684] call to 1:2320/100@fidonet
20:48 [1684] trying ipv6.livewirebbs.com [2602:306:83c1:a710:9d54:ff3c:6d09:1fcf]...
20:48 [1684] connected
+ 20:48 [1684] outgoing session with ipv6.livewirebbs.com:24554 [2602:306:83c1:a710:9d54:f
f3c:6d09:1fcf]
- 20:48 [1684] SYS LiveWire BBS
- 20:48 [1684] ZYZ Allen Prunty
- 20:48 [1684] LOC Parts Unknown, KY, USA
- 20:48 [1684] NDL 115200,TCP,BINKP
- 20:48 [1684] TIME Wed, 17 Aug 2016 14:48:48 -0400
- 20:48 [1684] VER binkd/1.1a-94/Win32 binkp/1.1
+ 20:48 [1684] addr: 1:2320/0@fidonet
+ 20:48 [1684] addr: 1:2320/100@fidonet
+ 20:48 [1684] addr: 21:1/148@fsxnet (n/a or busy)
+ 20:48 [1684] addr: 44:502/0@dorenet (n/a or busy)
+ 20:48 [1684] addr: 80:774/9@retronet (n/a or busy)
+ 20:48 [1684] addr: 115:1502/224@pascal-net (n/a or busy)
+ 20:48 [1684] addr: 901:1/12@dixienet (n/a or busy)
- 20:48 [1684] OPT EXTCMD GZ
+ 20:48 [1684] Remote supports EXTCMD mode
+ 20:48 [1684] Remote supports GZ mode
+ 20:48 [1684] done (to 1:2320/100@fidonet, OK, S/R: 0/0 (0/0 bytes))
20:48 [1684] session closed, quitting...

Congratulations, welcome to the Fiofonet IPv6 club.

Just a few points.

Having two different host names for IPv4 and IPv6 is undesirable. Just add both the A an the AAAA record to fido.livewirebbs.com and callers will sort out automatically if they should use IPv4 or IPv6.

I still would like to see the result of your ipconfig. I wonder why you need to set the address to dynamic. You may be using PE (Privacy Extension) address for the AAAA record. That is wrong. In a windopws environmemt with PE enabled, the address used for outgoing changes every 24 hour or so. What should be in the AAAA record is the SLAAC address. A SLAAC address is derived from the MAC address and it is recognisable by the ff fe in between.

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: he.net certified sage (2:280/5555)

Allen Prunty wrote to Michiel van der Vlist <=-

Moving it there. that's the ipv6 my provider says to use for now...
I've got it set to dynamically change.... if you can try to hit at ipv6.livewirebbs.com I would be greatful... check binkp port and telnet
if you can.

Off to a promising start. :-)

C:\vmware>ping ipv6.livewirebbs.com

Pinging ipv6.livewirebbs.com [2602:306:83c1:a710:9d54:ff3c:6d09:1fcf] with 32
y
tes of data:
Reply from 2602:306:83c1:a710:9d54:ff3c:6d09:1fcf: time=442ms
Reply from 2602:306:83c1:a710:9d54:ff3c:6d09:1fcf: time=274ms
Reply from 2602:306:83c1:a710:9d54:ff3c:6d09:1fcf: time=272ms
Reply from 2602:306:83c1:a710:9d54:ff3c:6d09:1fcf: time=273ms

Ping statistics for 2602:306:83c1:a710:9d54:ff3c:6d09:1fcf:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 272ms, Maximum = 442ms, Average = 315ms


binkp is listening

root@lemaker:~# telnet ipv6.livewirebbs.com 24554
Trying 2602:306:83c1:a710:9d54:ff3c:6d09:1fcf...
Connected to ipv6.livewirebbs.com.
Escape character is '^]'.
SYS LiveWire BBSZYZ Allen PruntyOC Parts Unknown, KY, USANDL 115200,TCP,BINKP%TIME Wed, 17 Aug 2016 17:59:31 -0400"VER binkd/1.1a-94/Win32 binkp/1.1 1:2320/0@fidonet 1:2320/100@fidonet 21:1/148@fsxnet 44:502/0@dorenet 80:774/9@retronet 115:1502/224@pascal-net 901:1/12@dixienet^]
telnet> quit
Connection closed.


Telnet not so good, unless you're using a non standard port.

root@lemaker:~# telnet ipv6.livewirebbs.com
Trying 2602:306:83c1:a710:9d54:ff3c:6d09:1fcf...
telnet: Unable to connect to remote host: Connection refused

... The four food groups: coffee, ice cream, beer and pizza.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

Michiel van der Vlist wrote to Allen Prunty <=-

Having two different host names for IPv4 and IPv6 is undesirable. Just add both the A an the AAAA record to fido.livewirebbs.com and callers will sort out automatically if they should use IPv4 or IPv6.

I agree that the primary hostname should have both A and AAAA records. There are reasons to have extra IPv4 and possibly IPv6 only records. The most common being where some of your services only run on IPv4, having an A record (e.g. ipv4.yourdomain.com) can prevent delays for IPv6 capable hosts that attempt to connect. But the main hostname should have A and AAAA records.

I'm using separate hostnames for binkp and telnet for this reaason. When I get around to upgrading the BBS and it can use IPv6, I won't need to do this. Similarly, one of my feeds is IPv6 capable. However, my feed was on a secondary mailer, which didn't support IPv6 at the time. This caused long delays on my end, until he added an IPv4 only hostname, which I switched to. The software has since been upgraded on his end, and I've gone back to polling the main IPv4/IPv6 hostname, now that his end answers on IPv6.


... Crayons can take you more places than starships. * Guinan
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

Hello Tony,

On Thursday August 18 2016 08:13, you wrote to me:

Having two different host names for IPv4 and IPv6 is
undesirable. Just add both the A an the AAAA record to
fido.livewirebbs.com and callers will sort out automatically if
they should use IPv4 or IPv6.

I agree that the primary hostname should have both A and AAAA records.

Yes, that would be the normal situation wouldn't it? I did not want to confuse Allen with the exceptions. Yet...

There are reasons to have extra IPv4 and possibly IPv6 only records.
The most common being where some of your services only run on IPv4,

Or only on IPv6...

having an A record (e.g. ipv4.yourdomain.com) can prevent delays for
IPv6 capable hosts that attempt to connect. But the main hostname
should have A and AAAA records.

I'm using separate hostnames for binkp and telnet for this reaason.
When I get around to upgrading the BBS and it can use IPv6, I won't
need to do this.

Yes, if not alle services support both IPv4 and IPv6 a seperate host name is a good idea.

Similarly, one of my feeds is IPv6 capable. However,
my feed was on a secondary mailer, which didn't support IPv6 at the
time. This caused long delays on my end,

Yes, that can happen when software is led to believe IPv6 is available when it is not.

until he added an IPv4 only hostname, which I switched to. The
software has since been upgraded on his end, and I've gone back to
polling the main IPv4/IPv6 hostname, now that his end answers on IPv6.

I am aware of it. In fact Kees van Eeten and me in our joint hunt for Fidonet potential IPv6 nodes often see this. He has a script that hunts for AAAA records in the nodelist that have not been tagged as IPv6 capable yet.

I then poll the node and sometimes I get an IPv6 connect. But more often this is what happens:

+ 00:49 [1716] call to 1:214/22@fidonet
00:49 [1716] trying f22.n214.z1.binkp.net [2602:306:bd31:aa50:e23f:49ff:fead:fa9]...
? 00:49 [1716] connection to 1:214/22@fidonet failed: {W32 API error
10060} Connection timed out
00:49 [1716] trying f22.n214.z1.binkp.net [104.49.12.129]:24554...
00:49 [1716] connected
+ 00:49 [1716] outgoing session with f22.n214.z1.binkp.net:24554 [104.49.12.129]
- 00:49 [1716] OPT CRAM-MD5-09ad8527aabc6275ef9509f2545471ee
+ 00:49 [1716] Remote requests MD mode
- 00:49 [1716] SYS US 99 BBS

There is an AAAA record, but no server answering on IPv6. Robots have patience so in this case it is no big deal. But if the caller is human, the one minute delay can be very annoying.

When this happens, I get in touch with the sysop. Some times it leads to nothing. Some other times it leads to another entry in the list of IPv6 capable nodes. ;-)


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: he.net certified sage (2:280/5555)

On Aug 18, 2016 12:43am, Michiel van der Vlist wrote to Tony Langdon:

MvdV> Hello Tony,

MvdV> On Thursday August 18 2016 08:13, you wrote to me:

Having two different host names for IPv4 and IPv6 is
undesirable. Just add both the A an the AAAA record to
fido.livewirebbs.com and callers will sort out automatically if
they should use IPv4 or IPv6.

I agree that the primary hostname should have both A and AAAA records.

MvdV> Yes, that would be the normal situation wouldn't it? I did not want
MvdV> to confuse Allen with the exceptions. Yet...

My provider does not allow A and AAAA records yet as they are just "testing" ipv6. It's coming they assure us and when they get it nailed down it will be
a dual a and aaaa record.

Right now they are telling me to test under the ipv6 domain first.

Allen

... FSX Net to me means... Friendship, Simplicity, and Xcellence
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: LiveWire -=* Louisville, KY USA *=- LiveWireBBS.Com (1:2320/100)

Hello Allen,

On Wednesday August 17 2016 19:18, you wrote to me:

I agree that the primary hostname should have both A and AAAA
records.

MvdV>> Yes, that would be the normal situation wouldn't it? I did not
MvdV>> want to confuse Allen with the exceptions. Yet...

My provider does not allow A and AAAA records yet as they are just "testing" ipv6.

Eh???

Your internet access provider is the one that provides your physical connection to the internet. Your DNS provider is the one that provides the link between the host names on your domain and the (Ipv4 and IPv6) IP addresses.

They can be one and the same, but ever so often they are not. If your DNS provider is still "just testing" and does not allow both an A record and an AAAA record for a given host name, then vote with your feet.

It's coming they assure us and when they get it
nailed down it will be a dual a and aaaa record.

Don't wait for them, vote with your feet. There are plenty of DSN providers who offer full DNS support (IPv6 and IPv4) and have been doing that for years. DNS is independant of internet access.

Right now they are telling me to test under the ipv6 domain first.

Tell them they are at least half a decade late if they can not handle dual protocol records.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: he.net certified sage (2:280/5555)