* Origin: he.net certified sage (2:280/5555)
Is there a full listing somewhere?
* Origin: he.net certified sage (2:280/5555)
As am I twice over.
Michiel van der Vlist wrote to Brian Rogers <=-
It is published weekly in Fidonews.
See also next message.
You have two T-shirts?
You have two T-shirts?
No they seemed to have stopped the T-shirt mailing.
My packet node is IPv6 ready as well, and I believe my bink should be.
If not I'll have to investigate why.
On 05-14-21 16:56, Brian Rogers wrote to Michiel van der Vlist <=-
My IPv6 takes priority. My block is mainly used for IPv6 under ax.25
but I also use it for my postfix, apache, and other servers. My packet node is IPv6 ready as well, and I believe my bink should be. If not
I'll have to investigate why.
Michiel van der Vlist wrote to Brian Rogers <=-
http://www.vlist.eu/fotos/sage-f.jpg
http://www.vlist.eu/fotos/sage-b.jpg
No need to investigate, it works fine:
+ 10:03 [2736] call to 1:142/103@fidonet
10:03 [2736] trying bbs.n1uro.com [2001:470:8a1e::3]...
10:03 [2736] connected
+ 10:03 [2736] outgoing session with bbs.n1uro.com:24554 [2001:470:8a1e::3] - 10:03 [2736] OPT
+ 10:03 [2736] addr: 432:1/157@vkradio (n/a or busy)
Tony Langdon wrote to Brian Rogers <=-
As you feed off me on VKRadio, you should be connecting to me by
default over IPv6, unless you override that.
http://www.vlist.eu/fotos/sage-f.jpg
http://www.vlist.eu/fotos/sage-b.jpg
Nice! One of the blocks I got was for a client of mine. I was also
pleased to learn that one of the guys in their tech support is also a
ham.
He was surprised to learn how I got IPv6 routed over the ax.25
protocol.
[2001:470:8a1e::3] - 10:03 [2736] OPT
Good, thanks for the report! Basically SBBS and it's built in Bink saw
the active IPv6 and ported it right in automatically.
+ 10:03 [2736] addr: 432:1/157@vkradio (n/a or busy)
Ahh now I have to figure out why this is!
Cheers and thanks again for the verification.
Michiel van der Vlist wrote to Brian Rogers <=-
HAMs are everywhere! ;-)
Once, a long time ago I pioneered in data over HAM radio. That was
before IPv6, even before AX25. I still kept the call, but I am no
longer active as a HAM.
No need for action. That is the standard response when Binkd sees an
AKA in an unknown domain. My binkd does not know about the domain vkradio.
73 de PA0MMV
On 05-16-21 07:51, Brian Rogers wrote to Tony Langdon <=-
Hello Tony;
Tony Langdon wrote to Brian Rogers <=-
As you feed off me on VKRadio, you should be connecting to me by
default over IPv6, unless you override that.
If there's an IPv6 path available, it takes priority... but it appears we've been having handshaking issues (password). Chalk it up to social distancing? <G>
On 05-16-21 07:50, Brian Rogers wrote to Michiel van der Vlist <=-
Good, thanks for the report! Basically SBBS and it's built in Bink saw
the active IPv6 and ported it right in automatically.
+ 10:03 [2736] addr: 432:1/157@vkradio (n/a or busy)
Ahh now I have to figure out why this is!
On 05-16-21 15:09, Michiel van der Vlist wrote to Brian Rogers <=-
He was surprised to learn how I got IPv6 routed over the ax.25
protocol.
No need for action. That is the standard response when Binkd sees an
AKA in an unknown domain. My binkd does not know about the domain vkradio.
On 05-16-21 10:05, Brian Rogers wrote to Michiel van der Vlist <=-
I'm a coordinator for 44-net. I handle 1/5th of the USA. They're now
just beginning to talk about incorporating IPv6 into amprnet however in
my case it's unneeded. I have a /48 from he.net and broker IPs to
various points whether they be ipencap tunnel on 44net OR encapsulated under ax.25! The trick was simple too. To route IP on ax.25 it demands
ARP so it can use the callsign as a mac address and we all know IPv6
uses NDS not ARP... so depending on the remote source I do a 6-to-4 mapping to their 44-net IP or to their commercial IP. For radio, the mapping goes to their 44-net IP since that's the only IP they have.
Speed wise, it's not much different than IPv4... and it's slick because using 44-net that's your ARP mapping.
Tony Langdon wrote to Brian Rogers <=-
Yeah I'm native IPv6 on my end. :) Yeah, have to compare passwords -
show me yours and I'll show you mine (in email, not here)... :D
Tony Langdon wrote to Brian Rogers <=-
On 05-16-21 10:05, Brian Rogers wrote to Michiel van der Vlist <=-
I'm a coordinator for 44-net. I handle 1/5th of the USA. They're now
just beginning to talk about incorporating IPv6 into amprnet however in
my case it's unneeded. I have a /48 from he.net and broker IPs to
various points whether they be ipencap tunnel on 44net OR encapsulated under ax.25! The trick was simple too. To route IP on ax.25 it demands
ARP so it can use the callsign as a mac address and we all know IPv6
uses NDS not ARP... so depending on the remote source I do a 6-to-4 mapping to their 44-net IP or to their commercial IP. For radio, the mapping goes to their 44-net IP since that's the only IP they have.
Speed wise, it's not much different than IPv4... and it's slick because using 44-net that's your ARP mapping.
Interesting, would like to know the details. I'm fully IPv6 capable,
and would like to be able to transmit it over AX.25 one day.
On 05-17-21 07:58, Brian Rogers wrote to Tony Langdon <=-
Yeah I'm native IPv6 on my end. :) Yeah, have to compare passwords -
show me yours and I'll show you mine (in email, not here)... :D
I have an HE.net 6-to-4 tunnel/map however it still take priority in my routing - as it should. I'll try to send you an ascii in email of what
I have. I really have a feeling that the nodelist isn't loading... but that's just my hunch.
... Equal opportunity antagonist
On 05-17-21 08:02, Brian Rogers wrote to Tony Langdon <=-
Interesting, would like to know the details. I'm fully IPv6 capable,
and would like to be able to transmit it over AX.25 one day.
Details are above.
If you want a Proof of Concept, traceroute6 wb2snn.ampr.org
That's an RF Only site with -no- internet whatsoever. You should get to gw-ipv6.n1uro.com then to wb2snn:
n1uro@n1uro:~$ traceroute6 wb2snn.ampr.org
traceroute to wb2snn.ampr.org (2001:470:8a1e::17), 30 hops max, 80 byte packets
1 gw-ipv6.n1uro.com (2001:470:8a1e::1) 1.432 ms 1.893 ms 2.747 ms
2 wb2snn.ampr.org (2001:470:8a1e::17) 3753.106 ms 3758.076 ms
3758.812 ms n1uro@n1uro:~$
And...
n1uro@n1uro:~$ telnet6 wb2snn.ampr.org node
Trying 2001:470:8a1e::17...
Connected to wb2snn.ampr.org.
Escape character is '^]'.
(wb2snn.ampr.org:uronode) login:
Not only is ipv6 working, but my URONode is IPv6 compatable.
73
... "Data, people do not _have_ internal chronometers." - Riker
Tony Langdon wrote to Brian Rogers <=-
Yeah I'm native IPv6 on my end. :) Yeah, have to compare passwords -
show me yours and I'll show you mine (in email, not here)... :D
What you sent looked good. And if you need a file copy of the nodelist (as opposed to DNS), you can download that from my file areas (again, anonymous HTTP/FTP work fine). :)
... To my embarrassment, I was born in bed with a lady!
Tony Langdon wrote to Brian Rogers <=-
The detailed details - I have a vague idea, but lacks enough for me to fully grasp it. :)
Little bit hard right now, while I'm offline on a plane going up the
east coast of Australia. ;)
Another reason I should check out UORNode. I'm in need of a new RF node/gateway, after I get back home. And since you support IPv6,
you've gone to the front of the queue. :)
... "Data, people do not _have_ internal chronometers." - Riker
I've been accused of it. :D
On 05-19-21 16:32, Brian Rogers wrote to Tony Langdon <=-
Yeah I'm native IPv6 on my end. :) Yeah, have to compare passwords -
show me yours and I'll show you mine (in email, not here)... :D
Ha! If I had a nickel for every time I heard that, I'd still be waiting
to get a nickel <G>
What you sent looked good. And if you need a file copy of the nodelist (as opposed to DNS), you can download that from my file areas (again, anonymous HTTP/FTP work fine). :)
I have one, I'm surprised it didn't load up for me.
... To my embarrassment, I was born in bed with a lady!
We used to have a chain store called Two Guys years ago. In today's
world you'd think that's where some of the more vocal ones came from :)
On 05-19-21 16:37, Brian Rogers wrote to Tony Langdon <=-
The detailed details - I have a vague idea, but lacks enough for me to fully grasp it. :)
When the time comes I can help ya get things going.
Little bit hard right now, while I'm offline on a plane going up the
east coast of Australia. ;)
Plane? What happened to the ol' feet? :) .. or do you have shoes like Apollo - with wings on them <G>
Another reason I should check out UORNode. I'm in need of a new RF node/gateway, after I get back home. And since you support IPv6,
you've gone to the front of the queue. :)
My axMail-FAX system, which uses Postfix as a backend MTA, also is IPv6 ready... since Postfix handles the mail in reality.
... "Data, people do not _have_ internal chronometers." - Riker
I've been accused of it. :D
Just don't play footsies with you, you've known to "nail" that one
down? :D
Tony Langdon wrote to Brian Rogers <=-
Hmm, strange. It's built from raw data with MakeNL.
Tony Langdon wrote to Brian Rogers <=-
Cool, I'll take you up on that one day. :)
Haha, it was a 1500+ km trip, this is a BIG country. Wasn't even an interstate flight! ;)
On 05-19-21 20:13, Brian Rogers wrote to Tony Langdon <=-
Tony Langdon wrote to Brian Rogers <=-
Hmm, strange. It's built from raw data with MakeNL.
I have it loaded up now. I just had to manually enter it in the .ini
file.
On 05-19-21 20:19, Brian Rogers wrote to Tony Langdon <=-
Tony Langdon wrote to Brian Rogers <=-
Cool, I'll take you up on that one day. :)
It's really no where near as difficult as one thinks.
Haha, it was a 1500+ km trip, this is a BIG country. Wasn't even an interstate flight! ;)
One big LONG sprint - no problem right? :)
Tony Langdon wrote to Brian Rogers <=-
I have it loaded up now. I just had to manually enter it in the .ini
file.
Ahh OK, cool. :)
Tony Langdon wrote to Brian Rogers <=-
Mor a case of getting used to the lay of the land. :)
Hmm, kind of an oxymoron. :P
On 05-20-21 06:51, Brian Rogers wrote to Tony Langdon <=-
I'm making the connect attempt, and via IPV6 no less. I'm receiving
your alias nodes though from what I see.
... I'll torture you SO slowly, you'll think it's a career
On 05-20-21 06:53, Brian Rogers wrote to Tony Langdon <=-
Tony Langdon wrote to Brian Rogers <=-
Mor a case of getting used to the lay of the land. :)
You do it once, it becomes old hat from then on :)
Hmm, kind of an oxymoron. :P
OR... you can have very VERY large feet <G>
... The best way to stop smoking is to carry wet matches.
Tony Langdon wrote to Brian Rogers <=-
Cool. I may set you to IPv6+IPv4. My IPv6 connectivity is actually better on the hub (native vs OpenVPN). How does that sound?
Haha catch me. :P
On 05-20-21 23:26, Brian Rogers wrote to Tony Langdon <=-
Hey Tony;
Tony Langdon wrote to Brian Rogers <=-
Cool. I may set you to IPv6+IPv4. My IPv6 connectivity is actually better on the hub (native vs OpenVPN). How does that sound?
That's perfect!.. it's like putting a humidifier and a dehumidifier in
the same room and letting them hash it out <G>
Haha catch me. :P
With my neuropathy are you kidding me?? :)
Tony Langdon wrote to Brian Rogers <=-
LOL, I had a track meet today (the reason I'm in Cairns, actually). :) Backing that up tomorrow with a 5k road race, for a change of pace, literally! :)
On 05-22-21 20:33, Brian Rogers wrote to Tony Langdon <=-
Hello Tony;
Tony Langdon wrote to Brian Rogers <=-
Seems the IPv6 path is working fine.
LOL, I had a track meet today (the reason I'm in Cairns, actually). :) Backing that up tomorrow with a 5k road race, for a change of pace, literally! :)
I'm lucky just to keep up with the daily rat race - and I've been on
the losing end of that lately too.
Tony Langdon wrote to Brian Rogers <=-
Cool, well it's more direct on my end. I'm unusual in that I run
native IPv6 on the BBS and tunnel IPv4. :)
LOL, I had a track meet today (the reason I'm in Cairns, actually). :) Backing that up tomorrow with a 5k road race, for a change of pace, literally! :)
I ended up winning the 5k in my age group, FYI. :)
[11:39:52 brorabbit jamstat]$ cat ~/logs/callip.log
2024-09-30 11:39:33.459 callip.pl v.0.9.6.0. -c /home/fido/etc/callip.conf -b
-f 2:467/4 2024-09-30 11:39:35.066 Finding last nodelist file from /home/fido/nodelist/nodelist.367. 2024-09-30 11:39:35.066 Last nodelist found
at 0.000 seconds. 2024-09-30 11:39:35.119 Nodelist for Saturday, September 14,
2024 -- Day number 258 parsed, 942 IP-nodes processed (0.053 sec) 2024-09-30
11:39:35.143 Calling 2:467/4 2024-09-30 11:39:35.143 ip.fido.odessa.ua:24554
2024-09-30 11:39:35.143 Error: Cannot getaddrinfo - eu??ec??oe u?? u?u c?y?6a
2024-09-30 11:39:52.859 callip.pl v.0.9.6.0. -c /home/fido/etc/callip.conf -b
-f 2:467/888 2024-09-30 11:39:52.887 Finding last nodelist file from /home/fido/nodelist/nodelist.367. 2024-09-30 11:39:52.887 Last nodelist found
at 0.000 seconds. 2024-09-30 11:39:52.939 Nodelist for Saturday, September 14,
2024 -- Day number 258 parsed, 942 IP-nodes processed (0.052 sec) 2024-09-30
11:39:52.943 Calling 2:467/888 2024-09-30 11:39:52.943
fido.paket.ua:24554 2024-09-30 11:39:52.943 Error: Cannot getaddrinfo - eu??ec??oe u?? u?u c?y?6a [11:40:05 brorabbit jamstat]$
[11:39:52 brorabbit jamstat]$ cat ~/logs/callip.log
2024-09-30 11:39:33.459 callip.pl v.0.9.6.0. -c
IP-nodes processed (0.053 sec) 2024-09-30 11:39:35.143 Calling 2:467/4 2024-09-30 11:39:35.143 ip.fido.odessa.ua:24554 2024-09-30 11:39:35.143 Error: Cannot getaddrinfo - ¥¨§¢¥á⮥ ¨¬ï ¨«¨ á«ã¦¡ 2024-09-30 11:39:52.859 callip.pl v.0.9.6.0. -c /home/fido/etc/callip.conf -b -f 2:467/888 2024-09-30 11:39:52.887 Finding last nodelist file from /home/fido/nodelist/nodelist.367. 2024-09-30 11:39:52.887 Last nodelist found at 0.000 seconds. 2024-09-30 11:39:52.939 Nodelist for Saturday, September 14, 2024 -- Day number 258 parsed, 942 IP-nodes processed (0.052 sec) 2024-09-30 11:39:52.943 Calling 2:467/888 2024-09-30 11:39:52.943 fido.paket.ua:24554 2024-09-30 11:39:52.943 Error: Cannot getaddrinfo - ¥¨§¢¥á⮥ ¨¬ï ¨«¨ á«ã¦¡ [11:40:05 brorabbit jamstat]$
IP-nodes processed (0.053 sec) 2024-09-30 11:39:35.143 Calling
2:467/4
2024-09-30 11:39:35.143 ip.fido.odessa.ua:24554 2024-09-30 11:39:35.143
Error: Cannot getaddrinfo - ¥¨§¢¥á⮥ ¨¬ï ¨«¨ á«ã¦¡ 2024-09-30
11:39:52.859 callip.pl v.0.9.6.0. -c /home/fido/etc/callip.conf -b -f
2:467/888 2024-09-30 11:39:52.887 Finding last nodelist file from
/home/fido/nodelist/nodelist.367. 2024-09-30 11:39:52.887 Last nodelist
found at 0.000 seconds. 2024-09-30 11:39:52.939 Nodelist for Saturday,
September 14, 2024 -- Day number 258 parsed, 942 IP-nodes processed
(0.052 sec) 2024-09-30 11:39:52.943 Calling 2:467/888 2024-09-30
11:39:52.943 fido.paket.ua:24554 2024-09-30 11:39:52.943 Error: Cannot
getaddrinfo - ¥¨§¢¥á⮥ ¨¬ï ¨«¨ á«ã¦¡ [11:40:05 brorabbit jamstat]$
if your ISP blocks .UA domains resolving, set dns to
1.1.1.1
8.8.8.8
2606:4700:4700::1111
2001:4860:4860::8888
then retry. and if these DNS are blocked too... well, try a VPN.
if your ISP blocks .UA domains resolving, set dns to
1.1.1.1
8.8.8.8
2606:4700:4700::1111
2001:4860:4860::8888
[ustasm@MikroTik] > /ip dns print
servers: 8.8.8.8,8.8.4.4,74.82.42.42,2001:470:20::2
dynamic-servers: 91.205.216.34,8.8.8.8,fe80::1
maybe, you were unlucky and 91.205.216.34 answered with host not
found.
109 2:5020/5452 Alex Barinov T-6in4 he.net
110 2:5030/723 Alexey Khromov Native RU-AI-20240222
111 2:550/278 Vladislav Muschinskikh Native Firstbyte
112 3:633/2744 Deon George Native EXETEL-AU
Alex Barinov and Deon George are not really new to the club, they
already had an IPv6 node on air. The above is their second node. The others are new AFAIK.
So Alex and Vladislav, welcome to the Fidomnet IPv6 club!
So Alex and Vladislav, welcome to the Fidomnet IPv6 club!
I also was in the list since 2023-08-09, with my two nodes
May be, earlier... =/
We have a couple of new ones.
BTW, if you are interested:
https://nodelist.fidonet.cc/analytics/ipv6
list of currently reachable ipv6 enabled nodes.
3) I doubt that explains all the differences between your list and
mine. There may be a few that I missed.
To be continued...
list of currently reachable ipv6 enabled nodes.
Interesting indeed.
1) Why am I not in it?
2) You list all the non /0 AKA's of a node. F.e. 292/854 is listed
with three other AKA's. In my list it is only listed once.
3) I doubt that explains all the differences between your list and
mine. There may be a few that I missed.
I did indeed miss a few but an important difference between your list
and mine is that you include nodes that advertise an IPv6 in the host
name but that answer only on IPv4. Example 2:301/1. Time out on IPv6.
I did indeed miss a few but an important difference between your
list and mine is that you include nodes that advertise an IPv6 in
the host name but that answer only on IPv4. Example 2:301/1. Time
out on IPv6.
Ah, yes, fixed how those cases are displayed.
I have updated my list with the help of your's. Eight new or returning nodes have been added. See next message. Thank you fo providing this service.
Why's my node is not there, I wonder... Or it requires expicit INA in nodelist?
BTW, if you are interested:
https://nodelist.fidonet.cc/analytics/ipv6
list of currently reachable ipv6 enabled nodes.
BTW, if you are interested:
https://nodelist.fidonet.cc/analytics/ipv6
list of currently reachable ipv6 enabled nodes.
Can we opt-out .. ?
Why's my node is not there, I wonder... Or it requires expicit INA in nodelist?
But what would be usefull to me is a list of nodes that advertise IPv6
Hello, Michiel!
Sunday September 21 2025 12:10, you wrote to me:
But what would be usefull to me is a list of nodes that advertise
IPv6
How do they advertise it?
Also, please check the new list of IPv6-capable nodes:
https://nodelist.fidonet.cc/analytics/ipv6
It still has some bugs! I haven't found them yet ;)
Or a literal IPv6 address in the nodelist. (A method not presently in use)
Also, please check the new list of IPv6-capable nodes:
https://nodelist.fidonet.cc/analytics/ipv6
It still has some bugs! I haven't found them yet ;)
I haven't found any bugs yet.;-)
By having an AAAA record in the DNS for the host name(s) in the
nodelist.
Or a literal IPv6 address in the nodelist. (A method not presently in
use)
I haven't found any bugs yet.;-)
I have, the site is IPv4-only! ;-)
It still has some bugs! I haven't found them yet ;)
By having an AAAA record in the DNS for the host name(s) in the
nodelist.
Or a literal IPv6 address in the nodelist. (A method not
presently in use)
Something like: https://nodelist.fidonet.cc/analytics/ipv6-nonworking
?
Something like:
https://nodelist.fidonet.cc/analytics/ipv6-nonworking ?
Yes, something like that.
Yes, something like that.
56 IPv6 non-working nodes found.
That's more than I expected. There is work to do!
56 IPv6 non-working nodes found.
That's more than I expected. There is work to do!
Please note (this is also written on the website):
for working nodes:
This report shows nodes that have IPv6 addresses resolved and have
been successfully tested with at least one protocol over the last 30
days.
for non working nodes:
This report shows nodes that have IPv6 addresses (either from nodelist
or resolved from hostnames) but no IPv6 services are currently working over the last 30 days.
So a node will be moved from working to non-working state only after
30 days of loosing ipv6 access.
I'll add a simple API to get these reports and updates with curl, but
I need to refactor the code first: it was written before I even knew
what this website would become and it's a bit of a mess :)
I take it that applies to existing nodes that once had working IPv6 connectivity and become nonworking at some point. But how about /new/ nodes that advertise IPv6 connectivity but never had it working?
I also note that a significant fraction of the 56 nodes in the list of
non working IPv6 nodes ha no connectivity at all. No IPv6 /and/ no
IPv4. It is not what I expected but I can live with it.
I'll add a simple API to get these reports and updates with curl,
but I need to refactor the code first: it was written before I
even knew what this website would become and it's a bit of a mess
:)
I stay tuned...
I take it that applies to existing nodes that once had working IPv6 connectivity and become nonworking at some point. But how about /new/ nodes that advertise IPv6 connectivity but never had it working?
I also note that a significant fraction of the 56 nodes in the list of
non working IPv6 nodes ha no connectivity at all. No IPv6 /and/ no
IPv4. It is not what I expected but I can live with it.
The list is still incomplete.
It's also sorted incorrectly.
I take it that applies to existing nodes that once had working
IPv6 connectivity and become nonworking at some point. But how
about /new/ nodes that advertise IPv6 connectivity but never had
it working?
Pls check:
https://nodelist.fidonet.cc/analytics/ipv6-weekly-news
This report uses data from the last 7 days (relative to the time you access this page) and compares it with the previous week. I can extend
the API to fetch this information with curl/python/perl if needed.
My idea is that checking for changes every day is too aggressive. But
it's up to you.. Correct me if I'm wrong.
I also note that a significant fraction of the 56 nodes in the
list of non working IPv6 nodes ha no connectivity at all. No IPv6
/and/ no IPv4. It is not what I expected but I can live with it.
Done!
https://nodelist.fidonet.cc/analytics/ipv6-advertised-ipv4-only
Great!
A daily check is indeed needlessly agressive. A weekly check is fine
with me.
I also note that a significant fraction of the 56 nodes in the
list of non working IPv6 nodes ha no connectivity at all. No
IPv6 /and/ no IPv4. It is not what I expected but I can live
with it.
Done!
https://nodelist.fidonet.cc/analytics/ipv6-advertised-ipv4-only
Great!
You realy did a great job with all this. It is very usefull to me in
my attempts to promote IPv6 in Fidonet. Keep up the good work!
BTW, if you move your mouse cursor over any (I hope so) red field, it
will show you the real error, such as "connection refused" and so on.
Feel free to ask for any additional functionality, because it looks
like I've finished all the reports I wanted for now
and will be moving on to fixing and improving the EMSI/modem part
(which, hopefully, will also be used in my planned Fidonet mailer/tosser/nntp sever software).
You realy did a great job with all this. It is very usefull to me
in my attempts to promote IPv6 in Fidonet. Keep up the good work!
Thank you for the kind words! I've also decided to sign a contract
with Vodafone for my new rented apartment in London, since they
provide IPv6. So they should probably pay you a percentage of my
bills, because you encouraged me to switch to an IPv6-enabled provider
;))
Now that you mention it... There is just one categorie I have not seen yet: IPv6 only nodes. AFAIK here are just two of them at the moment
but this number may rise in the foreseeable future. Hpw about adding
"IPv6 only" to IPv6 Analytics?
Wouw! I see that you already added that category.
And I am surprised. There er 9 entries. I expected just 2. 280/5006
and 450/5858. The later is not present as he is off-line at the
moment. The other eight apparently advertise IPv4 connectivity but do
not have it working. Surprise!
Now that you mention it... There is just one categorie I have not
seen
yet: IPv6 only nodes. AFAIK here are just two of them at the
moment but this number may rise in the foreseeable future. Hpw
about adding "IPv6 only" to IPv6 Analytics?
Wouw! I see that you already added that category.
Thank you for the kind words! I've also decided to sign a
contract with Vodafone for my new rented apartment in London,
since they provide IPv6. So they should probably pay you a
percentage of my bills, because you encouraged me to switch to an
IPv6-enabled provider ;))
What took you so long? ;-)
Hello, Michiel!
Friday October 17 2025 14:20, you wrote to me:
Now that you mention it... There is just one categorie I have not
seen yet: IPv6 only nodes. AFAIK here are just two of them at the
moment but this number may rise in the foreseeable future. Hpw about
adding "IPv6 only" to IPv6 Analytics?
Wouw! I see that you already added that category.
Oops! You've caught me in the process of adding and testing new code, which could be incorrect... ;)
My code lacked proper INO4 flag support, and I am still fixing
remaining bugs. Please check the "History" button to see the test
results - sometimes IPv6 only node is simply a misconfigured node that
has lost IPv4 access.
The result may not have been what you intended, but it did reveal an interesting category that I did not expect: nodes with working IPv6
with advertised but non working IPv4. Pleas keep it as a seperate caregory.
Hello, Michiel!
Friday October 17 2025 17:50, you wrote to me:
The result may not have been what you intended, but it did reveal
an interesting category that I did not expect: nodes with working
IPv6 with advertised but non working IPv4. Pleas keep it as a
seperate caregory.
Jawel, kapitein! ;)
I've finished all the analytics changes - feel free to send me any new ideas later, since I don't have any..
And thank you for your effort in promoting IPv6!
What I liked and what I miss in the latest version is the showing of
the IPv6 address(es) when hovering the mouse cursor over the host name field. It is how I quickly spotted a host name with a ULA. I'd like to have it back. The new addition of fields for copying the host name,
And just one more thing I'd like: Splitting up the IPv6 only category
in two. One just like the one you have now, IPv6 noes with non
functioning IPv4 and the other for pure IPv6 only nodes, nodes that
only advertise one or more IPv6 addresses and no IPv4 address at all.
It could be a browser incompatibility issue - I just found that it
wasn't working in my Safari, but working in Firefox. I've made some changes - could you try again and refresh the page with clearing
cache? Not sure which browser you are using, so don't know the exact shortcut.
And just one more thing I'd like: Splitting up the IPv6 only
category in two. One just like the one you have now, IPv6 noes
with non functioning IPv4 and the other for pure IPv6 only nodes,
nodes that only advertise one or more IPv6 addresses and no IPv4
address at all.
Done! "Pure IPv6 Only".
It still does not work. Hovering over the "red" protocols to disp;ay
the error still works howver. I am using Firefox 115.28.0esr 32 bit. A somewhat older version that still works on Win8.
I've tried it (64-bit version, though I don't think there's a
difference) and it works:
https://s.5001.ru/-M9SfB7oahc
Please try reloading the page with Ctrl+F5 to bypass cache.
| Sysop: | Weed Hopper |
|---|---|
| Location: | Clearwater, FL |
| Users: | 16 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 16:57:32 |
| Calls: | 133 |
| Files: | 50,534 |
| D/L today: |
107 files (17,165K bytes) |
| Messages: | 323,283 |
