We have a new one. Mihail Kapitanov of 2:467/239.
Mihail, welcome to the Fidonet IPv6 club.
Win some, lose some. I have removed RJ Clay of 1:120/544. His IPv6
has been down for over a month now and he does not respond.
So we keep hovering at 50 members.
We have a new one. Mihail Kapitanov of 2:467/239.
Mihail, welcome to the Fidonet IPv6 club.
Are these people contacting you personally? Or are you going out on
your own and finding them?
Win some, lose some. I have removed RJ Clay of 1:120/544. His
IPv6 has been down for over a month now and he does not respond.
Last I heard he's still having hardware issues, but who knows. After
that amount of time one could setup a VPS somewhere until they got
their own hardware straightened out. I think Allen is still awaiting a nodelist segment to be processed even. :(
So we keep hovering at 50 members.
Still a good number, in my opinion. Taking into account the limited availability of IPv6 connectable FTN mailers out there (as far as I
know, there's only three or less, and only one that is probably
considered "stable").
Three days trying to setup it, but me still traffic goes on IPv4 = (
Can you show the log of their connections?
Your assumptium seems right. When I do nothing special I get:
While normally a IPv6 address is always tried first...
I read it. But the manual says that "-6 *only* connect via IPv6". if a tunnel that something happens, then v4 i have not joined =(
Stas Degteff of 2:5080/102 has joined us. It is via 6to4, so not the bestway
of connecting to the IPv6 InterNet, but he is connecteable on IPv6.
No IPv6 address with binkp.net domain...
80 2:5030/1520 Andrey Geyko T-6in4 he.net f
Congratulations Andrey and welcome to the Fidonet IPv6 club.
Congratulations Andrey and welcome to the Fidonet IPv6 club.
Thank you, do you regulary monitor the nodelist for new ipv6 nodes?
And jubilee member. ;)
And jubilee member. ;)
We have en new member.
82 2:5010/352 Dmitriy Smirnov Native EkranTV f
Dmitriy welcome to the Fidonet IPv5 club!
Cheers, Michiel
Dmitriy welcome to the Fidonet IPv5 club!New club? ;D
>> Dmitriy welcome to the Fidonet IPv5 club!
TK> New club? ;D
Why not? The protocol exists =)
On 11-15-18 09:22, Alexandr Kruglikov wrote to Tommi Koivula <=-
@TZ: 00f0
Good ${greeting_time}, Tommi!
14 Nov 18 22:12, you wrote to Michiel van der Vlist:
Dmitriy welcome to the Fidonet IPv5 club!New club? ;D
Why not? The protocol exists =)
Dmitriy welcome to the Fidonet IPv5 club!
New club? ;D
Why not? The protocol exists =)Didn't think it ever got out in the wild.
On 11-15-18 14:33, Alexandr Kruglikov wrote to Tony Langdon <=-
Dmitriy welcome to the Fidonet IPv5 club!
New club? ;D
Why not? The protocol exists =)Didn't think it ever got out in the wild.
As far as I know, no. =)))
Many of the developments from it went into MPLS
We have a new one:
73 2:250/5 Christian Sacks Native Sky Broadband
Christian, welcome to the Fidonet IPv6 club!
80 2:240/100 Arno Klein Native OVH
Arno, welcome to the Fidonet IPv6 club.
Arno, welcome to the Fidonet IPv6 club.
Thanks! Happy to join. ;)
Ludwig, welcome to the Fidonet IPv6 club.thanks
82 2:2452/502 Ludwig Bernhartzeder Native DTAG OO
For the moment outgoing only, but we are working on that.
84 2:335/364 Fabio Bizzi Native IT-ALBACOM
84 2:335/364 Fabio Bizzi Native IT-ALBACOM
Fabio, congratulations and welcome to the Fdionet IPv6 club!
Tutto Bene! :)
We have a new one:
92 2:263/5 Martin List-Petersen Native TuxBox
On 04-15-20 22:01, Martin List-Petersen wrote to Michiel van der Vlist <=-
Thanks ... my BBS days were from about 1992 to 1997. Now rebooted.
My IPv6 days started around 2002 with a 6bone /48 from SUnet.
We have a new one:
92 2:263/5 Martin List-Petersen Native TuxBox
Martin, welcome to the Fidonet IPv6 club!
Thanks ... my BBS days were from about 1992 to 1997. Now rebooted.
My IPv6 days started around 2002 with a 6bone /48 from SUnet.
92 2:263/5 Martin List-Petersen Native TuxBox
Thanks ... my BBS days were from about 1992 to 1997. Now rebooted.
My IPv6 days started around 2002 with a 6bone /48 from SUnet.
I was playing with IPv6 around the same time, beating a Linux 2.2 kernel into submission (that was a lot of fun and games - one of the big bugs being that the default route didn't work!), and using various tunnels.
I wnet native in 2011, just before my ISP officially offered IPv6 to its customers, as they had an opt in pilot test before then for some time.
I had to wait until I purchased a router that supported IPv6. Been running native IPv6 since.
On 04-17-20 02:59, Martin List-Petersen wrote to Tony Langdon <=-
On 16 Apr 2020, Tony Langdon said the following...
I was playing with IPv6 around the same time, beating a Linux 2.2 kernel into submission (that was a lot of fun and games - one of the big bugs being that the default route didn't work!), and using various tunnels.
Hah .. ah well .. one could route 2000::/3 or 3ffe::/16 for 6bone.
There was always a way :)
See .. I fixed that differently. I came from a telecoms and ISP background. Worked as technical manager for my first telco '97 and onwards. So in 2006, I created my own ISP. By 2008 we offered native
IPv6 to our residential customers and were hosting a SixXS PoP on top
of that. We were the first and only ISP in Ireland to offer residential customers IPv6 by default.
I also claim the fame (infamious) to have been allocated the first PIv6 allocation in the RIPE region. I literally submitted my application
during the meeting at RIPE, when the policy was passed :) It was a step backwards in IPv6 thinking, but a step forward to bring entities onto IPv6.
I also claim the fame (infamious) to have been allocated the first
PIv6 allocation in the RIPE region. I literally submitted my
application during the meeting at RIPE, when the policy was passed :)
It was a step backwards in IPv6 thinking, but a step forward to bring entities onto IPv6.
Can you expand on that? What exactly was a step backward and how and why?
Martien, welcome to the Fidonet IPv6 club!
How do you get in the IPv6 club?
I've been IPv6 for a while now...
92 2:280/2030 Martien Korenblom Native Transip
Binkp reachable at bbs.korenbloem.nl. He will be in towmorrows daily nodelist.
Congratulations and welcome to the club!
You are nr 93 on the list, see next message.
The host part reflects your node number, but unlike the unofficial convention for f1d0 mumbers it is in hex instead of in decimal.
Any comment?
The host part reflects your node number, but unlike the
unofficial convention for f1d0 mumbers it is in hex instead of in
decimal. Any comment?
Yup, an IPv6 address is a hexadecimal address -
and mailers and tossers semi-think in hex, so it seemed fitting to me.
and mailers and tossers semi-think in hex, so it seemed fitting to me.
An IPv6 address is a 128 bit number. Usually (but not always) represented to the human by up to eight colon seperated groups of up to four hexadicimal digits.
If mailers and tossers think at all, which is questionable, they think in nodenumbers, which are almost always represented to the human in decimal.
f1d0 is "hex speak", directed at the human, not the machine.
Anyway, you are breaking the convention and that can be confusing. In your case it is clear because there is an "alfa digit" in one of the hex number groups, but there are plenty of hex numbers that only have the digits 0-9. How is the reader going
to know if it is hex or decimal?
The f1d0 convention is supposed to be humanly readable -- very few humans can immediately convert hex numbers into the corresponding nodenumber, that is decimal in normal "speak".
Yup, any "x" bit number (where X is divisable by 8) is representable
as a hex number.
If mailers and tossers think at all, which is questionable, they
think in nodenumbers, which are almost always represented to the
human in decimal.
Yeah, but they lay out packets to be sent using filesnames that are
named with a hex value, to represent the destination for the file.
f1d0 is "hex speak", directed at the human, not the machine.
Its cool isnt it that we can make a representable word from hex.
Anyway, you are breaking the convention and that can be
confusing. In your case it is clear because there is an "alfa
digit" in one of the hex number groups, but there are plenty of
hex numbers that only have the digits 0-9. How is the reader
going to know if it is hex or decimal?
Why do they need to know? If I went with SLAAC, it would be even more confusing right?
Yeah, but they lay out packets to be sent using filesnames that are
named with a hex value, to represent the destination for the file.
Some software does that. Your point?
Why do they need to know? If I went with SLAAC, it would be even more confusing right?SLAAC numbers do not have the "f1d0" marker in the first 16 bits of the host part.
Look, it is just a game among the members of the Fidonet IPv6 club. If you want to be a spoilsport and play your own game by using
hex instead of decimal for the node number part, then ... then you are on your own...
How would 2:5020/11200 represent their node number in your IPv6 f1d0 hex game?
How would 2:5020/11200 represent their node number in your IPv6
f1d0 hex game?
He would chose another node number for his IPv6 box?
How would 2:5020/11200 represent their node number in your IPv6 f1d0 hex game?He would chose another node number for his IPv6 box?
That's funny :)
That's funny :)How so?
That's funny :)
How so?
Rules of the ipv6 f1d0 game:
* Zone must be between 1-9999 - no problem there, if this network has scalability issues, its unlikely to be in our lifetime.
* Net must be between 1-9999 - note to ZC's dont create nets > 9999 otherwise if they represent their IPv6 address using the unofficial f1d0 convention, it will be confusing.
* Node must be between 1-9999 - note to NC's - see above. Sorry Sergey, you must get a new node number if you want to play.
What a unintuitive convention. I assumed it is a 1:1 mapping as both networks put the separators between 16-bit chunks.
You know you should never ASSUME right? ;)
How would 2:5020/11200 represent their node number in your IPv6 f1d0
hex game?
He would chose another node number for his IPv6 box?
------------^ 2:460/5858 ;)
Corrected.
Hello All,
97 1:105/5 Michael Pierce Native Comcast
Michael, welcome to the Fidobet IPv6 club!
Hi Michiel.
17 Dec 20 12:33:46, you wrote to Stas Mishchenkov:
Corrected.
===
Not.
We have a new one:
96 1:460/5858 Stas Mishchenkov T-6in4 het.net f INO4
Note that this is an IPv6 only node. It can not accept incoming IPv4 connections.
96 1:460/5858 Stas Mishchenkov T-6in4 het.net f
INO4
Note that this is an IPv6 only node. It can not accept incoming
IPv4 connections.
Shouldn't this be Z2?
104 1:154/7715 Dallas Hinton Native Shaw Comms.
Dallas, welcome to the Fidonet IPv6 club!
P.S. In fact, it is very pleasing that Fido has more and more IPv6 protocol...
Michiel van der Vlist wrote to All <=-
Dallas, welcome to the Fidonet IPv6 club!
Did I make it to the IPv6 list? Being an HE Sage twice I would hope so
:)
Michiel van der Vlist wrote to Brian Rogers <=-
You don't read Fidonews? The list is published weekly. You are #84 on
the list.
We have a new one. 106 2:5020/921 Andrew Savin T-6in4Hi there. Thanks, I'm not new, I'm returning one, btw ;)
he.net Andrew, welcome to the Fidonet IPv6 club.
We have a new one. 106 2:5020/921 Andrew Savin
T-6in4 he.net Andrew, welcome to the Fidonet IPv6 club.
Hi there. Thanks, I'm not new, I'm returning one, btw ;)
Hello All,
We have a new one.
109 1:266/420 Scott Street Native Comcast OO
For the moment outgoing only, there is a poblem with Comcast.
Something with opening IPv6 ports.
Scott, welcome to the Fidonet IPv6 club.
For the moment outgoing only, there is a poblem with Comcast.
Something with opening IPv6 ports.
I have Comcast and have no problems with opening IPv6 ports, although
I am using my own routers with OpenWRT firmware. If Scott is using Comcast's router/gateway, I wouldn't be surprised if there are issues
like that.
Andrew Leary wrote to Michiel van der Vlist <=-
I have Comcast and have no problems with opening IPv6 ports, although I
am using my own routers with OpenWRT firmware. If Scott is using Comcast's router/gateway, I wouldn't be surprised if there are issues
like that.
Scott, welcome to the Fidonet IPv6 club.
Ditto.
I have Comcast as well, however they filter the same ports on IPv6 as
they do on IPv4 such as 25, 80, etc. I see you're running under the Comcast native IPv6 - did they open the ports for you or are you lucky
and they just haven't hit your block yet? I ended up using HE.net with
a 6 to 4 tunnel which bypasses the Comcast blocks.
I have Comcast as well, however they filter the same ports on IPv6The filter on port 25 is easy to work around, and prevents a lot of
as they do on IPv4 such as 25, 80, etc. I see you're running under
the Comcast native IPv6 - did they open the ports for you or are you
lucky and they just haven't hit your block yet? I ended up using
HE.net with a 6 to 4 tunnel which bypasses the Comcast blocks.
spam entering the internet.
They do not filter port 80 for me.
(http://phoenix.bnbbbs.net works fine.) They have a list of blocked
ports on their website at https://www.xfinity.com/support/articles/list-of-blocked-ports ...
Andrew Leary wrote to Brian Rogers <=-
The filter on port 25 is easy to work around, and prevents a lot of
spam entering the internet. They do not filter port 80 for me. (http://phoenix.bnbbbs.net works fine.) They have a list of blocked
ports on their website at https://www.xfinity.com/support/articles/list-of-blocked-ports ...
We have a new one:again. ;-)
110 2:469/122 Sergey Zabotlotney T-6in4 he.net fmy node was already in your list before.
We have a new one:
again. ;-)
110 2:469/122 Sergey Zabotlotney T-6in4 he.net f
my node was already in your list before.
Vladislav, welcome to the Fidonet IPv6 club!
Vladislav is also the sysop of 2:5010/278. That node supports outgoing IPv6, but no incoming yet.
Hi guys!
Vladislav, welcome to the Fidonet IPv6 club!
Hi guys!
Happy to see everyone, IPv6 RULEZ! :D
https://brorabbit.g0x.ru/files/perl/findIPv6.pl - Finds IPv6 nodes in
the nodelist. Internet connection required.
https://brorabbit.g0x.ru/files/perl/findIPv6.pl - Finds IPv6
nodes in the nodelist. Internet connection required.
Nice! ;-)
56. 2:31/0 Helmut Renner fd14:7740:62f:4800:3a10:d5ff:fe93:7e79
57. 2:31/2 Helmut Renner fd14:7740:62f:4800:3a10:d5ff:fe93:7e79
https://brorabbit.g0x.ru/files/perl/findIPv6.pl - Finds IPv6 nodes in
the nodelist. Internet connection required.
Nice! ;-)
Parsing nodelist file NODELIST.012
Nodelist for Friday, January 12, 2024 -- Day number 012 parsed, 968 IP-nodes processed (0.012 sec)
155. 2:5020/1042 Michael Dukelsky 2a09:5302:ffff::f3c
156. 2:5020/1042 Michael Dukelsky 2a09:5302:ffff::f3c
MvdV> Nice indeed.https://brorabbit.g0x.ru/files/perl/findIPv6.pl - Finds IPv6
nodes in the nodelist. Internet connection required.
Nice! ;-)
56. 2:31/0 Helmut Renner fd14:7740:62f:4800:3a10:d5ff:fe93:7e79
57. 2:31/2 Helmut Renner fd14:7740:62f:4800:3a10:d5ff:fe93:7e79
I'm glad that this helps.
I'm checking to see how he resolves.
If you look at the error text, you will see a large number of nodes
there whose domain names are not resolved at all. This may be useful
for a nodelist cop. ;)
56. 2:31/0 Helmut Renner
fd14:7740:62f:4800:3a10:d5ff:fe93:7e79 57. 2:31/2 Helmut
Renner fd14:7740:62f:4800:3a10:d5ff:fe93:7e79
Surprise! ;)
If you look at the error text, you will see a large number of nodes
there whose domain names are not resolved at all. This may be useful
for a nodelist cop. ;)
Should I add the -6 option to callip.pl?
https://brorabbit.g0x.ru/files/perl/findIPv6.pl - Finds IPv6 nodes in the nodelist. Internet connection required.
Nice! ;-)
We have a new one:
Floris welcome to Fodonet and welcome to the Fidonet IPv6 club!
Hello All,
We have a new one:
108 2:280/2060 Dennis Slagers Native Ziggo f
Dennis is a returning sysop. Returning from net 2:283 after almost 25 years.
Dennis: welcome to the Fidonet IPv6 club!
Cheers, Michiel
Michiel van der Vlist wrote to All <=-
Hello All,
We have a new one:
101 2:5030/1520 Ekaterina Geyko T-6in4 he.net f Ekaterina, welcome to the Fidonet IPv6 club!
Ekaterina, welcome to the Fidonet IPv6 club!
Oh, how exciting!
Bjorn Felten wrote to Dan Clough <=-
Dan Clough -> Michiel van der Vlist skrev 2025-07-19 16:19:
Ekaterina, welcome to the Fidonet IPv6 club!
Oh, how exciting!
Thank you for your kind and eloquent contribution to the Fidonet community.
You swine. You vulgar little maggot. You worthless bag of filth.
Bjorn Felten wrote to Dan Clough <=-
Don't hold back; tell us how you *really* feel about IPv6.
My previous post should have made that clear, but ... you're slow, so...
In reality, IPv4 *continues* to work just fine, and will for a long time
to come. In a couple of generations there may be a need for a
"changeover", but there is no emergency pending. It reminds me of the
frenzy over the Y2K "issue", which turned out to be largely.... hype.
While I agree the Y2K issue was overhyped, part of the reason it
turned out to be largely hype was because a whole lot of folks spent a
lot of time figuring out and updating their systems to prevent it from being worse.
I should probably try to move this side discussion to a more
appropriate echo, but I am not sure what that would be. The Y2K echo
is long gone. ;)
I should probably try to move this side discussion to a more appropriate echo, but I am not sure what that would be. The Y2K echo is long gone.
;)
110 1:229/122 Scott Tompkins T-6in4 he.net
110 1:229/122 Scott Tompkins T-6in4 he.net
I believe Scott is 1:229/112.
he.net to the rescue, as so many of us have experienced throughout
the years.
115 2:240/8010 Sigi Schoenicke Native DTAG
Sigi, congratulations and welcome to the Fidonet IPv6 club!
115 2:240/8010 Sigi Schoenicke Native DTAG
Sigi, congratulations and welcome to the Fidonet IPv6 club!
Michiel, please give me one more *g*. :)
On Friday November 21 2025 14:47, you wrote to me:
115 2:240/8010 Sigi Schoenicke Native DTAG
Sigi, congratulations and welcome to the Fidonet IPv6 club!
Michiel, please give me one more *g*. :)
Done!
BTW, "Siggi" is that short for "Siegfried" or "Sigmund" ?
Does she live in Westview and is called Dottie?
Do we? The node was marked as Down in this weeks nodelist?
Do we? The node was marked as Down in this weeks nodelist?
I noticed that too...
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495936:59:59 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,953 |