Mailing List Archive: Cisco: NSP

IPv6 basic configuration problem

Index | Next | Previous | View Threaded

jstuxuhu0816 at gmail

Apr 23, 2012, 11:03 PM

Post #1 of 8 (630 views)
Permalink

IPv6 basic configuration problem

Hi Team,
For the IPv6, i have two basic problems;
1. In the real network, usually which kind of ipv6 addressing will use? the
normal one or EUI-64 type?
2. For the link local address, usually which kind of type will use?
manually or dynamic?

Since i don't have the real practical experience about the ipv6, so very
appreciate for any suggestions.

Thanks and regards,
Hu Xu
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

gert at greenie

Apr 23, 2012, 11:36 PM

Post #2 of 8 (590 views)
Permalink

Re: IPv6 basic configuration problem [In reply to]

Hi,

On Tue, Apr 24, 2012 at 02:03:23PM +0800, Xu Hu wrote:
> 1. In the real network, usually which kind of ipv6 addressing will use? the
> normal one or EUI-64 type?

This is a religious issue, and you should be able to find 5000 different
opinions on the NANOG list.

We use static addresses for servers and routers, and EUI64 autoconfig
(SLAAC+stateless DHCPv6) for client PCs.

> 2. For the link local address, usually which kind of type will use?
> manually or dynamic?

We do not configure anything there, so "dynamic". Less configuration is
less work...

gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany gert [at] greenie
fax: +49-89-35655025 gert [at] net

jstuxuhu0816 at gmail

Apr 24, 2012, 12:32 AM

Post #3 of 8 (592 views)
Permalink

Re: IPv6 basic configuration problem [In reply to]

Many thanks for your reply, now i understand.
For the servers and routers, we can use the static address.
For the mobile clients or desktop clients, we can use the SLAAC to get the
IPv6 address from Router (EUI-64) and Stateless + DHCPv6 to get other DNS
or Domain information.

2012/4/24 Gert Doering <gert [at] greenie>

> Hi,
>
> On Tue, Apr 24, 2012 at 02:03:23PM +0800, Xu Hu wrote:
> > 1. In the real network, usually which kind of ipv6 addressing will use?
> the
> > normal one or EUI-64 type?
>
> This is a religious issue, and you should be able to find 5000 different
> opinions on the NANOG list.
>
> We use static addresses for servers and routers, and EUI64 autoconfig
> (SLAAC+stateless DHCPv6) for client PCs.
>
> > 2. For the link local address, usually which kind of type will use?
> > manually or dynamic?
>
> We do not configure anything there, so "dynamic". Less configuration is
> less work...
>
> gert
> --
> USENET is *not* the non-clickable part of WWW!
> //
> www.muc.de/~gert/
> Gert Doering - Munich, Germany
> gert [at] greenie
> fax: +49-89-35655025
> gert [at] net
>
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

jstuxuhu0816 at gmail

Apr 24, 2012, 12:56 AM

Post #4 of 8 (590 views)
Permalink

Re: IPv6 basic configuration problem [In reply to]

In your network, i have another question, when you use the SLAAC +
Stateless DHCPv6 for clients PCs, you will choose the EUI-64 type, actually
it also can choose the static addressed? Am i right?

I check the website bellow:
http://cciethebeginning.wordpress.com/2012/01/18/stateless-dhcpv6-slaac-24/

2012/4/24 Gert Doering <gert [at] greenie>

> Hi,
>
> On Tue, Apr 24, 2012 at 02:03:23PM +0800, Xu Hu wrote:
> > 1. In the real network, usually which kind of ipv6 addressing will use?
> the
> > normal one or EUI-64 type?
>
> This is a religious issue, and you should be able to find 5000 different
> opinions on the NANOG list.
>
> We use static addresses for servers and routers, and EUI64 autoconfig
> (SLAAC+stateless DHCPv6) for client PCs.
>
> > 2. For the link local address, usually which kind of type will use?
> > manually or dynamic?
>
> We do not configure anything there, so "dynamic". Less configuration is
> less work...
>
> gert
> --
> USENET is *not* the non-clickable part of WWW!
> //
> www.muc.de/~gert/
> Gert Doering - Munich, Germany
> gert [at] greenie
> fax: +49-89-35655025
> gert [at] net
>
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

gert at greenie

Apr 24, 2012, 1:06 AM

Post #5 of 8 (584 views)
Permalink

Re: IPv6 basic configuration problem [In reply to]

Hi,

On Tue, Apr 24, 2012 at 03:56:47PM +0800, Xu Hu wrote:
> In your network, i have another question, when you use the SLAAC +
> Stateless DHCPv6 for clients PCs, you will choose the EUI-64 type, actually
> it also can choose the static addressed? Am i right?

If you configure the PC's IPv6 address by hand, of course it will work.

(Now how exactly is this relevant to *cisco*-nsp?)

gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany gert [at] greenie
fax: +49-89-35655025 gert [at] net

aaron1 at gvtc

Apr 24, 2012, 6:01 AM

Post #6 of 8 (576 views)
Permalink

Re: IPv6 basic configuration problem [In reply to]

Regarding an ISP like I work for that provides internet for cable modem
customers, dsl, ftth and dial-up, Does anyone out there use stateless auto
configuration for these type of customers ?

Next question....
Is there anything you all are aware of that would steer my away from SLAAC
for these type of customers ? ...wondering if I lose the ability to provide
identification of mac/ipv6 address for subpoena's and also for
infections/hack attempts coming from my customers that other security folks
in the internet query me about. Would I still be able to identify my
customers and also be able to know their identity after 3 months has gone
by....in other words, a subpoena comes in and Homeland security (ICE I
believe they are called) or some FBI agent wants to know "who had a certain
IP address 3 months ago"....will SLAAC in IPv6 have a historical log for me
to look at ?

Aaron

-----Original Message-----
From: cisco-nsp-bounces [at] puck
[mailto:cisco-nsp-bounces [at] puck] On Behalf Of Xu Hu
Sent: Tuesday, April 24, 2012 1:03 AM
To: cisco-nsp [at] puck
Subject: [c-nsp] IPv6 basic configuration problem

Hi Team,
For the IPv6, i have two basic problems; 1. In the real network, usually
which kind of ipv6 addressing will use? the normal one or EUI-64 type?
2. For the link local address, usually which kind of type will use?
manually or dynamic?

Since i don't have the real practical experience about the ipv6, so very
appreciate for any suggestions.

Thanks and regards,
Hu Xu
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

dwcarder at wisc

Apr 24, 2012, 7:02 AM

Post #7 of 8 (576 views)
Permalink

Re: IPv6 basic configuration problem [In reply to]

Thus spake Xu Hu (jstuxuhu0816 [at] gmail) on Tue, Apr 24, 2012 at 03:56:47PM +0800:
> In your network, i have another question, when you use the SLAAC +
> Stateless DHCPv6 for clients PCs, you will choose the EUI-64 type, actually
> it also can choose the static addressed? Am i right?
>
> I check the website bellow:
> http://cciethebeginning.wordpress.com/2012/01/18/stateless-dhcpv6-slaac-24/

When most devices do SLAAC now, they will not be doing EUI-64 any more.
Instead most clients will be using privacy extensions (rfc 4941) by
default.

Dale
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

mack.mcbride at viawest

Apr 24, 2012, 10:23 AM

Post #8 of 8 (576 views)
Permalink

Re: IPv6 basic configuration problem [In reply to]

If you assign a unique /64 per customer (pick your method of distributing) then yes, you should be able to link an IPv6 address to a customer.
Each customer should be getting at least a /64 with a /48 recommended.
The caveat is of course many home routers and interface devices only support a /64.
You should not be using SLAAC to assign individual IPs to customers cable modem/dsl/ftth etc.
You can use SLAAC to assign an IP to the cable modem or other interface device but then you need to route a /64 to that address.
The DSL product we offer uses statically assigned addresses for both v4 and v6 but we have a very small customer base.

Mack McBride
Network Architect

-----Original Message-----
From: cisco-nsp-bounces [at] puck [mailto:cisco-nsp-bounces [at] puck] On Behalf Of Aaron
Sent: Tuesday, April 24, 2012 7:01 AM
To: cisco-nsp [at] puck
Subject: Re: [c-nsp] IPv6 basic configuration problem

Regarding an ISP like I work for that provides internet for cable modem customers, dsl, ftth and dial-up, Does anyone out there use stateless auto configuration for these type of customers ?

Next question....
Is there anything you all are aware of that would steer my away from SLAAC for these type of customers ? ...wondering if I lose the ability to provide identification of mac/ipv6 address for subpoena's and also for infections/hack attempts coming from my customers that other security folks in the internet query me about. Would I still be able to identify my customers and also be able to know their identity after 3 months has gone by....in other words, a subpoena comes in and Homeland security (ICE I believe they are called) or some FBI agent wants to know "who had a certain IP address 3 months ago"....will SLAAC in IPv6 have a historical log for me to look at ?

Aaron

-----Original Message-----
From: cisco-nsp-bounces [at] puck
[mailto:cisco-nsp-bounces [at] puck] On Behalf Of Xu Hu
Sent: Tuesday, April 24, 2012 1:03 AM
To: cisco-nsp [at] puck
Subject: [c-nsp] IPv6 basic configuration problem

Hi Team,
For the IPv6, i have two basic problems; 1. In the real network, usually which kind of ipv6 addressing will use? the normal one or EUI-64 type?
2. For the link local address, usually which kind of type will use?
manually or dynamic?

Since i don't have the real practical experience about the ipv6, so very appreciate for any suggestions.

Thanks and regards,
Hu Xu
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads