On 2014-04-17 12:55, Per Jessen wrote:
Carlos E. R. wrote:
It may be used by anything on the client end that wants to talk an IPv6 host. A client application will not be aware it is using teredo, 6rd or some third mechanism.
Might be useful...
It is a tunnel, that pipes IPv6 inside, through NAT. As any such thing it needs collaboration from a known server on the outside to set it up, and this one belongs to Microsoft.
There are many such servers, not just one. There are also several Teredo relays.
Apparently, it does not affect anything else in the network. I did not find, yet, anything in Linux related to "teredo". I think that a Linux based firewall will not even be aware of it.
You could block outbound destination port 3544.
I just blocked on the router "LAN" firewall port 3544. There is no description, so I don't know in what direction it blocks. There another set of rules to block IPs, LAN or WAN, any direction you wish, tcp, udp, or all, within a time frame or not. However... you can not specify which ports! Ah, ok, found it. Just the Windows machine hast port 3544 blocked. Direction unclear. Thanks for the hint :-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)