On Tue, Jun 14, 2016 at 10:58:04AM +0200, DICK, L. (MR.) wrote:
> Please assist me. Thank you
Hi,
Please assist the group to be able to assist you: As requested earlier -
share more details of your overall set up. Your physical and layer2
configuration.
- Daniel
> On 20 Jun 2016, at 10:32 PM, Carlos M. Martinez wrote:
>
> As a data point, in our network we:
>
> - do run both SLAAC and DHCPv6
> - we send RDNSS info over SLAAC
> - we do provide both IPv4 and IPv6 DNSes via DHCP (v4 and v6 respectively)
>
> Now it’s less so as
> On 21 Jun 2016, at 2:33 PM, Mukom Akong T. wrote:
> But I think we can all agree that it's better for everyone if all client OSs
> can support all options. Right now, we have allies within one of these guys
> who need our help to ensure we can have those options ...
> On 20 Jun 2016, at 9:59 PM, Mukom Akong T. wrote:
>
> Most of the complaints about deploying IPv6 to users have been around needing
> to do both SLAAC and DHCPv6 in a normal network. Reasons being
>
> - Microsoft has refused to implement RFC 6106 (the ability to
> On Jan 22, 2016, at 4:04 PM, SM wrote:
>
> I read the blog article about spam. There are some mistakes in the article.
> I suggest getting an unbiased review.
Hello SM,
I’m not sure how that relates to the IPv6 specific mailing list, nor to this
thread…
I suggest
> On Jan 23, 2016, at 12:50 AM, Noah wrote:
>
> There you go.what you do with IPv4 ...do the same with IPv6. Even in the
> biggest ISP enviroment, same fundamentals are applied
>
> Only change is the vendor specific config sythax….
That’s pretty much it. Yes. :-)
Interesting slides. May be of interest to some.
https://datatracker.ietf.org/meeting/99/materials/slides-99-maprg-rate-limiting-of-ipv6-traceroutes-is-widespread-measurements-and-mitigations
___
AfrIPv6-Discuss mailing list
AfrIPv6-Discuss@afrinic.net
On 16/08/2017, 16:30, Lee Howardtyped:
>
> Yes, this is very interesting.
I'm glad everyone that's commented to far also found it interesting. I
certainly did!
It's not my work though, and I wished I'd caught the presentation at IETF 99. I
picked up the link to day in a Slack group.
Another interesting update from a big hyper-scale provider we all know:
https://cloudplatform.googleblog.com/2017/09/announcing-ipv6-global-load-balancing-ga.html
"Until today, global load balancing was available only for IPv4 clients. With
this launch, your IPv6 clients can connect to an IPv6
I didn't see this one on this list yet, although many of you may have already
read it. For the record:
https://blog.apnic.net/2017/01/19/ipv6-only-at-microsoft/
"IPv6-only at Microsoft
By Marcus Keane on 19 Jan 2017
Microsoft has been running IPv6 in some fashion on its corporate network for
On 11/06/2018, 18:31, Fernando Gont typed:
>
> Folks,
>
> APNIC folks asked me to summarize some of my recent presentations on
> "IPv6 network reconnaissance".
Thanks for sharing!
- Daniel
___
AfrIPv6-Discuss mailing list
Some may find this interesting...
> Begin forwarded message:
>
> From: "Templin, Fred L"
> Subject: [GROW] A Simple BGP-based Mobile Routing System for the Aeronautical
> Telecommunications Network
> Date: 9 March 2018 at 00:14:12 GMT+4
> To: "g...@ietf.org"
On Mon, 4 Nov 2019 at 06:33, Alejandro Acosta
wrote:
> The take away of Jordi's message and our message in general is that you
> need to take a different approach, you can not just scan the full IPv6
> address space; you mentioned nmap however AFAIK nmap does not allow IPv6 host
> scanning.
13 matches
Mail list logo