On 10/03/2016 07:00 PM, TE Dukes wrote:> /etc/sysconfig/ifcfg-eth1 > GATEWAY=192.168.1.1...> /etc/sysconfig/ifcfg-lo > GATEWAY=192.168.1.1Don't specify GATEWAY in interface files where it isn't used. This should be set on eth0 only.> # brctl show > > bridge name bridge id STP enabled interfacesOK, so you don't have a bridge interface. If you want to access guest VMs from the LAN, you need to set one up. Refer to the documentation I sent earlier. You'll create a bridge interface configuration, and the move the IP configuration from whichever ethX device you want to enslave to the bridge. The ethX configuration file, then, won't have any IP configuration specified, instead it'll contain "BRIDGE=br0".
Am 04.10.2016 um 08:46 schrieb Gordon Messmer <gordon.messmer at gmail.com>:> On 10/03/2016 07:00 PM, TE Dukes wrote: >> /etc/sysconfig/ifcfg-eth1 >> GATEWAY=192.168.1.1 > ... >> /etc/sysconfig/ifcfg-lo >> GATEWAY=192.168.1.1 > > Don't specify GATEWAY in interface files where it isn't used. This should be set on eth0 only. > >> # brctl show >> >> bridge name bridge id STP enabled interfaces > > OK, so you don't have a bridge interface. If you want to access guest VMs from the LAN, you need to set one up. Refer to the documentation I sent earlier. You'll create a bridge interface configuration, and the move the IP configuration from whichever ethX device you want to enslave to the bridge. The ethX configuration file, then, won't have any IP configuration specified, instead it'll contain "BRIDGE=br0".This can be accomplished by just this (generates ifcfg files etc): # virsh iface-bridge eth0 br0 If eth0 is the LAN interface otherwise change this. The VM configuration must then use br0/bridge as interface/type. -- LF
> -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > Behalf Of Gordon Messmer > Sent: Tuesday, October 4, 2016 2:47 AM > To: CentOS mailing list > Subject: Re: [CentOS] Virtualization Networking > > On 10/03/2016 07:00 PM, TE Dukes wrote: > > /etc/sysconfig/ifcfg-eth1 > > GATEWAY=192.168.1.1 > ... > > /etc/sysconfig/ifcfg-lo > > GATEWAY=192.168.1.1 > > Don't specify GATEWAY in interface files where it isn't used. This shouldbe> set on eth0 only. > > > # brctl show > > > > bridge name bridge id STP enabled interfaces > > OK, so you don't have a bridge interface. If you want to access guest VMs > from the LAN, you need to set one up. Refer to the documentation I sent > earlier. You'll create a bridge interface configuration, and the move theIP> configuration from whichever ethX device you want to enslave to thebridge.> The ethX configuration file, then, won't have any IP configurationspecified,> instead it'll contain "BRIDGE=br0". >I did. I disabled NetworkManager and created one. Its not there now because I have started over so many times. Thanks
On 10/04/2016 03:24 AM, Leon Fauster wrote:> This can be accomplished by just this (generates ifcfg files etc): > > # virsh iface-bridge eth0 br0Brilliant! I'm not sure why I haven't noticed that in the docs, before. I've definitely been to the page where Red Hat documents it... Thanks.
On 10/04/2016 04:18 AM, TE Dukes wrote:> I disabled NetworkManager and created one.You don't need to do that on CentOS 7, and I wouldn't recommend it. Use NetworkManager where it works.
On 04/10/16 11:24, Leon Fauster wrote:> Am 04.10.2016 um 08:46 schrieb Gordon Messmer <gordon.messmer at gmail.com>: >> On 10/03/2016 07:00 PM, TE Dukes wrote: >>> /etc/sysconfig/ifcfg-eth1 >>> GATEWAY=192.168.1.1 >> ... >>> /etc/sysconfig/ifcfg-lo >>> GATEWAY=192.168.1.1 >> >> Don't specify GATEWAY in interface files where it isn't used. This should be set on eth0 only. >> >>> # brctl show >>> >>> bridge name bridge id STP enabled interfaces >> >> OK, so you don't have a bridge interface. If you want to access guest VMs from the LAN, you need to set one up. Refer to the documentation I sent earlier. You'll create a bridge interface configuration, and the move the IP configuration from whichever ethX device you want to enslave to the bridge. The ethX configuration file, then, won't have any IP configuration specified, instead it'll contain "BRIDGE=br0". > > > > This can be accomplished by just this (generates ifcfg files etc): > > # virsh iface-bridge eth0 br0 > > If eth0 is the LAN interface otherwise change this. The VM > configuration must then use br0/bridge as interface/type. >I've just tried that on my machine (CentOS 7): # virsh iface-bridge enp4s0 br2 error: An error occurred, but the cause is unknown # virsh iface-bridge enp3s0 br1 error: An error occurred, but the cause is unknown # command -v virsh /bin/virsh # ip add 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether <redacted> brd ff:ff:ff:ff:ff:ff inet 192.168.1.2/24 brd 192.168.1.255 scope global enp3s0 valid_lft forever preferred_lft forever inet6 <redacted>/64 scope link valid_lft forever preferred_lft forever 3: enp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether <redacted> brd ff:ff:ff:ff:ff:ff inet 192.168.2.2/24 brd 192.168.2.255 scope global enp4s0 valid_lft forever preferred_lft forever 4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN link/ether <redacted> brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN qlen 500 link/ether <redacted> brd ff:ff:ff:ff:ff:ff # brctl show bridge name bridge id STP enabled interfaces virbr0 8000.<redacted> yes virbr0-nic Regards, Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20161004/9a70a736/attachment-0001.sig>