[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Android (lack of) support for DHCPv6
- Subject: Android (lack of) support for DHCPv6
- From: lorenzo at colitti.com (Lorenzo Colitti)
- Date: Wed, 10 Jun 2015 19:49:24 +0900
- In-reply-to: <1433920393.11511.52.camel@karl>
- References: <[email protected]> <CAKGbBm=dCDpeFJe4f0_KM6pjdvpeHrL4t7fyczOj2D3y=_07pg@mail.gmail.com> <1433905187.11511.25.camel@karl> <[email protected]> <1433907422.11511.30.camel@karl> <CAKGbBmkE_AbZcmWhtWS68a=t9QmuccLdarhaN=m+9QEmJxOcJg@mail.gmail.com> <1433920393.11511.52.camel@karl>
On Wed, Jun 10, 2015 at 4:13 PM, Karl Auer <kauer at biplane.com.au> wrote:
> You need as many as you need. Request them. Worry about it if you don't
> get them. This is exactly what happens when N=1, BTW. A DHCPv6 server is
> almost certainly not going to have an upper limit that significantly
> crimps your style...
Ok, let's see how that goes, even among the few people on this thread.
Question for everyone on this thread that has said that DHCPv6 NA is a
requirement: suppose that Android supported stateful DHCPv6 addressing,
requested a number of addresses, and did not use any of them if the number
of addresses received was less than N.
What does N need to be?