Hello Robert,

I personally use Open VSwitch for such pruposes, it requires a bit more work but is much more flexible in the end.  Would that sound like an acceptable solution?

Best regards,

Eric VISEUR | System Engineer | THALES Belgium S.A.

Rue des Frères Taymans, 28 |B-1480 TUBIZE - BELGIUM

Phone : +32 2 391 23 74 | Cell : +32 497 92 36 80 | eric.viseur@be.thalesgroup.com

From: virt-bounces@lists.fedoraproject.org [mailto:virt-bounces@lists.fedoraproject.org] On Behalf Of Robert Strickler
Sent: 18 September, 2014 03:49
To: virt@lists.fedoraproject.org
Subject: [fedora-virt] vanilla bridging network

I am trying to define a network tht just bridges the traffic between the virtual machine network and the LAN attached to eth0

No dnsmasq/dhcp as it is difficult to impossible to tie dnsmasq to the master ISC servers on the LAN.

It should forward/receive packets like a standard hardware bridge

The virtual guests should get their addressing from the dhcp server on the LAN and DNS from the server as well.

with the following I can not get dhcp discover reply from the LAN server, nor can I manually code the IP/gateway/DNS and ping the hard address (172.30.2.33) can anyone tell me what I am missing? Vhost and vguest are both CENTOS7

======================

<networkstatus>

  <class_id bitmap='0-2'/>

  <floor sum='0'/>

  <network>

    <name>plain</name>

    <uuid>31f78c2c-257d-4c57-82e5-0c53deadbeef</uuid>

    <forward mode='bridge'/>

    <bridge name='virbr1' />

    <mac address='52:54:00:b1:34:77'/>

    <domain name='plain'/>

    <ip address='172.30.2.1' netmask='255.255.255.0'>

        <dhcp relay='yes'/>

        <dhcp enable='no' relay='yes'/>

<!--

The relay will not be started if the "enable" property is 'no':

-->

    </ip>

  </network>

</networkstatus>

===========================

A routed environment would be acceptable, but bridged is better as it should not be required to change my routing on the gateway router 

TIA,

Bob