[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: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks at vt.edu)
- Date: Tue, 09 Jun 2015 23:40:50 -0400
- In-reply-to: Your message of "Tue, 09 Jun 2015 22:14:54 -0500." <[email protected]>
- References: <[email protected]> <CAKGbBm=dCDpeFJe4f0_KM6pjdvpeHrL4t7fyczOj2D3y=_07pg@mail.gmail.com> <1433905187.11511.25.camel@karl> <[email protected]> <[email protected]>
On Tue, 09 Jun 2015 22:14:54 -0500, Chris Adams said:
> Once upon a time, Valdis.Kletnieks at vt.edu <Valdis.Kletnieks at 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.
And the router knows to send to the "front" address to reach the "back" address,
how, exactly? Seems like somebody should invent a way to assign a prefix to
the front address that it can delegate to things behind it. :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20150609/25000baa/attachment.pgp>