Subj : Problems here after changing to he.net?
To   : Bj”rn Felten
From : Michiel van der Vlist
Date : Tue Dec 13 2016 16:37:10

Hello Bj”rn,

On Tuesday December 13 2016 04:55, you wrote to me:

Still no IPv6 coming from you:

- 13 Dec 16:12:59 [3744] incoming from 90.231.158.147 (4572)
+ 13 Dec 16:12:59 [4028] incoming session with 90.231.158.147
- 13 Dec 16:12:59 [4028] SYS Felten's Sharp System
- 13 Dec 16:12:59 [4028] ZYZ Bj”rn Felten
- 13 Dec 16:12:59 [4028] LOC S„ve, Sweden

 MvdV>> It is not a basic flaw at he.net. I ran a he.net tunnel for
 MvdV>> five years and had no problems with outgoing IPv6. It must be
 MvdV>> something in your configuration.

 BF>    Well, if it worked initially, I don't see how my configuration
 BF> suddenly can make it not work any more. Especially since it still
 BF> works on incoming calls.

Murphy's law, art 13.5: "Nothing was changed", changes to "something was changed, but that should not affect it" and then to "Hmmm, it seems something was changed after all"...

I can't explain it either, but I can see that it is not working as planned...

 MvdV>> How about web browsing? Do you see the turtle dancing at
 MvdV>> http://www.kame.net/ ?

 BF>    It's not that easy. As I may have said, I'm running an XP Mini on
 BF> my inbound router/fidonet computer. I don't have any browser installed
 BF> on it.

 BF>    But I'll see what netsh may have changed without me knowing about
 BF> it -- it's not like it would be the first time netsh is playing games
 BF> with me... :(

Well, Nick Bo‰l advised you to upgrade your Windows version. He may have a point, Win XP's IPv6 implementation is incomplete. It doesn't matter for Auntie Abbie who just does a bit of browsing and e-mail, but when you start doing more advanced things, you may run into some problems.

I'll go a bit furth, my advice is: stop trying to use Windows as a router. It was never designed for that and everyone who has ever tried it, reports problems. If you /must/ use a standard desk top as a router, go Linux. But I go one step furhter and say: use something that has hardware designed and optimised for being a router. And just that. OpenWrt has facilities for hosting he.net type tunnels and that will give you a much more stable situation. Plus that all the devices in your LAN that are IPv6 capable will automatically be assigned an IPv6 address from the /64 or /48 subnet you get from he.net. It really is much easier than fighting Windows.

My WRT54GL running OpenWrt has been oprating that way for five years on an "install and forget" basis. I sidetracked it because I got naitive IPv6 and that worked only with the modem/router from the ISP.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
 * Origin: he.net certified sage (2:280/5555)

.