Text 35596, 77 rader
Skriven 2009-09-04 00:08:16 av Grant Taylor (109048.fidonews)
  Kommentar till text 35595 av Michiel van der Vlist (109043.fidonews)
Ärende: FidoNews 26:32 [02/05]: Rebuttals To Previous Articles
==============================================================
  Re: FidoNews 26:32 [02/05]: Rebuttals To Previous Articles
  By: Grant Taylor to Michiel van der Vlist on Thu Sep 03 2009 11:28 pm

Dough!  Wrong key!  Send != Abort  *snarl*

 > Some points

 - Incoming and outgoing (internet) connections will have to be made via IPv6.
 - It does not matter if the IPv4 address is public or private because there is
no IPv4 path.  (This means that even so called public IPv4 addresses will not
make it to the internet.)  So we are free to use them for our own purposes.
 - There will have to be an IPv6 to IPv4 shim for each IPv6 address to proxy to
the IPv4 address.
 - There will have to be an IPv4 to IPv6 shim for each IPv4 address to proxy to
the IPv6 address.

(... This is rather difficult to get out coherently ... I have backed up and
re-written this multiple times. ...)

Here's how I would configure my Windows system to connect to some IPv4 systems
via IPv6.

 - I would install the Microsoft Loopback Adapter (MSLBA)
 - I would bind all ""remote IPv4 address(es) to the MSLBA with a netmask of
255.255.255.255 (/32).
 - I would set up a v6tov4 portproxy for my IPv6 address so others can get to
my IPv4 service.
 - I would set up a v4tov6 portproxy for each ""remote IPv4 address so I can
get to others IPv6 service.

This would allow BinkD (or what ever) to continue connecting to and receiving
connections from IPv4 address just like it is now.  The only difference is that
the address that it is connecting to would be on the local side of the internet
connection and ultimately proxied out an IPv6 connection.

Let's say that the following three SysOps have IPv4 only software and an IPv6
only internet connection:

SysOp1
IPv4:  111.111.111.111
IPv6:  aaaa:aaaa::a
   netsh interface portproxy v6tov4 listenaddress=aaaa:aaaa::a listenport=24554
connectaddress=111.111.111.111 connectport=24554
   netsh interface portproxy v4tov6 listenaddress=222.222.222.222
listenport=24554 connectaddress=bbbb:bbbb::b connectport=24554
   netsh interface portproxy v4tov6 listenaddress=333.333.333.333
listenport=24554 connectaddress=cccc:cccc::c connectport=24554

SysOp2
IPv4:  222.222.222.222
IPv6:  bbbb:bbbb::b
   netsh interface portproxy v6tov4 listenaddress=bbbb:bbbb::b listenport=24554
connectaddress=222.222.222.222 connectport=24554
   netsh interface portproxy v4tov6 listenaddress=111.111.111.111
listenport=24554 connectaddress=aaaa:aaaa::a connectport=24554
   netsh interface portproxy v4tov6 listenaddress=333.333.333.333
listenport=24554 connectaddress=cccc:cccc::c connectport=24554

SysOp3
IPv4:  333.333.333.333
IPv6:  cccc:cccc::c
   netsh interface portproxy v6tov4 listenaddress=cccc:cccc::c listenport=24554
connectaddress=333.333.333.333 connectport=24554
   netsh interface portproxy v4tov6 listenaddress=111.111.111.111
listenport=24554 connectaddress=aaaa:aaaa::a connectport=24554
   netsh interface portproxy v4tov6 listenaddress=222.222.222.222
listenport=24554 connectaddress=bbbb:bbbb::b connectport=24554

All of this only deals with my end of the connection.  The remote end of the
connection will either need to be native IPv6 or have similar IPv4 <-> IPv6
shims.



Grant. . . .
--- SBBSecho 2.12-Win32
 * Origin: Vertrauen - vert.synchro.net (1:103/705)