❦ 25 juillet 2016 06:06 CEST, Martin Kletzander <mkletzan@redhat.com> :>>╭─────┤ http://libvirt.org/formatnetwork.html#elementsConnect ├───── >>│Inclusion of the forward element indicates that the virtual network is >>│to be connected to the physical LAN.Since 0.3.0. The mode attribute >>│determines the method of forwarding. If there is no forward element, the >>│network will be isolated from any other network (unless a guest >>│connected to that network is acting as a router, of course). >>╰───── >> >>That's exactly what I want: just a vnet interface, no bridge, no >>routing, no forwarding. However, if I create a network with just that: >> > > "Just a vnet interface, no bridge" means you want no network. Where > should the vnet be connected?The host is able to handle the routing. It seems I could just declare an interface of type "ethernet" instead of "network" to get the effect I want. -- Write clearly - don't be too clever. - The Elements of Programming Style (Kernighan & Plauger)
On Mon, Jul 25, 2016 at 06:58:53AM +0200, Vincent Bernat wrote:> ❦ 25 juillet 2016 06:06 CEST, Martin Kletzander <mkletzan@redhat.com> : > >>>╭─────┤ http://libvirt.org/formatnetwork.html#elementsConnect ├───── >>>│Inclusion of the forward element indicates that the virtual network is >>>│to be connected to the physical LAN.Since 0.3.0. The mode attribute >>>│determines the method of forwarding. If there is no forward element, the >>>│network will be isolated from any other network (unless a guest >>>│connected to that network is acting as a router, of course). >>>╰───── >>> >>>That's exactly what I want: just a vnet interface, no bridge, no >>>routing, no forwarding. However, if I create a network with just that: >>> >> >> "Just a vnet interface, no bridge" means you want no network. Where >> should the vnet be connected? > >The host is able to handle the routing. It seems I could just declare an >interface of type "ethernet" instead of "network" to get the effect I >want.I'm sorry, but I have no idea what is the end result you are trying to achieve. Could you describe what are your trying to set up without libvirt technicalities?
❦ 25 juillet 2016 08:44 CEST, Martin Kletzander <mkletzan@redhat.com> :>>> "Just a vnet interface, no bridge" means you want no network. Where >>> should the vnet be connected? >> >>The host is able to handle the routing. It seems I could just declare an >>interface of type "ethernet" instead of "network" to get the effect I >>want. > > I'm sorry, but I have no idea what is the end result you are trying to > achieve. Could you describe what are your trying to set up without > libvirt technicalities?I have a process watching libvirt event to add a route like "ip route add 192.0.2.147/32 dev vnet18" once the VM is spawned. The host is then responsible for any routing to/from the VM. I don't want the VM to be part of a bridge. -- Indent to show the logical structure of a program. - The Elements of Programming Style (Kernighan & Plauger)