So comparing the ARP and ND tables on my Mikrotik home router, I see
that my Apple TV, indeed, does have an IPv6 address assigned to it
(SLAAC), even though the device, itself, does not display any IPv6
information in its network settings.
Then again, Apple never did think an "HDD is Active"
On 28/Nov/18 17:23, Nikolay Shopik wrote:
> tvOS will only show IPv6 dns servers in their "Network Settings" tab.
> They just forgot to update interface for some reason, like they did in
> back ios10 iirc to show all network configuration including IPv6.
I'm running tvOS 12.1 (16J602), and
On 28/11/18 5:25 pm, Mark Tinka wrote:
> Well, my Apple TV interface only has IPv4 bits to show.
>
> Are you saying IPv6 is hidden from the "Network Settings" tab? I haven't
> done an actual wire tap.
tvOS doesn't expose IPv6 addresses but it fully supported just like all
ios based systems since
On 11/28/18 8:25 AM, Mark Tinka wrote:
On 28/Nov/18 13:37, Nikolay Shopik wrote:
Sony Entertainment is know to be slowpoke in this area. PS4
firmware/kernel is SLAC enabled IPv6 but its not exposed to devs and
thus apps doesn't use it at all.
Which is what really surprised me with this
On 28/Nov/18 16:15, Radu-Adrian Feurdean wrote:
> Or there is some braindead wifi in-between that does not allow IPv6 to
> function (or makes it unreliable). Already seens a number of such devices
> from different vendors.
I have mine hooked into Cat-6 to my home switch (which has switching
On 28/Nov/18 15:41, valdis.kletni...@vt.edu wrote:
> Odd. Mine does DHCPv6. It might do SLAC as well, my OpenWRT wouldn't
> notice an unused SLAC address..
On what Sony device? I know they have different OS's for different TV
models, which could have an impact on this...
Mark.
On 28/Nov/18 13:37, Nikolay Shopik wrote:
> Sony Entertainment is know to be slowpoke in this area. PS4
> firmware/kernel is SLAC enabled IPv6 but its not exposed to devs and
> thus apps doesn't use it at all.
Which is what really surprised me with this 2014 TV I have, considering
it stopped
On Wed, Nov 28, 2018, at 12:37, Nikolay Shopik wrote:
> Are you sure about ATV4 netflix app? Support is there and I've seen
> traffic from it when recently did tcpdump from ATV4.
Or there is some braindead wifi in-between that does not allow IPv6 to function
(or makes it unreliable). Already
On Wed, 28 Nov 2018 14:37:06 +0300, Nikolay Shopik said:
> Sony Entertainment is know to be slowpoke in this area. PS4
> firmware/kernel is SLAC enabled IPv6 but its not exposed to devs and
> thus apps doesn't use it at all.
Odd. Mine does DHCPv6. It might do SLAC as well, my OpenWRT wouldn't
Sony Entertainment is know to be slowpoke in this area. PS4
firmware/kernel is SLAC enabled IPv6 but its not exposed to devs and
thus apps doesn't use it at all.
Are you sure about ATV4 netflix app? Support is there and I've seen
traffic from it when recently did tcpdump from ATV4.
On 28/11/18
On 26/Nov/18 06:47, Dave Temkin wrote:
>
> And yes, IPv6 is fully supported by every piece of our infrastructure;
> the issue is TVs and STBs that do not support v6 - but we have finally
> seen the largest device manufacturers commit to supporting it (if they
> don't already on their late
On Tue, Nov 27, 2018 at 3:48 AM Grant Taylor via NANOG
wrote:
> On 11/25/2018 09:47 PM, Dave Temkin wrote:
> > Putting an OCA with bypass through the CGN with RFC1918 space will
> > actually work just fine. We (Netflix) don't formally support it because
> > of the vast number of non-standard CGN
On 11/25/2018 09:47 PM, Dave Temkin wrote:
Putting an OCA with bypass through the CGN with RFC1918 space will
actually work just fine. We (Netflix) don't formally support it because
of the vast number of non-standard CGN implementations out there, but if
your clients are in RFC1918 space and
Not exactly. You don't need to advertise the RFC1918 to the OCA - just make
sure you advertise the CGN prefix to it, and make sure that the OCA's
default gateway knows how to reach the RFC1918 clients. So long as the
"outside" IP of your CGN is advertised to the OCA (the IP that clients who
would
Thanks Dave, so my local OCA will listen to my BGP advertisements for RFC1918
prefixes if I decided to advertise them?
Aaron
> On Nov 25, 2018, at 10:47 PM, Dave Temkin wrote:
>
> FWIW (reviving an old thread)-
>
> Putting an OCA with bypass through the CGN with RFC1918 space will actually
FWIW (reviving an old thread)-
Putting an OCA with bypass through the CGN with RFC1918 space will actually
work just fine. We (Netflix) don't formally support it because of the vast
number of non-standard CGN implementations out there, but if your clients
are in RFC1918 space and the next hop
On Tue, Sep 18, 2018 at 1:21 AM Radu-Adrian Feurdean <
na...@radu-adrian.feurdean.net> wrote:
> On Mon, Sep 17, 2018, at 17:48, Jared Mauch wrote:
>
> > I also strongly suggest you look at how to get native IPv6 from your
> > clients behind the CG-NAT rolled out. I know many folks have had
On Mon, Sep 17, 2018, at 17:48, Jared Mauch wrote:
> I also strongly suggest you look at how to get native IPv6 from your
> clients behind the CG-NAT rolled out. I know many folks have had issues
Getting IPv6 to your customers is good, but they still have to use it.
If I look at my stats, I
> On Sep 17, 2018, at 8:48 AM, Jared Mauch wrote:
>
>
>
>> On Sep 17, 2018, at 6:54 AM, Tom Ammon wrote:
>>
>> I'm looking to understand the impact of CG-NAT on a set of netflix OCAs, in
>> an ISP environment. I see in Netflix's FAQ on the subject that traffic
>> sourced from RFC
> On Sep 17, 2018, at 6:54 AM, Tom Ammon wrote:
>
> I'm looking to understand the impact of CG-NAT on a set of netflix OCAs, in
> an ISP environment. I see in Netflix's FAQ on the subject that traffic
> sourced from RFC 1918/6598 endpoints can't be delivered to the OCA. Is this
> simply a
20 matches
Mail list logo
