On Wed, Jun 10, 2015 at 2:56 PM, George, Wes <wesley.george@twcable.com> wrote:
On 6/10/15, 5:27 PM, "Ted Hardie" <ted.ietf@gmail.com> wrote:
... and this argument has been refuted by the word "bridging."
To repeat Valdis' question:
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. :)
WG] I made reference to it in a previous message, but since the question was repeated, I'll assume that was missed and repeat the answer. The hypervisor folks seem to have figured this out so that it "just works" without NAT, using virtual interfaces that have their own unique MAC addresses so that they look like unique hosts to the network/DHCP server. I'm using it on my FreeNAS (BSD) box at home with jails, and KVM supports it, so chances are it wouldn't even be that hard to incorporate into Android.
Thanks Wes
Hi Wes,
I saw your response, but creating a hypervisor-equivalent network stack inside Android didn't seem particularly easy to me. This may be, however, because I've mostly dealt with OVS-style approaches in the past few years and my calibration is off. If you have pointers to implementations that are for mobile devices, I'd be happy to be educated. regards, Ted
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.