[180833] in North American Network Operators' Group
Re: Android (lack of) support for DHCPv6
daemon@ATHENA.MIT.EDU (Michael Thomas)
Wed Jun 10 18:50:40 2015
X-Original-To: nanog@nanog.org
Date: Wed, 10 Jun 2015 15:50:33 -0700
From: Michael Thomas <mike@mtcc.com>
To: nanog@nanog.org
In-Reply-To: <D19E2EBA.5551F%wesley.george@twcable.com>
Errors-To: nanog-bounces@nanog.org
On 06/10/2015 03:32 PM, George, Wes wrote:
> From: Ted Hardie <ted.ietf@gmail.com<mailto:ted.ietf@gmail.com>>
> Date: Wednesday, June 10, 2015 at 6:09 PM
> To: "George, Wes" <wesley.george@twcable.com<mailto:wesley.george@twcab=
le.com>>
> Cc: Doug Barton <dougb@dougbarton.us<mailto:dougb@dougbarton.us>>, "nan=
og@nanog.org<mailto:nanog@nanog.org>" <nanog@nanog.org<mailto:nanog@nanog=
=2Eorg>>
> Subject: Re: Android (lack of) support for DHCPv6
>
>
> I saw your response, but creating a hypervisor-equivalent network stack=
inside Android didn't seem particularly easy to me. This may be, howeve=
r, because I've mostly dealt with OVS-style approaches in the past few ye=
ars and my calibration is off. If you have pointers to implementations th=
at are for mobile devices, I'd be happy to be educated.
>
> WG] I was merely observing that bridging so that multiple virtual inter=
faces/devices can share the same interface and get their own addresses is=
a solved problem generically. From what I can see with KVM, it involves =
creating a bridge interface or group, and bridging both the physical inte=
rface and any virtual interfaces into it, and then standing back. Doesn't=
seem obvious to me that it requires an entire hypervisor-equivalent netw=
ork stack to get this one fairly limited feature, and I'm not aware of an=
y mobile implementations, but it does seem to me that its presence in Lin=
ux makes it something we shouldn't dismiss out of hand when exploring sol=
utions to this problem given Android's Linux roots - At it's core, it's s=
till a general=E2=80=93purpose computer with a set of network interfaces.=
I'm not an expert on either Android's networking stack nor Linux's, nor =
hypervisors, but I have a hunch if this was allowed to move through the e=
xisting Android feature development process, we might find some folks tha=
t are and can tell us whether this is doable as an alternative to DHCP=E2=
=80=93PD or SLAAC on networks that generally adhere to the one address pe=
r device rule.
>
>
Besides, virtualizing the os environment on a phone would be a very=20
interesting thing in its own right. I thought that
was gaining momentum at one point as a way to deal with the friction=20
between corpro-IT demands of control, and
end user desire to keep nannyware crap off their phone -- just have two=20
vm's with each environment.
Mike
