• FidoNews 42:01 [00/08]: The Front Page

    From FidoNews Robot@2:2/2 to All on Monday, January 06, 2025 00:07:16
    The F I D O N E W S Volume 42, Number 01 06 Jan 2025 +--------------------------+-----------------------------------------+
    | |The newsletter of the | | |
    | | FidoNet community. | | Netmail attach to (POTS): |
    | | Est. 1984 | | 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__| / \// | Publisher: Björn Felten |
    | ______ _//|| _\ / | |
    | / Fido \ (_/(_|(____/ | Newspapers should have no friends. |
    | (________) (jm) | -- JOSEPH PULITZER | +--------------------------+-----------------------------------------+


    Table of Contents
    1. FOOD FOR THOUGHT ......................................... 1
    2. GENERAL ARTICLES ......................................... 2
    IPv6 only experiment ..................................... 2
    3. LIST OF FIDONET IPV6 NODES ............................... 5
    List of IPv6 nodes ....................................... 5
    4. JAMNNTPD SERVERS LIST .................................... 8
    The Johan Billing JamNNTPd project ....................... 8
    5. FIDONEWS'S FIDONET SOFTWARE LISTING ...................... 9
    6. SPECIAL INTEREST ......................................... 17
    Statistics from the Fidoweb .............................. 17
    Nodelist Stats ........................................... 18
    7. FIDONEWS INFORMATION ..................................... 20
    How to Submit an Article ................................. 20
    Credits, Legal Infomation, Availability .................. 22

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, January 06, 2025 00:07:16
    =================================================================
    FOOD FOR THOUGHT =================================================================

    People have a lot to say about lives they've never lived.

    -- Mindful Maven 2024

    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, January 06, 2025 00:07:16
    =================================================================
    GENERAL ARTICLES =================================================================

    IPv6 only experiment
    By Michiel van der Vlist, 2:280/5555

    In my last week's (or last year's if you want) article *1) I mentioned
    Alex Haydock's IPv6 only project. *2) This inspired me to have a look
    at how Fidonet systems would behave in such an environment. My conclu-
    sion was that the "problem" of literal IPv4 addresses in the nodelist
    can be worked around by using binkp.net. At the end of that part I
    wrote: "Did I test this? Yes of course! See next week's article..."

    So here it is: a report of what I tested and how.

    I choose to not build an entire IPv6 only environment like Alex
    Haydock did but to use the minumum required for the test I had in
    mind. Just a single system with IPv6 only access: The laptop running
    my point system. That laptop (a Dell Latitude D620, running WIN7) has
    WiFi on board and an RJ45 connector for UTP cable. It has a manual
    switch to enable/disble the WiFi. So the first step was to switch off
    the WiFi and connect the laptop to the LAN with a cable. This allowed
    me to easely switch between the original setup and the IPv6 only
    setup. Just plug/unplug the cable and unset/set the WiFi switch.

    The second step was to disable IPv4 in the LAN cable interface.

    After doing that I found out I no longer had access to the Internet.
    It turned out the DNS servers of my provider (Caiway Fiber) do not
    work well in an IPv6 only environment. Malus point for Caiway! The DNS
    servers of my other provider (Ziggo) do not have that problem. No big
    deal because for the test I had in mind, I have to use other DNS
    servers anyway. I need DNS64 and NAT64 to be able to access IPv4 only
    systems. Contrary to Alex Haydock I do not have a provider that offers
    these services so I have to look elsewhere. Instead of building a
    NAT64 gateway myself just for this experiment, I decided to make use
    of a third party. The free service of Kasper Dupont was not hard to
    find. *3) All I had to do was to configure the wired LAN interface to
    use he following DNS servers:

    2a00:1098:2c::1
    2a01:4f8:c2c:123f::1
    2a01:4f9:c010:3f02::1

    These are DNS64 servers. For accessing IPv4 only systems they refer to
    his NAT64 gateway. That is all that is needed to create an IPv6 only environment with DNS64/NAT64 support.

    For details on the working of DNS64/NAT64: Google is your friend! *4)

    After configuring the above DNS servers binkd could connect to IPv6
    nodes and most IPv4 nodes in the nodelist. IPv6 nodes are connected
    as usual and IPv4 only nodes are connected via the NAT64 gateway.
    So to the other side they will appear to come from the IPv4 WAN
    address of the gateway. 95.216.219.126 in this case. It will back
    resolve to nat64.dyndns.dk. So if you have an IPv4 only binkp node
    and you see that in your logs with an incoming connection from
    2:280/5555.1 that was me testing.

    For nodes listed with a literal IPv4 address a work around is still
    needed. DSN64/NAT64 does not work with literal IPv4 addresses. The
    work around - as mentioned in my previous article *1) - is to use
    binkp.net. After manually configuring * for the literal adresses in
    binkd.cfg these nodes were connected without further problems.

    So running a Fidonet node in an IPv6 only environment is no problem.

    There are a few snags though. For one, it is not possible to connect
    to nodes that advertise IPv6 connectivity but do not actually support
    it. I could not connect to 240/8010. Binkd times out and that's it.
    There is no fall back to IPv4 in this configuration. Of course there
    isn't! This is IPv6 only remember!? So if we want to prepaire for an
    IPv6 only Internet, we'd better get used to that. But for those who
    are not quite ready for that there is a work around, but it is a bit
    more complicated. Configure [2a00:1098:2c::5:93.236.155.101] as the
    literal IPv6 address for binkd to connect. Here we bypass the DNS64
    and directly connect to the NAT64 gateway. 2a00:1098:2c::5: is the
    prefix used by the NAT64 gateway and 93.236.155.10 is the IPv4 address
    of the node in question. Writing the last 32 bits of an IPv6 address
    as an IPv4 quad is a legitimate way of writing an IPv6 address though
    not all applications may understand it. Apparently the WIn32 version
    of binkd does. Your milage may vary.

    This method could also be used to connect to IPv4 only nodes with a
    literal IPv4 address though it may not be practial.

    Authors of scripts that generate a configuration file for binkd from
    the nodelist may consider to add either method as an option.

    It goes without saying that incoming IPv6 is no problem in this confi- guration. It works as before.

    Incoming IPv4... Well, there isn't. Not in this IPv6 only configura-
    tion. In my, now 7+ year old DS-Lite emulation experiments *4-8), I demonstrated that running an IPv6 node without incoming IPv4 is do-
    able. And for those who can not or do not want to renounce incoming
    IPv4 yet, there is Feste-ip.net. *7) But maybe we should just forego
    incoming IPv4 for a while to entice the IPv4 only sysops of Fidonet to
    adopt IPv6. :-)

    As a side note: I wonder how long Kasper Dupont will continue this
    service. It is free and open to all without any registration or other authorisation. I feel a bit uncomfortable about that, it looks like a
    recipe for abuse. But he has been running it for over five years now,
    so it may not be a serious problem. So it feels OK for a short and
    simple test.

    Another problem with public NAT64 gateways is similar to the problem
    with the 6to4 tunnels that some of us are still using: services using geolocation to grant access may get confused because all traffic seems
    to come from the gateway, not from the originator. Not a problem for
    Fidonet I'd say, but for other use it may be.

    For those and some other reasons I would prefer a NAT64 gateway run
    by my provider if I ever start to use this permanently. I have two
    providers at the moment and neither of them provides such a service.
    I may make that a goal for the coming year. Or next year...


    References:

    1) FN 41:53 Dec 2024 IPv6 in 2024
    2) https://blog.infected.systems/posts/2024-12-01-no-nat-november/
    3) https://nat64.net/
    4) https://en.wikipedia.org/wiki/IPv6_transition_mechanism
    5) FN 34:31 Jul 2017 DS-Lite emulation experiment v2.0
    6) FN 34:37 Sep 2017 DS-Lite emulation experiment 2.0, the results
    7) FN 34:33 Aug 2017 DS-Lite: a solution
    8) FN 34:38 Sep 2017 DS-Lite Emulation experiment v2.1



    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, January 06, 2025 00:07:16
    =================================================================
    LIST OF FIDONET IPV6 NODES =================================================================

    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 4 Jan 2025


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen Native Freedom f
    2 2:280/5003 Kees van Eeten Native KPN f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo/Caiway f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Elisa f
    7 2:221/6 Tommi Koivula Native OVH
    8 1:154/10 Nicholas Boel Native Spectrum f
    9 2:203/2 Bjorn Felten T-6in4 he.net
    10 2:280/5006 Kees van Eeten Native KPN f INO4
    11 3:712/848 Scott Little T-6in4 he.net f
    12 2:5020/545 Alexey Vissarionov T-6in4 he.net f
    13 1:103/17 Stephen Hurd T-6in4 he.net
    14 2:5020/9696 Alexander Skovpen T-6in4 IP4Market
    15 2:421/790 Viktor Cizek Native CZ-IJC-20071015
    16 2:222/2 Kim Heino Native TeliaSonera
    17 3:633/280 Stephen Walsh Native AusNetServers f
    18 1:19/10 Matt Bedynek T-6in4 he.net
    19 3:770/1 Paul Hayton Native VETTA
    20 3:770/100 Paul Hayton Native VETTA
    21 2:5053/58 Alexander Kruglikov Native ER-Telecom f
    22 1:103/1 Stephen Hurd Native Choopa
    23 3:633/281 Stephen Walsh Native Internode
    24 2:310/31 Richard Menedetter Native DE-NETCUP f
    25 3:633/410 Tony Langdon Native IINET
    26 2:5020/329 Oleg Lukashin Native Comfortel f
    27 2:331/51 Marco d'Itri Native BOFH-IT
    28 1:154/30 Mike Miller Native LINODE
    29 2:5001/100 Dmitry Protasoff Native Layer7 Networks
    30 2:5059/38 Andrey Mundirov T-6in4 he.net
    31 2:5083/444 Peter Khanin Native OVH
    32 2:240/5413 Ingo Juergensmann Native RRBONE-COLO f
    33 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    34 1:103/13 Stephen Hurd Native Choopa
    35 2:5020/1042 Stas Mishchenkov T-6-in4 he.net f
    36 2:5019/400 Konstantin Kuzov Native LT-LT
    37 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    38 2:5010/275 Evgeny Chevtaev T-6in4 IP4Market f
    39 2:280/2000 Michael Trip Native KPN
    40 2:230/38 Benny Pedersen Native Linode
    41 2:460/58 Stas Mishchenkov T-6in4 he.net f
    42 2:5101/1 Andrey Ignatov Native HETZNER
    43 2:5005/49 Victor Sudakov T-6in4 he.net f
    44 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    45 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    46 2:5010/352 Dmitriy Smirnov Native SAGE-SU-V6
    47 2:292/854 Ward Dossche Native Proximus
    48 2:469/122 Sergey Zabolotny T-6in4 he.net f
    49 2:5053/400 Alexander Kruglikov Native FirstVDS f
    50 2:5030/1997 Alexey Fayans T-6in4 he.net
    51 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    52 2:240/502 Ludwig Bernhartzeder Native DTAG
    53 2:423/39 Karel Kral Native WEDOS
    54 2:280/1049 Simon Voortman Native Solcon
    55 2:335/364 Fabio Bizzi Native OVH
    56 1:124/5016 Nigel Reed Native DAL1-US f
    57 2:5030/1520 Andrey Geyko T-6in4 he.net f
    58 1:229/664 Jay Harris Native Rogers f
    59 2:280/2030 Martien Korenblom Native Transip
    60 3:633/509 Deon George Native Telstra
    61 2:5020/4441 Yuri Myakotin Native SOVINTEL
    62 1:320/319 Andrew Leary Native Comcast f
    63 2:240/5824 Anna Christina Nass Native DTAG f
    64 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
    65 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    66 2:301/812 Benoit Panizon Native WOODYV6
    67 1:229/616 Vasily Losev Native GIGEPORT
    68 2:301/113 Alisha Stutz T-6in4 he.ne
    69 1:153/7715 Dallas Hinton Native Shaw Comms
    70 1:218/840 Morgan Collins Native Linode
    71 2:5020/921 Andrew Savin Native HURRICANE-IPV6-24
    72 2:240/1634 Hugo Andriessen Native Vodafone
    73 2:280/2040 Leo Barnhoorn Native KPN f
    74 2:5020/736 Egor Glukhov Native RUWEB f
    75 2:221/10 Tommi Koivula Native Hetzner f INO4
    76 1:218/850 John Nicpon Native LINODE-US
    77 2:301/1 Alisha Stutz Native CH-DATAWIRE
    78 2:5035/63 Vladimir Goncharov Native RFEIV6NET
    79 2:5020/290 Andrew Kolchoogin T-6in4 he.net
    80 1:214/22 Ray Quinn T-6in4 he.net
    81 2:5030/49 Sergey Myasoedov Native FR-VIRTUA-SYSTEMS
    82 1:218/820 Ryan Fantus Native DIGITALOCEAN
    83 1:103/705 Rob Swindell Native Spectrum f
    84 1:135/395 Charles Blackburn Native Charter Comms
    85 1:134/303 Travis Mehrer Native Shaw Comms
    86 2:5057/19 Max Vasilyev Native ER-Telecom f
    87 2:5075/35 Eugene Subbotin Native RUWEB f
    88 2:5075/37 Andrew Komardin Native IHC
    89 2:5075/128 Eugene Subbotin T-6in4 IP4Market f
    90 2:550/278 Vladislav Muschinskikh Native FirstByte
    91 2:5010/278 Vladislav Muschinskikh T-6in4 he.net f
    92 2:240/5411 Stephan Gebbers Native DTAG
    93 2:5020/715 Alex Barinov T-6in4 he.net f
    94 1:16/201 Sergey Myasoedov Native Amazon
    95 1:104/117 Vitaliy Aksyonov Native LLC
    96 2:5030/1340 Dmitry Afanasiev T-6in4 TUNNEL-BROKER-NET
    97 2:221/360 Tommi Koivula Native Elisa f
    98 2:5031/25 Alex Kazankov Native VDSINA
    99 4:902/26 Fernando Toledo Native Claro
    100 2:280/2050 Floris van Unen Native Azure
    101 2:280/2060 Dennis Slagers Native Ziggo f
    102 2:467/4 Ruslan Suleimanov T-6in4 he.net
    103 2:467/888 Ruslan Suleimanov T-6in4 he.net f
    104 1:266/625 Scott Street Native Verizon
    105 2:5020/5452 Alex Barinov T-6in4 he.net
    106 2:5030/723 Alexey Khromov Native RU-AI-20240222
    107 3:633/2744 Deon George Native EXETEL-AU
    108 4:930/1 David Gonzalez Native EPMNET
    109 3:633/267 Andrew Clarke Native widebandnetv6 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.
    Example: ::f1d0:2:280:5555 (for node 2:280/5555)
    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.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    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.


    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 when compiled with AF_FORCE=1). 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 005


    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, January 06, 2025 00:07:16
    =================================================================
    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 2023-09-06


    URL news://eljaco.se:4119
    Join http://fidonews.eu
    NETMAIL Yes, 2:203/2

    URL nntp://rbb.fidonet.fi
    Join https://news.fidonet.fi
    NETMAIL Yes, 2:221/360

    URL nntp://fidonews.mine.nu
    URL nntps://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


    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, January 06, 2025 00:07:16
    =================================================================
    FIDONEWS'S FIDONET SOFTWARE LISTING =================================================================



    =================================================================
    FIDONET SOFTWARE LISTING
    =================================================================

    BBS Software List

    Updated 2024-11-15

    Maintained by Andrew Leary (1:320/219)
    Editors Emeritus: Robert Couture, Janis Kracht,
    Sean Dennis

    M=Mailer T=Tosser B=BBS D=Door C=Comm/Terminal
    P=Points E=Editor I=Internet U=Utility #=Info
    F=TIC/SRIF Processor

    *=Software is available and may be registerable,
    but no longer supported or updated.

    @=Website is operating but is no longer updated.

    ?=Software's updating/support status is unknown.

    O=Software is open source.

    This list contains BBS-related software that is available
    for registration (not necessarily supported), open source
    software and actively developed/supported software by its
    author. Software listed may be available for DOS, Linux,
    OS/2 (eComStation), Windows (16 or 32 bit) and OSX.

    .- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -.
    |Software: Author |Type |URL, Contact, Ver, Notes Help Node|
    `- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -'

    ==> FRONT-END/INTERNET MAILERS

    Argus |MI*? |http://www.ritlabs.com/en/products
    | | /argus/
    | | v3.210 on 2001-03-29

    BinkleyTerm XE |MO* |http://btxe.sourceforge.net
    | | 2.60XE Beta-XH7 on 2000-10-22

    BinkD |MI? |http://binkd.grumbler.org
    | | gul@gul.kiev.ua 2:463/68
    | | v.1.0.4
    | | v.1.1a-115 (alpha)
    | | ftp://cvs.happy.kiev.ua/pub/fidosoft
    | | /mailer/binkd/
    | |http://www.filegate.net/r50/aftnbinkd/

    D'Bridge |MTCPE|http://www.dbridgemailer.com
    |I | support@dbridgemailer.com 1:1/130
    Nick Andre | | v4.00 on 2024-11-12

    FIDO-Deluxe IP |MPUI |http://www.datenbahn.dd-dns.de/
    | | cdp/fp_deluxe/
    | | v2.4 on 2003-09-26

    FrontDoor, FD/APX: |MITPC|http://www.defsol.se
    Definite Solutions |E | sales@defsol.se
    | | FD v2.33ml, FD/APX v1.15

    InterMail |MCPE |http://www.Intermail.net 1:106/201
    Dale Barnes | | dalebarnes42@majik.net
    | | IM v2.60 on 2017-08-28

    Husky Project |MTPUI|http://husky.sourceforge.net/
    |EO? | v1.9 RC2 on 2010-04-20

    Taurus |MI |http://www.fidotel.com/public/forums/
    (based on Radius) |? | taurus/index.htm
    | | v5.0 on 2006-06-12
    | |

    T-Mail |MI |http://www.tmail.spb.ru (Russian only)
    |? | v2608 on 2001-12-12

    AfterShock |MTEI |https://play.google.com/store/apps/
    Asvcorp | | details?id=com.asvcorp.aftershock
    Anatoly Vdovichev | | rudi.timmermans@mailfence.com
    Rudi Timmermans | | v1.7.1 on 2022-11-30 2:292/140

    HotDogEd |E |https://play.google.com/store/apps/
    Sergey Pushkin | | details?id=com.pushkin.hotdoged
    | | v2.13.5 on 2017-03-13 2:5020/2141

    HotDogEd FidoNet |MTI |https://play.google.com/store/apps/
    Provider | | details?id=com.pushkin.hotdoged.fido
    Sergey Pushkin | | v2.13.5 on 2017-03-13 2:5020/2141

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    MAIL TOSSERS

    Crashmail II |TO |http://ftnapps.sourceforge.net/
    | | crashmail.html

    FastEcho |T |http://www.softeq.de/old/Products
    | | /FastEcho/fastecho.html
    | | v1.46.1 on 2007-11-13
    | | Registration keys are free & available
    | | by request from the author

    Fidogate |TUI? |http://www.fidogate.org
    | | v4.4.10 on 2004-08-27
    | |

    FMail |TO |https://sourceforge.net/projects/fmail/
    | | v2.3.1.0 on 2024-03-30 2:280/464

    InterEcho |T |http://www.Intermail.net 1:220/60
    Dale Barnes | | dalebarnes42@majik.net
    | | IE 1.20 on 2017-08-28

    JetMail: JetSys |TU |
    (ATARI ST only) | | v1.01 on 2000-01-01

    Squish |T* |http://www.filegate.net/maximus_bbs/
    | | v1.11R2 on 2009-01-01
    | | Source code available in Maximus BBS
    | | archive: http://maximus.sourceforge.net


    WWIVToss |T |http://www.weather-station.org/wwiv/
    | | v1.51 on 2015-05-23

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    BBS SOFTWARE

    BBBS |BICTM|http://www.bbbs.net 2:222/2
    | | b@bbbs.net
    | | v4.01 on 2007-01-28

    EleBBS |BO*? |http://www.elebbs.com
    | | v0.10.RC1 on 2002-06-09

    Enthral BBS |B |http://enthralbbs.com
    Linux/BSD/OSX | | v0.429/Alpha on 2010-10-14
    | | Fidonet filebone SCENEENT

    Ezycom BBS |BT* |http://www.ezycom-bbs.com
    | | v2.15g2 on 2009-11-16

    GT Power |B |http://www.gtpowerbbs.com/
    | | v19.00

    Hermes II Project |BT |http://www.hermesbbs.com/
    Macintosh-based | | malyn@strangegizmo.com
    | | v3.5.10b3

    Maximus BBS |BO* |http://www.filegate.net/maximus_bbs/
    | | v3.03
    | | Source code available at:
    | | http://maximus.sourceforge.net/

    MBSE BBS |BMTFI|https://sourceforge.net 1:1/119
    |PO | /projects/mbsebbs
    | | ajleary@sourceforge.net
    | | v1.1.0 on 2024-07-13
    Meltdown BBS |UIO |http://meltdown-bbs.sourceforge.net/
    | | v1.0b on 2004-04-26

    Mystic BBS |BMTCE|http://www.mysticbbs.com
    |I | v1.12 A48 on 2023-01-15

    NiKom BBS (Amiga) |BO |http://www.nikom.org
    | | v2.3.1 on 2017-07-01

    RemoteAccess BBS |B? |http://www.rapro.com 1:1/120
    | | bfmorse@rapro.com
    | | v2.62.2SW on 2000-10-25

    Renegade BBS |B |http://renegadebbs.info 1:129/305
    | | v1.33/DOS on 2023-05-05

    Spitfire BBS |B? |http://www.buffalocrk.com/
    | | mdwoltz@buffalocrk.com
    | | v3.7 on 2010-01-01

    Synchronet BBS |BMTIO|http://www.synchro.net 1:103/705
    | | v3.19b on 2022-01-02

    Telegard BBS |B* |
    | | v3.09g2-sp4/mL on 1999-12-19

    WildCat! Interactive |MTBEI|http://www.santronics.com
    Net Server, Platinum| | sales@santronics.com
    Xpress: Santronics | |
    Software, Inc. | | v8.0 AUP 454.12 on 2021-05-14

    WWIV BBS |B |http://www.wwivbbs.org
    | | v5.6.1 on 2021-04-23

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    TIC PROCESSORS/FILEFIX/SRIF

    Allfix |FIUT |http://www.allfix.com/ 1:218/720
    Ken Johnson | | v6.1.0 on 2019-02-02

    NEF/pk |F |http://nefpk.8m.com/
    | | v2.45b2 on 2000-03-05

    TinyTIC |FO |http://ftnapps.sourceforge.net
    | | /tinytic.html

    VIReq |FO |http://ftnapps.sourceforge.net
    | | /vireq.html

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    BBS DOORS/UTILITIES

    Cheepware |DU |http://outpostbbs.net/cheepware.html
    Sean Dennis | | sysop@outpostbbs.net 1:18/200
    | | Fidonet filebone CH-WARE

    DDS (Doorware |D@ |http://www.doorgames.org
    Distribution System)| | ruth@doorgames.org
    Ruth Argust | |

    Jibben Software |D* |http://www.jibbensoftware.com/
    | | bbs-door-games.cfm
    | | scott@jibben.com
    | | 1995-99 Release dates

    John Dailey Software |DU |http://www.johndaileysoftware.com

    Shining Star |D* |http://www.shiningstar.net/bbsdoors/
    | | nannette@shiningstar.net
    | | Doors are registerable via website

    Sunrise Doors: |D |http://www.sunrisedoors.com
    Al Lawrence | | al@sunrisedoors.com
    | | Tel: (404) 256-9518

    T1ny's Software |DU |http://www.tinysbbs.com/files/tsoft/
    Shawn Highfield | | shighfield@gmail.com 1:229/452
    | | Fidonet filebone CH-WARE

    The Brainex System |D |http://www.brainex.com/brainex_system/
    | | stanley@brainex.com
    | | 1994-99 Releases

    Trade Wars |D* |http://www.eisonline.com/tradewars/
    | | jpritch@eisonline.com
    | | v3.09 (DOS-32) in 2002

    Vagabond Software |DU* |http://vbsoft.dhakota.org
    | | d@dhakota.org
    | | Last update: 2008-04-11

    WWIVEdit |DE |http://www.weather-station.org/wwiv/
    | | v3.0 on 2011-06-27

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    +- - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - - - -+

    ==> POINT SOFTWARE

    APoint |PI |https://stargate.org.uk/apoint/
    | | v1.25 on 2001-12-12 (Win32)
    | | Needs the binkD Toolkit for Fido-over-IP
    | | which is available from the above URL.

    CrossPoint |P |http://www.crosspoint.de
    | | pm@crosspoint.de
    | | v3.12d on 1999-12-22 (DOS, Shareware)

    FreeXP |PO |http://www.freexp.de
    | | support@freexp.de
    | | v3.42 on 2020-09-25 (DOS)

    OpenXP |PIO |https://sourceforge.net/projects/openxp5/
    | |https://openxp.uk/
    | | dev@openxp.uk
    | | v5.0.51 on 2021-12-26
    | | (Win32, Linux(64-Bit})

    WinPoint |PI |http://www.winpoint.org/
    | | Tim Schattkowsky 2:240/1120.29
    | | v415.0 on 2023-02-17 (Win32)

    +- - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - - - -+

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    SYSOP MAIL EDITORS

    GoldEd+ |EO |http://golded-plus.sourceforge.net/
    | | v1.1.5 (Snapshot) on 2023-02-14
    | | NOTE: Unstable versions released often

    SqEd32 |E |http://www.sqed.de 2:2476/493
    | | v1.15 on 1999-12-15
    | | Website is in German and English

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    INTERNET UTILITIES

    Ifmail |UIO |http://ifmail.sourceforge.net
    | | crosser@average.org

    Internet Rex |UI? |http://members.shaw.ca/InternetRex/
    | | telnet://xanadubbs.ca 1:342/806
    | | v2.29 on 2001-10-21

    JamNNTPd |UIO |http://ftnapps.sourceforge.net
    | | /jamnntpd.html

    Luckygate |UO | ftp://happy.kiev.ua/pub/fidosoft/gate
    | | /lgate
    | | gul@gul.kiev.ua

    MakeNL |UO |http://makenl.sourceforge.net
    | | v3.5.0 on 2019-05-06

    PLMake |UOP |https://sourceforge.net/projects
    | | /plmake 2:280/464
    | | v2.1 beta on 2024-11-01

    ErrFlags |UO |http://sourceforge.net/projects
    | | /errflags 2:280/464
    | | v3.0.0 on 2023-02-21

    RNtrack |U |http://sourceforge.net/projects
    | | /ftrack-as 2:5080/102
    | |stas_degteff@users.sourceforge.net
    | | v2.1.10 on 2020-04-30

    TransNet |UIO? |http://www-personal.umich.edu/~mressl/
    | | transnet/index.html
    | | transnet@ressl.com.ar
    | | v2.11 on 2007-09-13

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    INFORMATIONAL WEBSITES/BBS LISTS

    Telnet/Dialup BBS |# |http://www.telnetbbsguide.com 1:275/89
    Guide | | Maintained by Dave Perrussel
    | | This is probably the most updated BBS
    | | list on the Internet for a general
    | | BBS list.

    Synchronet BBS List |# |http://www.synchro.net/sbbslist.html
    | | Maintained automatically
    | | This list is specifically for
    | | Synchronet-based BBS systems and is
    | | automatically updated nightly.

    The BBS Corner |# |http://www.bbscorner.com
    | | This website is more than just files,
    | | it's an encyclopedia of knowledge for
    | | BBS sysops and people who want to
    | | become sysops. This site is run by
    | | the same person who does the Telnet

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, January 06, 2025 00:07:16
    | | BBS Guide.

    BBS Nexus |# |https://bbsnexus.com
    | | This website offers a searchable list
    | | of Telnet BBS's.

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    File Archives:

    http://archives.thebbs.org
    http://sysopscorner.thebbs.org (site is no longer maintained)
    http://www.filegate.net/ (FTP access via port 60721)

    Note: Most also provide FTP access (use ftp instead of http above)

    The BBS Software List is published weekly in the FidoNews.

    If you have corrections, suggestions or additions to the information
    above, please contact Andrew Leary with your information via the
    FIDONEWS echo or netmail at 1:320/219.

    --------------------------------------------------------------------

    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, January 06, 2025 00:07:16
    =================================================================
    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

    201/* 1.1m 0.6m 8 0.0h 0.3h 8
    221/* 0.8m 0.5m 648 4.4h 5.0h 650
    280/* 0.7m 0.4m 671 6.6h 4.4h 671
    292/* 3.2m 1.4m 17 5.0h 3.0h 16
    320/* 2.7m 1.5m 262 1.6h 3.4h 262

    Sigma 1.1m 1.1m 1606 4.9h 4.8h 1607

    -----------------------------------------------------------------
    Nodelist Stats

    Input nodelist nodelist.003
    size 160.8kb
    date 2025-01-03

    The nodelist has 827 nodes in it
    and a total of 1209 non-comment entries

    including 4 zones
    30 regions
    157 hosts
    59 hubs
    admin overhead 250 ( 30.23 %)

    and 86 private nodes
    17 nodes down
    29 nodes on hold
    off line overhead 132 ( 15.96 %)


    Speed summary:

    >9600 = 20 ( 2.42 %)
    9600 = 89 ( 10.76 %)
    (HST = 2 or 2.25 %)
    (CSP = 0 or 0.00 %)
    (PEP = 0 or 0.00 %)
    (MAX = 0 or 0.00 %)
    (HAY = 0 or 0.00 %)
    (V32 = 43 or 48.31 %)
    (V32B = 10 or 11.24 %)
    (V34 = 53 or 59.55 %)
    (V42 = 38 or 42.70 %)
    (V42B = 9 or 10.11 %)
    2400 = 1 ( 0.12 %)
    1200 = 0 ( 0.00 %)
    300 = 717 ( 86.70 %)

    ISDN = 19 ( 2.30 %)

    -----------------------------------------------------
    IP Flags Protocol Number of systems -----------------------------------------------------
    IBN Binkp 710 ( 85.85 %) ----------------------------------
    IFC Raw ifcico 63 ( 7.62 %) ----------------------------------
    IFT FTP 36 ( 4.35 %) ----------------------------------
    ITN Telnet 102 ( 12.33 %) ----------------------------------
    IVM Vmodem 12 ( 1.45 %) ----------------------------------
    IP Other 1 ( 0.12 %) ----------------------------------
    INO4 IPv6 only 5 ( 0.60 %) ----------------------------------

    CrashMail capable = 758 ( 91.66 %)
    MailOnly nodes = 247 ( 29.87 %)
    Listed-only nodes = 18 ( 2.18 %)



    [Report produced by NETSTATS - A PD pgm]
    [ Revised by B Felten, 2:203/2]
    [ NetStats 3.8 2014-11-23]

    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, January 06, 2025 00:07:16
    =================================================================
    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. TABs (ASCII 09) are not allowed -- there's no knowing
    how long you've set your tab markings. 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.


    In case a) and b) above is not crystal clear, here's an excellent
    summary by Ward Dossche, a major article contributor:

    Piece of cake:

    1) Ascii text
    2) Line length of 70
    3) Put this at the very top:

    *The title of your text
    The title of your text
    Your Name - Your Nodenumber

    The title is there twice, the line with the * is how it will be
    visible in the table of content.


    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.

    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.


    -----------------------------------------------------------------
    Credits, Legal Infomation, Availability

    + -- -- -- -- -- -- -- -- FIDONEWS STAFF - -- -- -- -- -- -- -- +
    | |
    | Editor: Björn Felten, 2:2/2 |
    | |
    | The IPv6 list: Michiel van der Vlist, 2:280/5555 |
    | The S/W list: Andrew Leary, 1:320/219 |
    | |
    + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +

    + -- -- -- -- -- -- -- - 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 |
    | or FNEWTvii.ZIP |
    | articles, vol.no nn, issue ii INPUnnii.ZIP |
    | |
    | On the web: |
    | http://eljaco.se/FILES/fnews/ |
    | |
    | The FIDONEWS echo in your newsreader: |
    | news://eljaco.se/FIDONEWS |
    | |
    + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +

    -----------------------------------------------------------------


    ** Prepared for FIDONEWS by Azure/NewsPrep 3.0
    (c) Copyright 1996-1999 Peter Karlsson

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From deon@3:633/509 to Michiel van der Vlist on Monday, January 06, 2025 12:27:56
    Re: FidoNews 42:01 [02/08]: General Articles
    By: FidoNews Robot to All on Mon Jan 06 2025 12:07 am

    Howdy,

    Another problem with public NAT64 gateways is similar to the problem
    with the 6to4 tunnels that some of us are still using: services using geolocation to grant access may get confused because all traffic seems
    to come from the gateway, not from the originator. Not a problem for
    Fidonet I'd say, but for other use it may be.

    For those and some other reasons I would prefer a NAT64 gateway run
    by my provider if I ever start to use this permanently. I have two
    providers at the moment and neither of them provides such a service.
    I may make that a goal for the coming year. Or next year...

    Why not run a NAT64 gateway at home? Its pretty easy, mine runs on a raspberry pi, but it could easily be a virtual machine.


    ...δεσ∩
    --- SBBSecho 3.23-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)
  • From Michiel van der Vlist@2:280/5555 to Deon George on Monday, January 06, 2025 18:11:46
    Hello deon,

    On Monday January 06 2025 12:27, you wrote to me:

    For those and some other reasons I would prefer a NAT64 gateway run
    by my provider if I ever start to use this permanently. I have two
    providers at the moment and neither of them provides such a
    service. I may make that a goal for the coming year. Or next
    year...

    Why not run a NAT64 gateway at home?

    I did not think it was worth the effort for the test. For a more permanent configuration, when running the NAT64 at home, I'd still need an IPv4 connecvtion to the rest of the world. I was prepairing for a situation that my connection to the rest of the world is IPv6 only.

    Its pretty easy, mine runs on a raspberry pi, but it could easily be a virtual machine.

    So why not write a Fidonews article about it?


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:280/5555)
  • From Dennis Slagers@2:280/2060 to deon on Monday, January 06, 2025 22:13:16

    Hello deon!

    06 Jan 25 12:27, you wrote to Michiel van der Vlist:

    Why not run a NAT64 gateway at home? Its pretty easy, mine runs on a raspberry pi, but it could easily be a virtual machine.

    How and what service/tools do you use? I am intrigued about it.


    Dennis


    ... User input isn't a priority right now.
    --- GoldED+/LNX 1.1.5-b20240309
    * Origin: ---- BOFH: Problem solved, user deleted. (2:280/2060)
  • From deon@3:633/509 to Dennis Slagers on Tuesday, January 07, 2025 09:00:26
    Re: FidoNews 42:01 [02/08]: General Articles
    By: Dennis Slagers to deon on Mon Jan 06 2025 10:13 pm

    Howdy,

    How and what service/tools do you use? I am intrigued about it.

    To use NAT64, you also need (to be using) a DNS server that is capable of DNS64.

    The process is this:

    * You resolve a hostname that has an IP4 (only) address. (If the hostname also returns an AAAA record for IP6, then NAT64 wouldnt be need anyway.)

    A DNS server that is setup for DNS64, would return an AAAA record, instead of an A record for the IP4 address, like:

    eg: for tfb-bbs.org (180.150.99.174)
    # host tfb-bbs.org
    tfb-bbs.org has address 64:ff9b::b496:63ae

    (bind supports DNS64).

    * Your internal routing would then route 64:ff9b::/96 via a machine running jool (the nat64 part). In theory you could use any IP6 net, but I think most use 64:ff9b::/96.

    Jool then proxies the connection to the IP4 address (hence it needs to have a working internet IP4 stack) to the destination, and sends the replies to the originator over IP6.

    The jool machine doesnt need a public internet IP4 address, it can still be an internal private address (192.168...), and if that was the case, then your outgoing router would need to be doing SRC NAT to its public IP4 address. (Like it probably would be anyway.)

    In my case, I have an alpine virtual machine running on a PI4, with 512MB memory. Alpine provides the jool app and kernel module.

    nat64:/# apk list|grep jool
    jool-modules-lts-6.6.56-r0 aarch64 {jool-modules-lts} (GPL-2.0-or-later) [installed]
    jool-modules-rpi-6.6.49-r0 aarch64 {jool-modules-rpi} (GPL-2.0-or-later) jool-tools-4.1.11-r1 aarch64 {jool-tools} (GPL-2.0-only) [installed] jool-tools-bash-completion-4.1.11-r1 aarch64 {jool-tools} (GPL-2.0-only) jool-tools-doc-4.1.11-r1 aarch64 {jool-tools} (GPL-2.0-only) jool-tools-openrc-4.1.11-r1 aarch64 {jool-tools} (GPL-2.0-only) [installed]

    I ran it exclusively for a week on IP6, and it worked well. It doesnt help you if you have some devices inside your network (like I do) that dont have an IP6 stack. You'll need to have them use a DNS server that doesnt do the DNS64 bit (since they dont understand IP6), or configure your bind server to not do DNS64 replies to those devices, via ACLs.


    ...δεσ∩
    --- SBBSecho 3.23-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)
  • From Michiel van der Vlist@2:280/5555 to deon on Tuesday, January 07, 2025 16:17:25
    Hello deon,

    On Tuesday January 07 2025 09:00, you wrote to Dennis Slagers:

    eg: for tfb-bbs.org (180.150.99.174)
    # host tfb-bbs.org
    tfb-bbs.org has address 64:ff9b::b496:63ae

    (bind supports DNS64).

    * Your internal routing would then route 64:ff9b::/96 via a machine running jool (the nat64 part). In theory you could use any IP6 net,
    but I think most use 64:ff9b::/96.

    Only if you use a "local" NAT64 gateway. 64:ff9b::/96 is reserved as the "well known prefix" for NAT64 gateways. But it is not globally routable! So third parties like Kasper Dupont use a prefix in the normal routable ranges.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:280/5555)