Kitz Forum

Computers & Hardware => Networking => Topic started by: broadstairs on March 11, 2014, 09:04:22 AM

Title: Terado tunneling activated
Post by: broadstairs on March 11, 2014, 09:04:22 AM

I suddenly discovered yesterday that my W7 guest on Virtualbox had set up port forwarding for Terado tunnelling on my router when it booted. I assume because UPNP was enabled. On doing some research I discovered that both W7 and W8 will set up this facility by default. This tunnelling is to allow access to IPV6 networks over IPV4 and uses intermediate 'relay' servers on the net to convert the request to IPV6 and pass it on, picks up the message back and converts back to IPV4 and then back to the requester. More is available on Wikipedia (http://en.wikipedia.org/wiki/Teredo_tunneling).

Apparently there is a possibility that this could be abused and so I turned it off in W7 by issuing this command as Administrator.

Code: [Select]

netsh interface teredo set state disabled

I also turned off UPNP in the hope that any other W7 or W8 PCs which may be used on my Lan cannot set this up.

Stuart

Title: Re: Terado tunneling activated
Post by: burakkucat on March 11, 2014, 04:29:37 PM

Thank you for highlighting the protocol Stuart.

After doing some background reading I was not filled with a warm and fuzzy feeling.  :no:  Probably because I learnt that Terado tunnelling had been developed by Micro$oft.  :-X

Title: Re: Terado tunneling activated
Post by: sheddyian on March 11, 2014, 04:53:14 PM

By a strange coincidence, I found this yesterday as well  :D

I'd reflashed my HG612 with the Asbo formware, as I'd noticed that upnp wasn't working on the later Wolfy firmware for this device, even when "enabled" via the interface.

Once up and running, upnp was working, Windows saw a new device on the network, starting a program that wanted ports open would automatically open ports (I know, I know...  :-X ).

Later on I booted a different Windows 7 PC and was surprised to find a "Teredo Tunneling" port open to that machines internal ip address!

I too found it was  Microsoft TCP/IP V4 > V6 thing, but hadn't yet done anything about it, so thanks for the info on how to disable it!

Ian

ps at least having upnp enabled and working properly, you can see which ports are being opened "behind your back" by which computers on your network :)