All,
ISTR that Teredo was going to be sunset, Microsoft having tested
removing the DNS name teredo.ipv6.microsoft.com.
(Ignoring the Xbox One stuff here - just the windows desktop
server/relay stuff)
However, my Windows 7 machine is still resolving that name and forming a
Teredo address,
On 2014-11-17 17:38, Phil Mayers wrote:
On 17/11/2014 16:23, Jeroen Massar wrote:
What are you trying to achieve by blocking that port?
I honestly don't know why you want to talk about other things, but I've
no interest in discussing them with you.
Then don't make statements that you are
On 17/11/2014 16:40, Jeroen Massar wrote:
On 2014-11-17 17:38, Phil Mayers wrote:
On 17/11/2014 16:23, Jeroen Massar wrote:
What are you trying to achieve by blocking that port?
I honestly don't know why you want to talk about other things, but I've
no interest in discussing them with you.
Why not just disable teredo at the command line?
netsh int ipv6 set teredo disabled
-Original Message-
From: ipv6-ops-bounces+cholzhauer=sscorp@lists.cluenet.de
[mailto:ipv6-ops-bounces+cholzhauer=sscorp@lists.cluenet.de] On Behalf Of
Phil Mayers
Sent: Monday, November 17,
Presumably because the clients are unmanaged?
On Mon, Nov 17, 2014, 09:02 Carl Holzhauer cholzha...@sscorp.com wrote:
Why not just disable teredo at the command line?
netsh int ipv6 set teredo disabled
-Original Message-
From:
On 11/17/2014 7:06 AM, Phil Mayers wrote:
All,
ISTR that Teredo was going to be sunset, Microsoft having tested
removing the DNS name teredo.ipv6.microsoft.com.
(Ignoring the Xbox One stuff here - just the windows desktop
server/relay stuff)
However, my Windows 7 machine is still resolving
On 17/11/2014 17:43, Darren Pilgrim wrote:
Any ideas what's going on? Microsoft, anyone care to comment?
Microsoft released an Windows Update for the prefix policy table. The
update dropped Teredo's precedence to lower than IPv4.
Just to be clear - are you suggesting they did this instead
I said:
But if the client has the old RFC 3483 policy table,
:::0:0/96 has the lowest precedence so Teredo would win over
IPv4, which is a Bad Thing. There isn't much to be done about
that unless the user has netsh skills.
s/3483/3484/
Brian
On 18/11/2014 13:01, Brian E Carpenter
We (Microsoft) has a standing plan to deactivate our public Teredo servers,
which would essentially deactivate the default Teredo functionality in the
Windows user base. We had thought to do that next year, but delayed for various
reasons - one being that the pain/noise around it's default
