Hello All,

Here is an update. I have listed Allen Prunty as OO as he does noty yet have an host name in the nodelist with an AAAA record, so he can not accept incoming IPv6 by means gleened from the nodelist only.

Mattias Larsson in not in the nodelist yet, so he is listed as a prospective member.



=== Cut ===
List of Ipv6 nodes
By Michiel van der Vlist, 2:280/5555

Updated 18 August 2016


Node Nr. Sysop Type Provider Remark

1 2:280/464 Wilfred van Velzen Native Xs4All
2 2:280/5003 Kees van Eeten Native Xs4All
3 2:5019/40 Konstantin Kuzov T-6in4 he.net PO4
4 2:240/1661 Markus Reschke Native DTAG
5 2:280/5555 Michiel van der Vlist Native Ziggo
6 1:320/219 Andrew Leary Native Comcast
7 2:221/0 Tommi Koivula T-6in4 he.net
8 2:221/1 Tommi Koivula T-6in4 he.net
9 2:221/6 Tommi Koivula T-6in4 he.net
10 2:5053/54 Denis Mikhlevich Native TTK-Volga
11 2:5030/257 Vova Uralsky T-6in4 he.net
12 1:154/10 Nicholas Bo‰l Native TWC
13 2:203/0 Bj”rn Felten T-6in4 SixXs
14 2:280/5006 Kees van Eeten Native Xs4All INO4
15 3:712/848 Scott Little T-6RD iiNet
16 2:5020/545 Alexey Vissarionov Native Hetzner
17 1:103/17 Stephen Hurd T-6in4 he.net
18 2:5020/9696 Alexander Skovpen T-6to4 he.net
19 2:301/812 Benoit Panizzon Native IMPNET
20 2:421/790 Viktor Cizek Native T-Mobile
21 2:222/2 Kim Heino Native TeliaSonera
22 3:633/280 Stephen Walsh Native Ransom IT
23 1:266/404 Bill McGarrity Native Comcast
24 4:902/26 Fernando Toledo T-AYIY SixXs
25 2:463/877 Alex Shuman Native Nline IO
26 2:280/2000 Michael Trip Native Choopa
27 1:19/10 Matt Bedynek T-6in4 he.net
28 1:249/303 Joe Delahaye Native Teksavvy
29 2:280/1043 Michel van Osenbruggen Native Bit
39 3:770/1 Paul Hayton T-AYIY SixXs
31 2:5053/58 Alexandr Kruglikov Native CJSC The First
32 1:103/13 Stephen Hurd Native Choopa
33 1:120/545 RJ Clay Native DC74L
34 3:633/281 Stephen Walsh T-6in4 he.net
35 2:310/31 Richard Menedetter T-6in4 SixXs
36 3:633/410 Tony Langdon Native IINET
37 2:5005/33 Evgeny Zyatkov T-6in4 he.net PO4
38 2:5020/329 Oleg Lukashin Native Comfortel
39 3:772/100 James Kelly Native 2degrees
40 2:246/1305 Emil Schuster Native TAL.DE
41 2:2443/1313 Dirk Astrath Native VOLMARNET
42 2:2448/4000 Tobias Burchhardt Native DTAG IO
43 2:331/51 Marco d'Itri Native BOFH-IT
44 2:203/210 Mattias Larsson T-6in4 he.net PM
45 1:2320/100 Allen Prunty Native AT&T OO


T-6in4 Static 6in4
T-AYIY Dynamic AYIYA
T-6to4 6to4
T-6RD 6RD

Remarks:

IO Incoming only (Node can not make outgoing IPv6 calls)
OO Outgoing only (Node can not accept incoming IPv6 calls)
INO4 No IPv4 (Node can not accept incoming IPv4 calls)
PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
but is configured to try IPv4 first)
6DWN The IPv6 connectivity of this node is temporarely down.
DOWN This node is temporarely down for both IPv4 and IPv6
PM Prospective Member. The node has demonstrated IPv6
capability but is not yet listed in de Fidonet nodelist.


