Text 24110, 139 rader
Skriven 2015-04-27 04:06:03 av FidoNews Robot (2:2/2.0)
Ärende: FidoNews 32:17 [02/07]: General Articles
================================================
=================================================================
                        GENERAL ARTICLES
=================================================================

                IPv6 Penetration in Fidonet
                By Michiel van der Vlist 2:280/5555
                IPv6 enthousiast

1 November 2011 is the day that the first documented binkp connect
was made between two Fidonet nodes over IPv6. The connect was between
the systems of Andre Grueneberg of 2:2411/525 and that of Benny
Pedersen of 2:230/0. That was three and a half years ago. Since then
IPv6 has slowly but irreversibly penetrated into Fidonet.

Let us look at the last three entries of the list of IPv6 capable
nodes that is published weekly in Fidonews.

 27  4:903/26      Fernando Toledo        T-??    SixXs
 28  2:463/877     Alex Shuman            Native  Nline     IO
 29  2:5080/102    Stas Degteff           T-6to4

Number 27 on the list is Fernando Toledo. He was added last week and
that was another mile stone. Now all four remaining Fidonet zones
have IPv6 connectivity. Welcome to the Fidonet IPv6 club Fernando.

Number 28, the one from Alex Shuman is an interesting one. Alex uses
an IPv6 to IPv4 proxy to make his Radius answer to IPv6. In itself
this is not unique, others have used proxies as well, but what is
remarkable is that Alex found a way to let Windows 7 do the trick
all on its own. No external proxy needed. This is the trick:


netsh int portproxy add v6tov4 listenport=24554
connectaddress=10.10.5.2 connectport=24554 listenaddress=*


Note: The above is one line. As it is too long for Fidonews, it is
broken into two lines, but enter it in netsh as one line.

10.10.5.2 is the local address of the machine running the mailer.
One would think that "localhost" or 127.0.0.1 should do it as well,
but it does not. Welcome to the wonderfull world of netsh.

The same trick of course works for a Telnet the BBS if you have one:

netsh int portproxy add v6tov4 listenport=23
connectaddress=10.10.5.2 connectport=23 listenaddress=*


This is for incoming. Outgoing is a bit more complicated and less
practical. One needs to explicitly define every node one wants to
call over IPv6:

First one has to enter a port number in the local nodelist for the
node one wants to call, a different port number for each node,
- 24555 in this case - and then tell netsh what host name to use for
that port:


netsh int portproxy add v4tov6 listenport=24555
connectaddress="fido.vlist.eu" connectport=24554
listenaddress=127.0.0.1

Again the above is one line, broken into three for Fidonews.

Thanks Alex for figuring this out.

And it does not only work on Win7, it works an good old XP as well.

netsh int portproxy add v6tov4 listenport=80
connectaddress=192.168.1.3 connectport=80 listenaddress=*

Note that one must explicitly open port 80 on the firewall to make
this work.

You are welcome to IPv6 connect to my binkp mailer at fido.vlist.eu
and to my web site at www.vlist.eu.


© Michiel van der Vlist, all rights reserved.
Permission to publish in the FIDONEWS file scho and the FIDONEWS
discussion echo as originating from 2:2/2


-----------------------------------------------------------------
Dead wood and what to do with...
Ward Dossche - 2:292/854

Fidonet is shrinking, we all know that and there is a gazillion number
of reasons that can be identified for that.

It's a sad reality.

What's even more sad, is that several people have not even the
courtesy anymore to say they are leaving, they do not even close the
door with a loud bang -- they just unplug and that's it.

The result is "dead wood".

In Zone-2 dead wood has been in the process of being removed for a
long time. However, sometimes it isn't that easy.

For example, take the case of Region40 Israel. RC40 still polls here
like a clockwork once a week and picks-up whatever's there to be
picked up ... echo-traffic, netmails, nodediff, nodelist, Fidonews,
... This has been going on for years now with nothing coming back this
way.

Once in a while even a new, or maybe the same, segment gets delivered
(4 times in 2014, last in October) ... but all attempts at reaching
someone are fruitless.

For a while we had a live-person in the area who checked out all
entries and could not get a connect. PSTN or IP. Even today (Apr.20
2015) it was discovered that none of the IP-nodes are alive, I cannot
send anything direct to the RC because the listed system is not
responding. Of course, Janis will be able to connect, at least she
will claim she does.

The plan is to lift R40 Israel eventually from the nodelist because as
far as I can see there is no activity anymore. But before that
happens, I am addressing the sysop- community, and especially the
Russian-speaking community of R45, R46 and R50 if it has any knowledge
about active nodes in Israel because all of those sysop-names sound
"very Russian".

So if there's anyone who can assist in this matter, please get back to
me with relevant and pertinent information.

Thanks a million,

Ward Dossche
ZC2


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

--- Azure/NewsPrep 3.0
 * Origin: Home of the Fidonews (2:2/2.0)