FidoNews · Vol 35, No 53 · 31 Dec 2018
The F I D O N E W S Volume 35, Number 53 31 Dec 2018
+--------------------------+-----------------------------------------+
| |The newsletter of the | | |
| | FidoNet community. | | Netmail attach to (POTS): |
| | | | Editor @ 2:2/2 (+46-31-960447) |
| | ____________| | |
| | / __ | Netmail attach to (BinkP): |
| | / / \ | Editor @ 2:203/0 |
| | WOOF! ( /|oo \ | |
| \_______\(_| /_) | Email attach to: |
| _ @/_ \ _ | b @ felten dot se |
| | | \ \\ | |
| | (*) | \ ))| |
| |__U__| / \// | Editor: Björn Felten |
| ______ _//|| _\ / | |
| / Fido \ (_/(_|(____/ | Newspapers should have no friends. |
| (________) (jm) | -- JOSEPH PULITZER |
+--------------------------+-----------------------------------------+
Table of Contents
1. GENERAL ARTICLES ......................................... 1
IPv6 in 2018 ............................................. 1
2. LIST OF FIDONET IPV6 NODES ............................... 4
List of IPv6 nodes ....................................... 4
3. JAMNNTPD SERVERS LIST .................................... 7
The Johan Billing JamNNTPd project ....................... 7
4. SPECIAL INTEREST ......................................... 8
Statistics from the Fidoweb .............................. 8
Nodelist Stats ........................................... 9
5. FIDONEWS INFORMATION ..................................... 11
How to Submit an Article ................................. 11
Credits, Legal Infomation, Availability .................. 13
FIDONEWS 35-53 Page 1 31 Dec 2018
=================================================================
GENERAL ARTICLES
=================================================================
IPv6 in 2018
By Michiel van der Vlist, 2:280/5555
Another year has passed. When we compare the statistics as published
by the end of 2017 with those of today, we see that IPv6 in Fidonet
has grown again. From 64 to 78 nodes.
80 -|
| .
-|
|
70 -|
|
-| .
| N
60 _|
|
_|
| .
50 _|
|
_|
|
40 _| .
|
_|
|
30 _|
|
_| .
|
20 _|
|
_|
|
10 _| .
|
_| .
| .
0 _|________._____________________________________________
| | | | | | | | | |
2010 2011 2012 2013 2014 2015 2016 2017 2018 2019
The growth went from exponentiual in the first five years to almost
lineair since 2015. Until the end of 2015, the number almost doubled
every year. In 2016 we had a mere net increase of 12 nodes. I say
"net" because in 2016, not only did we see new IPv6 nodes, we also
saw nodes disappear from the list. Some stopped supporting IPv6, some
FIDONEWS 35-53 Page 2 31 Dec 2018
left Fidonet altogether. This trend continued in 2017 and 2018. A net
increase of 13 nodes in 2017 and 14 in 2018.
In the first half of 2018 we saw a quick rise in the number of IPv6
nodes. Mostly from Eastern Europe. The number even rose to 82 and for
a moment it looked like we would reach 100 by the end of the year.
But then it levelled off and by clearing out the dead would it
dropped below 80 again.
Other than that, 2018 was not all that eventfull regarding IPv6. Not
for Fidonet en not for the Internet in general. We saw steady growth
but there is not much more exciting to report.
Infortunately we can not easely compare the growth of IPv6 for the
Internet in general to the growth of IPv6 in Fidonet. The statistics
published for the Internet show traffic flow in bits/second. All we
know about IPv6 in Fidonet is the number of nodes supporting it. It
is a fair assumption that this is not representative for the flow
measured in bits as the IPv6 nodes are presumably more active than
the average node and there surely is a lot more dead wood in the
nodelist among the IPv4 only nodes. So we can't easely translate the
percentage of numbers of nodes to percentage of flow. A safe
assumption would be that latter is higher, but that is all I dare
say about it.
I can' t even tell for my own system how much of the traffic is in
IPv4 or IPv6. A clever log analyser may tell, but presently there are
no such tools available.
What we did not see in 2017 and still have not seen in 2018 either
is the coming of systems that no longer have a public IPv4 address
because their provider converted them to a DS-Lite connection. The
exhaustion of the IPv4 address space not only makes IPv6 unavoidable,
it also makes it unavoidable that at least part of the internet
community will have to make do with a DS-Lite connection and so no
longer has a public IPv4 address. The trend that providers, mostly
in Europe and Australasia, are switching to DS-lite continues. Some
providers only put new customers on DS-Lite and allow existing
customers to keep their public IPv4 address, others move existing
customers to DS-Lite as well. It has not affected Fidonet yet, but I
expect that to be a matter of time. DS-Lite is unavoidable and it
will affect Fidonet. If not next year, then surely in the years to
come.
Fidonet will survive the exhaustion of IPv4 addresses. But only for
those that move to IPv6. Unfortunately like in the Big Bad World
there are people that are in denial regarding global warming, there
is a non negligible fraction of Fidonet sysops that are in denial
regarding IPv6. They seem to think that it is just a conspiracy to
extract more money from the cutomers, a hoax or a hype that will blow
over.
Well, it ain't. IPv4 address exhaustion is real and IPv6 is
unavoidable. Those that remain in denial will eventually be left
behind. It may take a while, maybe another decade, but running a
Fidonet node on an IPv4 only connection will eventually lead to
FIDONEWS 35-53 Page 3 31 Dec 2018
isolation. IPv6 is a must, not an option.
Happy IPv6 in 2019.
-----------------------------------------------------------------
FIDONEWS 35-53 Page 4 31 Dec 2018
=================================================================
LIST OF FIDONET IPV6 NODES
=================================================================
List of IPv6 nodes
By Michiel van der Vlist, 2:280/5555
Updated 30 Dec 2018
Node Nr. Sysop Type Provider Remark
1 2:280/464 Wilfred van Velzen Native Xs4All f
2 2:280/5003 Kees van Eeten Native Xs4All f
3 2:5019/40 Konstantin Kuzov T-6in4 he.net f PO4
4 2:240/1661 Markus Reschke Native DTAG f
5 2:280/5555 Michiel van der Vlist Native Ziggo f
6 1:320/219 Andrew Leary Native Comcast f
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 f
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 Spectrum f
13 2:203/0 Björn Felten T-6in4 he.net
14 2:280/5006 Kees van Eeten Native Xs4All f INO4
15 3:712/848 Scott Little T-6RD iiNet f IO
16 2:5020/545 Alexey Vissarionov Native Hetzner f
17 1:103/17 Stephen Hurd T-6in4 he.net
18 2:5020/9696 Alexander Skovpen T-6to4 Westlan
19 2:301/812 Benoit Panizzon Native IMPNET
20 2:421/790 Viktor Cizek T-6in4 he.net
21 2:222/2 Kim Heino Native TeliaSonera
22 3:633/280 Stephen Walsh Native AusNetServers f
23 2:463/877 Alex Shuman Native Nline f IO
24 1:19/10 Matt Bedynek T-6in4 he.net
25 3:770/1 Paul Hayton T-6in4 he.net
26 2:5053/58 Alexandr Kruglikov Native Aruba S.p.a f
27 1:103/1 Stephen Hurd Native Choopa
28 3:633/281 Stephen Walsh Native Internode
29 2:310/31 Richard Menedetter T-6in4 he.net
30 3:633/410 Tony Langdon Native IINET
31 2:5005/33 Evgeny Zyatkov Native RUCITYCONNECT f
32 2:5020/329 Oleg Lukashin Native Comfortel
33 2:246/1305 Emil Schuster Native TAL.DE
34 2:2443/1313 Dirk Astrath Native VOLMARNET
35 2:2448/4000 Tobias Burchhardt Native DTAG IO
36 2:331/51 Marco d'Itri Native BOFH-IT
37 1:214/22 Ray Quinn T-6to4 AT&T f
38 1:154/30 Mike Miller Native LINODE
39 1:282/1031 Jeff Smith Native Qwest
40 2:5083/444 Peter Khanin Native OVH
41 2:5001/100 Dmitry Protasoff Native Hetzner
42 2:5059/38 Andrey Mundirov T-6in4 he.net
43 2:221/10 Tommi Koivula Native OVH
44 2:240/5853 Philipp Giebel Native Hetzner
FIDONEWS 35-53 Page 5 31 Dec 2018
45 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
46 1:123/10 Wayne Smith T-6in4 he.net
47 2:5021/46 Dmitry Komissarov Native THEFIRST
48 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
49 2:5080/102 Stas Degteff T-6to4 Novator
50 1:135/300 Eric Renfro Native Choopa
51 1:135/371 Eric Renfro Native Cox Comm
52 1:103/13 Stephen Hurd Native Choopa
53 2:5020/1042 Michael Dukelsky Native FORPSI Ktis f
54 2:5095/0 Sergey V. Efimoff T-6in4 he.net
55 2:5095/20 Sergey V. Efimoff T-6in4 he.net
56 2:5030/74 Michael Skolsky Native RU-SKNT 6DWN
57 4:902/26 Fernando Toledo T-6in4 he.net
58 2:400/2992 Avshalom Donskoi Native OVH f PM*1
59 2:5019/400 Konstantin Kuzov Native LT-LT
60 2:467/239 Mihail Kapitanov T-6in4 he.net f
61 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
62 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
63 2:5020/736 Egor Glukhov Native VPSVILLE f
64 2:280/2000 Michael Trip Native Xs4All
65 2:230/38 Benny Pedersen Native Linode
66 2:460/58 Stas Mishchenkov T-6in4 he.net f
67 1 135/367 Antonio Rivera Native RRSW-V6
68 2:5020/2123 Anton Samsonov T-6in4 he.net
69 2:5020/2332 Andrey Ignatov Native ru.rtk
70 1:340/201 Michael Pierce Native ComCast
71 2:5005/49 Victor Sudakov T-6in4 he.net
72 2:5005/77 Valery Lutoshkin T-6in4 NTS f
73 2:5005/106 Alexey Osiyuk T-6in4 he.net f
74 1:153/757 Alan Ianson Native TELUS
75 2:5057/53 Ivan Kovalenko T-6in4 he.net f
76 2:5020/921 Andrew Savin Native Starlink
77 2:5010/352 Dmitriy Smirnov Native EkranTV f
78 2:292/854 Ward Dossche Native Belgacom OO
T-6in4 Static 6in4
T-AYIY Dynamic AYIYA
T-6to4 6to4
T-6RD 6RD
Remarks:
f Has a ::f1d0:<zone>:<net>:<node> style host address
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 listed or does not advertise an
IPv6 address in the Fidonet nodelist yet.
*1 IPv6 address: 2001:41d0:303:69c6:f1d0:2:400:2992
FIDONEWS 35-53 Page 6 31 Dec 2018
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 for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
and up). If the destination address is a 6to4 tunnel address
(2002::/16) many OSs default to IPv4 if an IPv4 address is present.
Submitted on day 364
-----------------------------------------------------------------
FIDONEWS 35-53 Page 7 31 Dec 2018
=================================================================
JAMNNTPD SERVERS LIST
=================================================================
The Johan Billing JamNNTPd project
This is a list of known JamNNTPd servers working. They are essentially
the modern version of Bulletin Board Systems.
You connect to them using the newsreader of your choice and you don't
need any other software installed on your computer -- regardless of
operating system -- but that favourite mail client of yours.
Even smart phones can handle this, giving you the opportunity to get
your daily doses of fidonet on the bus, tram or train on the way to
your job, school or whatever.
Updated 2018-09-29
URL news://eljaco.se
Join http://fidonews.eu
NETMAIL Yes, 2:203/2
URL news://rbb.bbs.fi
Join Info in group +GETACCESS+
NETMAIL Yes, 2:221/360
URL news://fidonews.mine.nu
Join http://fidonews.mine.nu
NETMAIL Yes, 2:221/6
URL nntp://news.bytemuseum.org
nntps://news.bytemuseum.org (secure)
Join Info in group +ACCCESS&SUPPORT+
NETMAIL Yes, 1:19/10
URL nntp://news.pharcyde.org
Join Info in group, +GETACCESS+
NETMAIL Yes, 1:154/10
URL: news.tequilamockingbirdonline.net
Join mailto:sysop@tequilamockingbirdonline.net
NETMAIL Yes, 1:266/404
-----------------------------------------------------------------
FIDONEWS 35-53 Page 8 31 Dec 2018
=================================================================
SPECIAL INTEREST
=================================================================
Last week's statistics from the Fidoweb
By EchoTime, 2:203/0
(Some nets may have lost their last
digit for technical reasons)
pkt (toss-toss) msg (write-toss)
nodes mean dev no mean dev no
154/* 22.0m 9.6m 315 1.5h 5.3h 315
201/* 2.4m 2.3m 26 8.1h 11.2h 25
221/* 4.0m 8.9m 275 5.7h 7.4h 275
230/* 50.9m 2.3m 2 0.2h 0.1h 2
240/* 2.7m 5.9m 10 11.5h 6.1h 10
280/* 3.6m 9.4m 412 5.8h 6.8h 412
292/* 4.2m 3.8m 32 4.2h 7.4h 31
320/* 4.1m 7.8m 297 2.6h 6.0h 297
502/* 0.7m 0.3m 8 2.0h 1.5h 8
Sigma 8.0m 11.8m 1377 4.1h 6.8h 1375
-----------------------------------------------------------------
FIDONEWS 35-53 Page 9 31 Dec 2018
Nodelist Stats
Input nodelist nodelist.362
size 196.8kb
date 2018-12-28
The nodelist has 1021 nodes in it
and a total of 1560 non-comment entries
including 4 zones
32 regions
174 hosts
81 hubs
admin overhead 291 ( 28.50 %)
and 133 private nodes
50 nodes down
65 nodes on hold
off line overhead 248 ( 24.29 %)
Speed summary:
>9600 = 62 ( 6.07 %)
9600 = 259 ( 25.37 %)
(HST = 6 or 2.32 %)
(CSP = 0 or 0.00 %)
(PEP = 0 or 0.00 %)
(MAX = 0 or 0.00 %)
(HAY = 0 or 0.00 %)
(V32 = 110 or 42.47 %)
(V32B = 30 or 11.58 %)
(V34 = 138 or 53.28 %)
(V42 = 100 or 38.61 %)
(V42B = 32 or 12.36 %)
2400 = 1 ( 0.10 %)
1200 = 0 ( 0.00 %)
300 = 699 ( 68.46 %)
ISDN = 57 ( 5.58 %)
-----------------------------------------------------
IP Flags Protocol Number of systems
-----------------------------------------------------
IBN Binkp 746 ( 73.07 %)
----------------------------------
IFC Raw ifcico 90 ( 8.81 %)
----------------------------------
IFT FTP 60 ( 5.88 %)
----------------------------------
ITN Telnet 156 ( 15.28 %)
----------------------------------
IVM Vmodem 10 ( 0.98 %)
----------------------------------
IP Other 5 ( 0.49 %)
----------------------------------
FIDONEWS 35-53 Page 10 31 Dec 2018
INO4 IPv6 only 0 ( 0.00 %)
----------------------------------
CrashMail capable = 868 ( 85.01 %)
MailOnly nodes = 333 ( 32.62 %)
Listed-only nodes = 27 ( 2.64 %)
[Report produced by NETSTATS - A PD pgm]
[ Revised by B Felten, 2:203/2]
[ NetStats 3.8 2014-11-23]
-----------------------------------------------------------------
FIDONEWS 35-53 Page 11 31 Dec 2018
=================================================================
FIDONEWS INFORMATION
=================================================================
How to Submit an Article
If you wish to submit an article for inclusion in the Fidonews, here
are some guidelines, if you send it as an attached file; the preferred
method if you want reasonable control over how the published article
will appear in the Fidonews:
a) Plain text. If you could type it on your keyboard, it's probably
quite OK. No line may be longer than 70 characters.
b) Put a title to the article. Put the title in two times. The first
time, on the first line, with an * before it. The second time, on
the second line, without the * and centered. This will help in the
format since the title with the * is removed and used in the index,
the second line will become the headline. On the third line, put
your name and FidoNet address, present or former. If former, you
may want to add some other address where you can be reached for
personal comments.
c) Deadline for article submission is Sunday, 22:00 UTC.
Help the Editor by following the above guides. Below are some subjects
and the file extension for the article as set in the configuration
file for the making of the Fidonews. Please help by putting the file
extension of the correct subject on the file name if known.
Ideas for Subject areas:
Subject File | Subject File
----------------------------------|----------------------------------
From the *C's *.css | Rebuttals to articles *.reb
Fidonet Regional News *.reg | Fidonet Net News *.net
Retractions *.rtx | General Fidonet Articles *.art
Guest Editorial *.gue | Fidonet Current Events *.cur
Fidonet Interviews *.inv | Fidonet Software Reviews *.rev
Fidonet Web Page Reviews *.web | Fidonet Notices *.not
Getting Fidonet Technical *.ftc | Question Of The Week *.que
Humor in a Fido Vein *.hfv | Comix in ASCII *.cmx
Fidonet's Int. Kitchen *.rec | Poet's Corner *.poe
Clean Humor & Jokes *.jok | Other Stuff *.oth
Fidonet Classified Ads *.ads | Corrections *.cor
Best of Fidonet *.bof | Letters to the Editor *.let
If you don't know or are not sure, send the article anyway. Put a .TXT
on it and I'll try to figure out where it should be in the Fidonews.
If you follow these simple guidelines, there should be little problem
in getting your article published. If your submission is too far out
of specs for the Fidonews, it will be returned to you and/or a message
sent informing you of the problem. This DOES NOT mean that your
article is not accepted. It means that there is something in it that I
can not fix and I need your help on it.
FIDONEWS 35-53 Page 12 31 Dec 2018
Send articles via e-mail or netmail, file attach or message to:
Björn Felten
Fidonet 2:2/2 or 2:203/0
E-Mail b @ felten dot se
Skype file bfelten
IMPORTANT! If you send the article via e-mail, make sure you put the
word "fidonews" somewhere in the subject line! That way it
will always pass the spam filter, ending up in the proper
folder.
Please include a message, telling me that you have sent an article.
That way I will know to look for it.
-----------------------------------------------------------------
FIDONEWS 35-53 Page 13 31 Dec 2018
Credits, Legal Infomation, Availability
+ -- -- -- -- -- -- -- -- FIDONEWS STAFF - -- -- -- -- -- -- -- +
| |
| Editor: Björn Felten, 2:2/2 |
| |
+ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +
+ -- -- -- -- -- -- -- - EDITORS EMERITI - -- -- -- -- -- -- -- +
| |
| Tom Jennings, Thom Henderson, Dale Lovell, Vince |
| Perriello, Tim Pozar, Sylvia Maxwell, Donald Tees, |
| Christopher Baker, Zorch Frezberg, Henk Wolsink, |
| Doug Meyers, Warren D. Bonner, Frank L. Vest |
| |
+ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +
Fidonews is published weekly by and for the members of Fidonet.
There is no copyright attached to Fidonews, though authors
retain rights to their contributed articles. Opinions expressed
by the authors are strictly their own. Noncommercial duplication
and distribution within Fidonet is encouraged. Authors are
encouraged to send their articles in ASCII text to the Editor
at one of the addresses above.
The weekly edition of Fidonews is distributed through the file
area FIDONEWS, and is published as echomail in the echo FIDONEWS.
The different articles are distributed in the file area SNOOZE.
A service to various projects for making Fidonews available on
the web with a more pleasing lay-out.
These sources are normally available through your Network
Coordinator. The current and past issues are also available from
the following sources:
+ -- -- -- -- -- -- - FIDONEWS AVAILABILITY - -- -- -- -- -- -- +
| |
| File request from 2:2/2 or 2:203/0: |
| current issue FIDONEWS |
| back issue, volume v, issue ii FNEWSvii.ZIP |
| articles, vol.no nn, issue ii INPUnnii.ZIP |
| |
| On the web: |
| http://eljaco.se/FILES/fnews/ |
| http://fidonews.eu/FNEWS/ |
| |
| The Snooze *and* the FIDONEWS echo in your newsreader: |
| news://eljaco.se/FIDONEWS |
| |
+ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +
-----------------------------------------------------------------
Download original FidoNews · Volume 35 (2018) · ← Previous · Next →