Notes:

To make an IPv6 connection to a node connected via 6to4 tunneling
one may have to force the mailer into IPv6 (-6 option in binkd's
node config). If the destination address is a 6to4 tunnel address
(2002::/16) Windows defaults to IPv4 if an IPv4 address is present.



=== Cut ===


Cheers, Michiel

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

On Aug 18, 2016 02:10pm, Michiel van der Vlist wrote to All:

MvdV> Hello All,

MvdV> Here is an update. I have listed Allen Prunty as OO as he does noty
MvdV> yet have an host name in the nodelist with an AAAA record, so he can
MvdV> not accept incoming IPv6 by means gleened from the nodelist only.

MvdV> Mattias Larsson in not in the nodelist yet, so he is listed as a
MvdV> prospective member.

ipv6.livewirebbs.com should do it. And my provider is technically lightspeed... which is a bit different than the stock at&t.

Allen



MvdV> === Cut ===
MvdV> List of Ipv6 nodes
MvdV> By Michiel van der Vlist, 2:280/5555

MvdV> Updated 18 August 2016


MvdV> Node Nr. Sysop Type Provider Remark

MvdV> 1 2:280/464 Wilfred van Velzen Native Xs4All
MvdV> 2 2:280/5003 Kees van Eeten Native Xs4All
MvdV> 3 2:5019/40 Konstantin Kuzov T-6in4 he.net PO4
MvdV> 4 2:240/1661 Markus Reschke Native DTAG
MvdV> 5 2:280/5555 Michiel van der Vlist Native Ziggo
MvdV> 6 1:320/219 Andrew Leary Native Comcast
MvdV> 7 2:221/0 Tommi Koivula T-6in4 he.net
MvdV> 8 2:221/1 Tommi Koivula T-6in4 he.net
MvdV> 9 2:221/6 Tommi Koivula T-6in4 he.net
MvdV> 10 2:5053/54 Denis Mikhlevich Native TTK-Volga
MvdV> 11 2:5030/257 Vova Uralsky T-6in4 he.net
MvdV> 12 1:154/10 Nicholas Bo‰l Native TWC
MvdV> 13 2:203/0 Bj”rn Felten T-6in4 SixXs
MvdV> 14 2:280/5006 Kees van Eeten Native Xs4All INO4
MvdV> 15 3:712/848 Scott Little T-6RD iiNet
MvdV> 16 2:5020/545 Alexey Vissarionov Native Hetzner
MvdV> 17 1:103/17 Stephen Hurd T-6in4 he.net
MvdV> 18 2:5020/9696 Alexander Skovpen T-6to4 he.net
MvdV> 19 2:301/812 Benoit Panizzon Native IMPNET
MvdV> 20 2:421/790 Viktor Cizek Native T-Mobile
MvdV> 21 2:222/2 Kim Heino Native TeliaSonera
MvdV> 22 3:633/280 Stephen Walsh Native Ransom IT
MvdV> 23 1:266/404 Bill McGarrity Native Comcast
MvdV> 24 4:902/26 Fernando Toledo T-AYIY SixXs
MvdV> 25 2:463/877 Alex Shuman Native Nline IO
MvdV> 26 2:280/2000 Michael Trip Native Choopa
MvdV> 27 1:19/10 Matt Bedynek T-6in4 he.net
MvdV> 28 1:249/303 Joe Delahaye Native Teksavvy
MvdV> 29 2:280/1043 Michel van Osenbruggen Native Bit
MvdV> 39 3:770/1 Paul Hayton T-AYIY SixXs
MvdV> 31 2:5053/58 Alexandr Kruglikov Native CJSC The First
MvdV> 32 1:103/13 Stephen Hurd Native Choopa
MvdV> 33 1:120/545 RJ Clay Native DC74L
MvdV> 34 3:633/281 Stephen Walsh T-6in4 he.net
MvdV> 35 2:310/31 Richard Menedetter T-6in4 SixXs
MvdV> 36 3:633/410 Tony Langdon Native IINET
MvdV> 37 2:5005/33 Evgeny Zyatkov T-6in4 he.net PO4
MvdV> 38 2:5020/329 Oleg Lukashin Native Comfortel
MvdV> 39 3:772/100 James Kelly Native 2degrees
MvdV> 40 2:246/1305 Emil Schuster Native TAL.DE
MvdV> 41 2:2443/1313 Dirk Astrath Native VOLMARNET
MvdV> 42 2:2448/4000 Tobias Burchhardt Native DTAG IO
MvdV> 43 2:331/51 Marco d'Itri Native BOFH-IT
MvdV> 44 2:203/210 Mattias Larsson T-6in4 he.net PM
MvdV> 45 1:2320/100 Allen Prunty Native AT&T OO


