Comment 2 for bug 1472704
Revision history for this message
| Carl Baldwin (carl-baldwin) wrote Re: Support networks that work through routing instead of bridging | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
neiljerram, kevinbenton, and I discussed [1] how this relates to [2]. The way I see it, this rfe proposes L3 to the port. L2 is confined to the port and used only to bootstrap the VM on to the L3 network by providing responses to DHCP, arp, the like.
The tap interface is not bridged to a bridge. Therefore, dnsmasq must be configured to listen to tap interfaces directly.
Having read the devref [3], I think this proposal is somewhat consistent with [4] in that they will use provider types to mark a network.
[1] http://
[2] https:/
[3] https:/
[4] https:/