[180706] in North American Network Operators' Group
Re: Android (lack of) support for DHCPv6
daemon@ATHENA.MIT.EDU (Joel Maslak)
Tue Jun 9 23:49:22 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <CADb+6TCR9ybuTiKg098dHt+Fm57M64jHSBG6xEcp05QMe7e1yw@mail.gmail.com>
Date: Tue, 9 Jun 2015 21:45:38 -0600
From: Joel Maslak <jmaslak@antelope.net>
To: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Of course I've been up too long, ignore the idiot (me). :)
On Tue, Jun 9, 2015 at 9:37 PM, Joel Maslak <jmaslak@antelope.net> wrote:
> Most APs don't support bridging, not enough addresses in the protocol
> (without enabling WDS or whatever modern versions of that are).
>
> On Tue, Jun 9, 2015 at 9:14 PM, Chris Adams <cma@cmadams.net> wrote:
>
>> Once upon a time, Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> said:
>> > On Wed, 10 Jun 2015 12:59:47 +1000, Karl Auer said:
>> > > Hope the question doesn't make me look like an idiot, but why does
>> using
>> > > stateful DHCPv6 mean having to go back to NAT?
>> >
>> > How does the device ask for a *second* DHCPv6'ed address for tethering
>> or
>> > whatever?
>>
>> It's called "bridging". Let whatever is being tethered ask directly for
>> its own address.
>> --
>> Chris Adams <cma@cmadams.net>
>>
>
>