MvdV> T-6in4 Static 6in4
MvdV> T-AYIY Dynamic AYIYA
MvdV> T-6to4 6to4
MvdV> T-6RD 6RD

MvdV> Remarks:

MvdV> IO Incoming only (Node can not make outgoing IPv6 calls)
MvdV> OO Outgoing only (Node can not accept incoming IPv6 calls)
MvdV> INO4 No IPv4 (Node can not accept incoming IPv4 calls)
MvdV> PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
MvdV> but is configured to try IPv4 first)
MvdV> 6DWN The IPv6 connectivity of this node is temporarely down.
MvdV> DOWN This node is temporarely down for both IPv4 and IPv6
MvdV> PM Prospective Member. The node has demonstrated IPv6
MvdV> capability but is not yet listed in de Fidonet nodelist.


MvdV> Notes:

MvdV> To make an IPv6 connection to a node connected via 6to4 tunneling
MvdV> one may have to force the mailer into IPv6 (-6 option in binkd's
MvdV> node config). If the destination address is a 6to4 tunnel address
MvdV> (2002::/16) Windows defaults to IPv4 if an IPv4 address is present.



MvdV> === Cut ===


MvdV> Cheers, Michiel

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

... The greatest enemy of creatitivy is staying inside your comfort zone
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: LiveWire -=* Louisville, KY USA *=- LiveWireBBS.Com (1:2320/100)

Hello Allen,

On Saturday August 20 2016 07:54, you wrote to me:

On Aug 18, 2016 02:10pm, Michiel van der Vlist wrote to All:

MvdV>> Here is an update. I have listed Allen Prunty as OO as he does
MvdV>> noty yet have an host name in the nodelist with an AAAA record,
MvdV>> so he can not accept incoming IPv6 by means gleened from the
MvdV>> nodelist only.

ipv6.livewirebbs.com should do it.

It does, but that host name is not in the nodelist and it does not carry an A record.

And my provider is technically lightspeed...

Which provider? You internet access provider of you DNS provider? As I already tried to explain to you, there is a difference. The internet access provider is the one that arranges for your access to the internet. It is them that issue you your IP number(s). If I do a whois for 2602:306:83c1:a710::48 or 104.60.26.113, I end up with AT&T,

Your DNS provider OTOH, does not issue IP numbers. What the DNS provider does is list you in the "telephone book of the internet". The make the link between yous host name and your IP address(es). If I do a whois on livewirebbs.com I end up with VITALWERKS INTERNET SOLUTIONS.

Any decent DNS provider should have the option of attaching both an A (IPv4) and AAAA (Ipv6) record to a host name. If they can't provide that servive, vote with your feet.

In the meantime I have done something to help you out. I have created livewirebbs.vlist.eu. It has an A and an AAAA record attached that points to your binkp server. That should work as long as your IP addresses don't change. So have that in the nodelist and you qualify as a fully fledged member of the IPv6 Fidonet club.

Feel free to use livewirebbs.vlist,eu for as long as you need.

And than either get VITALWORKS to get their stuff fixed ASAP, or take your DNS bussines elsewhere.


Cheers, Michiel

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

