= Сообщение: 4151 из 7440 ============================================= IPV6 = От : Michiel van der Vlist 2:280/5555 12 Feb 17 23:55:43 Кому : Björn Felten 12 Feb 17 23:55:43 Тема : Making IPv6 prio number one FGHI : area://IPV6?msgid=2:280/5555+58a0ef2f На : area://IPV6?msgid=2:203/2+58a0677c = Кодировка сообщения определена как: CP850 ================================== ============================================================================== Hello Björn,
On Sunday February 12 2017 14:47, you wrote to me:
BF> Don't you think it's worth while to demonstrate that you can get BF> full IPv6 capability even with a 15yo XP setup?
BF> We all know how reluctant fido sysops are to totally abandon their BF> decades old setups (hard- as well as software) just to get IPv6 BF> capability -- now here's living proof that it can be done without BF> scrapping the working system. No?
Well.. yes and no... Yes, you do have a fully functional Fidonet IPv6 connectable node. It can accept incoming binkp connects over IPv6 and it can also make outgoing IPv6 connects. Yes, you earned your place in the list of Fidonet IPv6 capable nodes.
But... full IPv6 capability? Eh.. no I would not say so. The world of IPv6 is bigger than just connecting one Fidonet node via IPv6. Full IPv6 connectivity implies having IPv6 for your entire local network. Correct me if I am wrong, but I do not think you have that.
When I got my SixXs account, what was it, seven, eight? years ago, my plan was to use my Fido XP machine that is on 24/7 anyway as the tunnel endpoint and router for the IPv6 subnet that I could get from SixXs. Well, I got the tunnel part working quicky enough, but routing the subnet to my other devices on the LAN, that I never got to work. After some not so nice interchanges with the SixXs' Head Honcho, I learned that routing a tunneled IPv6 subnet just doesn't work with windows XP as a router.
So I abandonned that idea and went for installing a he.net tunnel on a Linksys WRT54GL flashed with OpenWrt. And with THAT ssetup, I managed to route a /64 subnet to my LAN. In the meantime, I have moved on. I now have native IPv6 from my ISP and a modem/router that routes a subnet to my LAN. I have not cancelled my tunnel aacounts, but the tunnels are sleeping.
Once again, correct me if I am wrong, but I think you are still stuck where I was seven years ago with a tunnel that could just provide IPv6 for ONE machine on my LAN.
