I have a /32 assigned from ARIN (2001:4918::/32)
I’m looking for some direction/reading list of how to properly
configure IPv6. I’ve read to use a /64 for PtP interfaces and I’ve
read use a /128 instead.Assign all loopbacks from the same /64,
use a different /64 for each loopback. Ect, ect
Why do not you feel compelled to ask this question?
Did you ask this question when you deployed ipv4?
AFAIK, everyone deploys ipv4 in a unique way. Same for ipv6. IPv6 is not
exotic or filled with unique pitfalls. A lot of networks have deployed
production networks with ipv6, each one unique, s
On Mon, Jan 16, 2017 at 10:11 AM, Matthew Crocker
wrote:
> I’m looking for some direction/reading list of how to properly configure
> IPv6. I’ve read to use a /64 for PtP interfaces and I’ve read use a /128
> instead.Assign all loopbacks from the same /64, use a different /64 for
> each lo
Hi,
> Suggest /128's for loopbacks and /124's for point to points, all from
> the same /64. This way you don't burn space needlessly, don't open
> yourself to neighbor discovery issues on point to points
I usually reserve one /64 for loopbacks, reserve a /64 per point-to-point
connection and con
Hi, a few years back some in the community got together to write this:
On Mon, Jan 16, 2017 at 10:11 AM, Matthew Crocker
wrote:
>
> Hello,
>
> I’m AS7849 and I have an IP problem.
>
> I’m running IPv4 ( /16 legacy + /20) and have enough space to last me for
> a while, multi-homed, BGP4 full tab
Oops:
http://nabcop.org/index.php/IPv6_Subnetting
On Tue, Jan 17, 2017 at 12:48 PM, Michael Still
wrote:
> Hi, a few years back some in the community got together to write this:
>
> On Mon, Jan 16, 2017 at 10:11 AM, Matthew Crocker <
> matt...@corp.crocker.com> wrote:
>
>>
>> Hello,
>>
>> I’m A
On Tue, Jan 17, 2017 at 12:48 PM, Michael Still wrote:
> http://nabcop.org/index.php/IPv6_Subnetting
That's overall good advice. I quibble with a couple of points:
1. If you plan to use a /126 on a point to point and can't imagine how
you would use a /64 on that point to point, don't allocate a
ent: Tuesday, January 17, 2017 4:02 PM
> To: Michael Still
> Cc: nanog@nanog.org
> Subject: Re: Questions on IPv6 deployment
>
> On Tue, Jan 17, 2017 at 12:48 PM, Michael Still
> wrote:
> > http://nabcop.org/index.php/IPv6_Subnetting
>
> That's overall good advice
| Phone: 914-460-4039
> aim: matthewbhuff| Fax: 914-694-5669
>
>
>> -Original Message-
>> From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of William
>> Herrin
>> Sent: Tuesday, January 17, 2017 4:02 PM
>> To: Michael Still
>>
On Tue, Jan 17, 2017 at 4:07 PM, Matthew Huff wrote:
> The reason for allocating a /64 for a point to point link is due to various
> denial of service attack vectors.
Hi Matthew,
I'm always interested in learning something new. Please explain the
DOS vectors you're referring to and how they're
On 1/17/17 1:55 PM, William Herrin wrote:
> On Tue, Jan 17, 2017 at 4:07 PM, Matthew Huff wrote:
>> The reason for allocating a /64 for a point to point link is due to various
>> denial of service attack vectors.
if you mean allocating a /127, then... sure.
Neighbor discovery on point to point
7 4:56 PM
> To: Matthew Huff
> Cc: Michael Still ; nanog@nanog.org
> Subject: Re: Questions on IPv6 deployment
>
> On Tue, Jan 17, 2017 at 4:07 PM, Matthew Huff wrote:
> > The reason for allocating a /64 for a point to point link is due to
> various denial of service attack v
Hi Bill,
> Op 17 jan. 2017, om 22:55 heeft William Herrin het volgende
> geschreven:
>
> I'm always interested in learning something new. Please explain the
> DOS vectors you're referring to and how they're mitigated by
> allocating a /64 to the point to point link.
One thing that comes to min
On Tue, Jan 17, 2017 at 6:06 PM, Sander Steffann wrote:
> One thing that comes to mind is that it seems that some routers only have
> limited space in their routing tables for prefixes longer than a /64. If you
> would configure a /127 on the link but push the /64 to the routing table then
> yo
On Tue, Jan 17, 2017 at 5:13 PM, Matthew Huff wrote:
> Please check the nanog archives.
> I was just responding to the argument that a /64 is wasteful and serves
> little purpose.
Then respond. With explanation, reasoning and evidence. Telling me to
search a massive archive for nebulous discussi
15 matches
Mail list logo