Michiel van der Vlist mumbled to All.. <=-

Hello All,

Here is an update. I have listed Allen Prunty as OO as he does noty yet have an

host name in the nodelist with an AAAA record, so he can not accept incoming IPv6 by means gleened from the nodelist only.

Mattias Larsson in not in the nodelist yet, so he is listed as a prospective member.

Finally got my Fido feed hooked back up. I'm ipv6 capable as well, and my domains have both A and AAAA records.

I imagine I'll be back in the nodelist within the next couple weeks. :)

domains: warensemble.com bbs.warensemble.com binkp.warensemble.com

(all point to the same IPs for now. I separated them just in case I want to move them to different machines later)




Mike

... Ambition is the curse of the political class.
=== MultiMail/Linux v0.50
--- SBBSecho 3.00-Linux
* Origin: War Ensemble - warensemble.com - Appleton, WI (1:154/30)

Hello Mike,

On 23 Aug 16 00:00, Mike Miller wrote to Michiel van der Vlist:

I imagine I'll be back in the nodelist within the next couple weeks.
:)

FYI, if all goes as planned you will be in the nodelist this week.

domains: warensemble.com bbs.warensemble.com binkp.warensemble.com

(all point to the same IPs for now. I separated them just in case I
want to move them to different machines later)

You might want to take the AAAA record off one of those to give to IPv4 links, due to trying IPv6 first and falling back to IPv4 can cause non-necessary delays.

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20160322
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Nicholas Boel mumbled to Mike Miller.. <=-

Hello Mike,

On 23 Aug 16 00:00, Mike Miller wrote to Michiel van der Vlist:

I imagine I'll be back in the nodelist within the next couple weeks.
:)

FYI, if all goes as planned you will be in the nodelist this week.

Hooray! I send a facebook message to the guy who had my node number before me, telling him I stole his address (Jon Verrett of Flashpoint BBS). :)
I've known him for as long as I've been BBSing.

domains: warensemble.com bbs.warensemble.com binkp.warensemble.com

(all point to the same IPs for now. I separated them just in case I
want to move them to different machines later)

You might want to take the AAAA record off one of those to give to IPv4 links, due to trying IPv6 first and falling back to IPv4 can cause non-necessary delays.

Hey, if there's a delay, someone needs to fix their setup, that's on their end, not mine! :D

Seriously though, if it becomes an issue I can either set up a ipv6 subdomain, or just drop it off the nodelisted domain.



Mike

... MODEM? I've been calling this BBS with a Tarot deck.
=== MultiMail/Linux v0.50
--- SBBSecho 3.00-Linux
* Origin: War Ensemble - warensemble.com - Appleton, WI (1:154/30)

Hello Mike,

On 23 Aug 16 17:21, Mike Miller wrote to Nicholas Boel:

FYI, if all goes as planned you will be in the nodelist this
week.

Hooray! I send a facebook message to the guy who had my node number before me, telling him I stole his address (Jon Verrett of Flashpoint BBS). :) I've known him for as long as I've been BBSing.

I vaguely remember trying to reach out to him while his system was still up and I was merging nets 139 and 154 to form one Wisconsin net. I don't think I got a response at the time.

domains: warensemble.com bbs.warensemble.com
binkp.warensemble.com

(all point to the same IPs for now. I separated them just in case
I want to move them to different machines later)

You might want to take the AAAA record off one of those to give
to IPv4 links, due to trying IPv6 first and falling back to IPv4
can cause non-necessary delays.

Hey, if there's a delay, someone needs to fix their setup, that's on their end, not mine! :D

Well, seeing as though more than half of the world still doesn't have IPv6, I would expect to see them. Heck you may not even notice it as your mailer will only tell you when there's an actual connection. But if/when others complain is when I did something about it. :)

Seriously though, if it becomes an issue I can either set up a ipv6 subdomain, or just drop it off the nodelisted domain.

