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.
 Mv> 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!
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".
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...
That's funny :)How so?
What a unintuitive convention. I assumed it is a 1:1 mapping as both networks put the separators between 16-bit chunks.
Michiel van der Vlist wrote to All <=-
Dallas, welcome to the Fidonet IPv6 club!
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 ;)
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 ...
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
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 190:36:45 |
Calls: | 184 |
Calls today: | 1 |
Files: | 5,413 |
Messages: | 222,750 |