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: 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, 2014 11:55 AM > To: Jeroen Massar; IPv6 Ops list > Subject: Re: Teredo sunset - did it happen? > > 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. > > > > Then don't make statements that you are blocking them... > > In the interests of the principle of charity - I am trying hard to assume > good motives on your part - let me try again... > > === > > We've historically blocked Teredo, for probably erroneous reasons. I'd > like to unblock it, to specifically let XBox One consoles use their new > Teredo stuff. > > At the same time, I'd like to avoid even the possibility of triggering a > behaviour change on Microsoft Windows clients. I had thought Teredo was > sunsetted, but examination of my Windows 7 PC suggests it is not, although > it is broken. > > To inform my decision about unblocking it, I'd like to ask a few questions. > > Does anyone know why Teredo has not been sunsetted yet? > > Does anyone know when Teredo will be sunsetted? > > Does anyone know of a safe way to block Teredo from Microsoft Windows > clients, but leave Teredo from XBox One unaffected? Jeroen, your suggestion > of blocking the DNS name is a good one. Anyone any other ideas I should > also consider. > > === > > Hopefully this is specific enough... >