I went more with option number one. I have three domains: pharcyde.org (@, A, AAAA records), bbs.pharcyde.org (only an A record), and binkp.pharcyde.org (setup the same as the @). I use binkp.pharcyde.org in the nodelist, and if anyone has an issue I tell them to use bbs.pharcyde.org. A lot of my links are setup direct these days anyways, so I've discussed connection methods with most of them by now. :)

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20160322
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Mike Miller wrote to Nicholas Boel <=-

You might want to take the AAAA record off one of those to give to IPv4 links, due to trying IPv6 first and falling back to IPv4 can cause non-necessary delays.

Hey, if there's a delay, someone needs to fix their setup, that's on their end, not mine! :D

The only time you would normally get a delay is if the BBS is not listening on IPv6, but has an AAAA record. Then IPv6 capable hosts will experience a delay as they try a non existent IPv6 service, before falling back to IPv4.

IPv4 hosts aren't affected. They'll simply look up the A record and make an IPv4 connection straight away.

Seriously though, if it becomes an issue I can either set up a ipv6 subdomain, or just drop it off the nodelisted domain.

Shouldn't have any issues, provided you're listening on both IPv4 and IPv6.


... I'm a soldier, not a diplomat. I can only tell the truth.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

Hello Tony!

24 Aug 16 12:47, you wrote to me:

You might want to take the AAAA record off one of those to give
to IPv4 links, due to trying IPv6 first and falling back to IPv4
can cause non-necessary delays.

Hey, if there's a delay, someone needs to fix their setup,
that's on their end, not mine! :D

The only time you would normally get a delay is if the BBS is not listening on IPv6, but has an AAAA record. Then IPv6 capable hosts
will experience a delay as they try a non existent IPv6 service,
before falling back to IPv4.

IPv4 hosts aren't affected. They'll simply look up the A record and
make an IPv4 connection straight away.

Yeah, services are listening on both IPs. At least, the ones that matter.



Mike


=== GoldED+/LNX 1.1.5-b20160322
# Origin: warensemble.com - Appleton, WI (1:154/30)
--- SBBSecho 3.00-Linux
* Origin: War Ensemble - warensemble.com - Appleton, WI (1:154/30)

Mike Miller wrote to Tony Langdon <=-

Yeah, services are listening on both IPs. At least, the ones that
matter.

Cool. The dual A and AAAA records should be fine. :-)


... Computer Hacker wanted. Must have own axe.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

Hello Mike,

On Tuesday August 23 2016 00:00, you wrote to me:

Finally got my Fido feed hooked back up. I'm ipv6 capable as well,
and my domains have both A and AAAA records.

I noticed. I also noticed that your binkp server accepts IPv6 incoming connections.

I imagine I'll be back in the nodelist within the next couple weeks.
:)

Weeks!!? Does your Net/Region not participate in de DAILYLST project?

domains: warensemble.com bbs.warensemble.com binkp.warensemble.com

(all point to the same IPs for now. I separated them just in case I
want to move them to different machines later)

For the same reason I use seperate host name for my http en binkd servers.

Anyway, pending nodelist entry, I have entered you in thelist of Fidonet IPv6 capable nodes as a prospective member.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: Michiel's laptop (2:280/5555.1)

Hello Tony,

On Wednesday August 24 2016 12:47, you wrote to Mike Miller:

Hey, if there's a delay, someone needs to fix their setup,
that's on their end, not mine! :D

The only time you would normally get a delay is if the BBS is not listening on IPv6, but has an AAAA record. Then IPv6 capable hosts
will experience a delay as they try a non existent IPv6 service,
before falling back to IPv4.

Yes, that would cause a dalay. But it is not the only way dalays can occur.

IPv4 hosts aren't affected. They'll simply look up the A record and
make an IPv4 connection straight away.

Properly set up IPv4 systems are not affected.

But what also can happen is that the servers supports and advertises IPv6 and the client just /thinks/ it has IPv6 connectivity. 6to4 and Teredo tunnels are notorious for this. The client tries IPv6 first, but gets no connection because it does not have a working IPv6 connection.

