= Сообщение: 4154 из 7440 ============================================= IPV6 = От : Michiel van der Vlist 2:280/5555 13 Feb 17 16:12:00 Кому : Björn Felten 13 Feb 17 16:12:00 Тема : Making IPv6 prio number one FGHI : area://IPV6?msgid=2:280/5555+58a1cd51 На : area://IPV6?msgid=2:203/2+58a07442 = Кодировка сообщения определена как: CP850 ================================== ============================================================================== Hello Björn,
On Sunday February 12 2017 15:42, you wrote to me:
BF> Thanks!
You'r welcome. ;-)
BF> Now, considering that a vast amount of FTN systems still probably BF> runs on an XP setup(?), can we perhaps help those willing to try a BF> tunnel through all the hoops they'll encounter?
"Vast amount"? Now that we have come down from 30000+ nodes and half a million points to an estimated 1000+ nodes and maybe even less points?
OK, that still leaves an estimated couple of hundred XP systems running FTN software. Only those running IPv6 capable mailers will be interested. And of those some already have IPv6. And then there are the IPv6 denyers. They believe it is all just a scheme from the providers to let us pay more for our internet connection and if we just refuse to go along, it will blow over...
But... I think the killer filter is that very few that run an XP system have it directly connected to the InterNet. The normal setup is to have it behind a router. You may be the only Fidonet sysop haveing an XP system directly connected to the internet, using it as a router and host your tunnel end point.
BF> I know that you are probably one of the most knowledgeable netsh BF> experts amongst us;
Me? That's too much honour.
BF> what if we analyse all the netsh commands needed BF> to get an XP system from scratch and create a generic one that lacks BF> the mistakes SixXS as well as he.net has made?
What mistakes? I did not have much trouble installing my SixXs tunnel on my XP system. In fact, I seem to have taken the same steps as you. Look here:
D:\FIDO\R28>netsh int ipv6 show routes Der aktive Status wird abgefragt...
Veröff. Typ Met Präfix Idx Gateway/Schnittstelle ------- -------- ---- ------------------------ --- --------------------- no Autokonf 256 2001:1c02:1100:fd00::/56 4 fe80::7277:81ff:fe72:a4bb no Autokonf 8 2001:1c02:1100:fd00::/64 4 LAN-Verbindung no Autokonf 256 ::/0 4 fe80::7277:81ff:fe72:a4bb no Manuell 0 2001:7b8:2ff:3a9::/64 5 aiccu yes Manuell 0 ::/0 5 2001:7b8:2ff:3a9::1
The last two are relics from my SixXs (AYIYA) tunnel.
What I could never get to work was routing a sunbnet that way. Tha was the main reason I abondonned that plan and installed a he.net tunnel on WRT54GL running OpenWrt. The instructions on the he.net website were quite clear. But OpenWrt is Linux, not XP..
BF> As a basis I would use this:
BF> netsh int ipv6 install
BF> That's obvious.
Obvious.
BF> netsh int ipv6 6to4 set state disabled BF> netsh int ipv6 set teredo disable BF> netsh int ipv6 isatap set state state=disabled
BF> I would really want a total delete function here, if nothing else BF> but to clean up the ipconfig /all response.
I would like that too, at least I would like to make those three totally invisible. But I have not yet found a way to do that. I am not the netsh guru you seem to think I am...
BF> netsh int ipv6 add address "he.net" 2001:470:27:302::2 BF> netsh int ipv6 add route 2001:470:27:302::2/64 he.net BF> netsh int ipv6 add route 0::/0 he.net 2001:470:27:302::1 publish=yes
Probably what I did to install my SixXs tunnel. Almost a decade ago...
BF> And here is probably where we need to put a lot of comments. For BF> starters, there's no IPv4 addresses here, so I guess it's working for BF> me because I added it somewhere else along the line.
Must be... I don't recall how I did it. Too long ago...