Teredo is history, or at least it should be, Microsoft shut off their Teredo servers.

6to4 is still among us....


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: Michiel's laptop (2:280/5555.1)

Hi Michiel!

Aug 24 14:51 2016, Michiel van der Vlist wrote to Mike Miller:

MvdV> Weeks!!? Does your Net/Region not participate in de DAILYLST
MvdV> project?

YEARLYST :)

(all point to the same IPs for now. I separated them just in case I
want to move them to different machines later)

MvdV> For the same reason I use seperate host name for my http en binkd
MvdV> servers.

Yep, using dedicated names for each service makes life very simple. Less trouble when moving services around. Recently I switched to another server hoster and was able to move each service step by step resulting in a smooth migration.

If someone got problems finding an IPv4/IPv6 DynDNS provider and is able to run bind's nsupdate or ssh, I might help with a subdomain. This offer is meant as a last resort. I don't want to run that for the whole Fidonet :) Or if you need a secondary nameserver, drop me a netmail.

ciao,
Markus

---
* Origin: *** theca tabellaria *** (2:240/1661)

Michiel van der Vlist wrote to Tony Langdon <=-

Yes, that would cause a dalay. But it is not the only way dalays can occur.

IPv4 hosts aren't affected. They'll simply look up the A record and
make an IPv4 connection straight away.

Properly set up IPv4 systems are not affected.

But what also can happen is that the servers supports and advertises
IPv6 and the client just /thinks/ it has IPv6 connectivity. 6to4 and Teredo tunnels are notorious for this. The client tries IPv6 first, but gets no connection because it does not have a working IPv6 connection.

Yes, that's correct. I can reproduce that issue here too, if I replace my IPv6 copnnection with an IPv4 only one. The hosts are statically configured, so still have IPv6. It has happened, but not as part of a normal setup (was a workaround when the DSL line went down).

Teredo is history, or at least it should be, Microsoft shut off their Teredo servers.

6to4 is still among us....

Yes, 6to4 is there, though not something I ever used myself.


... Bit: The increment by which programmers slowly go mad
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

Hello Tony,

On Thursday August 25 2016 07:17, you wrote to me:

6to4 is still among us....

Yes, 6to4 is there, though not something I ever used myself.

I have never used it myself, but there are systems in the list of IPv6 nodes that use it.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: Michiel's laptop (2:280/5555.1)

Michiel van der Vlist wrote to Tony Langdon <=-

I have never used it myself, but there are systems in the list of IPv6 nodes that use it.

I did see that.


... Some men are discovered; others are found out.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

Hello Michiel!

24 Aug 16 14:51, you wrote to me:

Finally got my Fido feed hooked back up. I'm ipv6 capable as
well, and my domains have both A and AAAA records.

I noticed. I also noticed that your binkp server accepts IPv6 incoming
connections.

Yeah, it's much easier when you run your own DNS cluster. I'm debating over migrating it all to Route53 though...

I imagine I'll be back in the nodelist within the next couple
weeks.
:)

Weeks!!? Does your Net/Region not participate in de DAILYLST project?

I think my RC is still in the process of rebuilding his system. I checked today's Nodelist and I wasn't in there :(

domains: warensemble.com bbs.warensemble.com
binkp.warensemble.com

(all point to the same IPs for now. I separated them just in case
I want to move them to different machines later)

For the same reason I use seperate host name for my http en binkd
servers.

Yeah, the BBS is running on a Linode VPS. I doubt it will ever use the resources it has been given, but if I need to offload mail processing I'd like to have the option.

Anyway, pending nodelist entry, I have entered you in thelist of
Fidonet IPv6 capable nodes as a prospective member.

Thanks. I'm sure I'll show back up in there ... someday :)


Mike


... Never trust a computer you cannot carry.
--- GoldED+/LNX 1.1.5-b20160322
* Origin: War Ensemble - warensemble.com - Appleton, WI (1:154/30)