From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leroy Tennison Date: Tue, 09 Jun 2015 03:12:07 +0000 Subject: Re: Trying to set up a bridge for KVM Message-Id: <55765987.6090506@verizon.net> List-Id: References: <55750F6F.5060206@verizon.net> In-Reply-To: <55750F6F.5060206@verizon.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org This is what is so frustrating, all I'm doing is booting with ifcfg-br0 and ifcfg-eth0 as shown below (no 'routes' file at all). ifcfg-eth0 is configured to be started by another process (br0 I assume). Unless something is wrong with ifcfg-br0 or ifcfg-eth0 I'm not telling eth0 to acquire an IP address but it "auto-magically" does. The 'ip ...' listing is based on that configuration, no intermediate modifications. I checked the working configuration (at work) again and the only differences are that the IP address in ifcfg-br0 is different (no surprise - different subnet) and it has a routes file containing one line (modified to be the equivalent of my network): default 192.168.1.1 - The only other difference is the working system is on openSuSE 12.3 and I'm on 13.1. This is why I was hoping someone would spot something wrong in one of those two files. On 06/08/2015 12:48 AM, Mike Schmidt wrote: > You have both eth0 and br0 claiming the same network as far as routing is > concerned. If eth0 is in br0, as I think you expect it to be, you should > remove the ip address from eth0, and let br0 handle the network. > If that's not the case. make sure that eth0 and br0 are in different > subnets. Otherwise, you need to add different metrics to the routes, so > that the kernel can always send packets out via the same interface. > > On Sun, Jun 7, 2015 at 11:43 PM, Leroy Tennison > wrote: > >> I've used what I've found on the web and even copied a working config from >> a hypervisor at work running the same version of openSuSE (13.1) I use at >> home - nothing works at home. The working config from the hypervisor (the >> only change is the IP address for home) is listed below, what am I doing >> wrong? (Thanks for your help). >> >> ifcfg-br0 >> >> USERCONTROL='no' >> STARTMODE='auto' >> BOOTPROTO='static' >> BRIDGE='yes' >> BRIDGE_STP='off' >> BRIDGE_FORWARDDELAY='0' >> BRIDGE_PORTS='eth0' >> BRIDGE_PORTPRIORITIES='-' >> BRIDGE_PATHCOSTS='-' >> NETWORK='' >> NETMASK='' >> BROADCAST='' >> PREFIXLEN='' >> IPADDR='192.168.1.101/24' >> ETHTOOL_OPTIONS='' >> MTU='' >> NAME='' >> REMOTE_IPADDR='' >> >> ifcfg-eth0 >> >> BOOTPROTO='none' >> BROADCAST='' >> ETHTOOL_OPTIONS='' >> IPADDR='' >> MTU='' >> NAME='Intel Ethernet controller' >> NETMASK='' >> NETWORK='' >> REMOTE_IPADDR='' >> STARTMODE='auto' >> USERCONTROL='no' >> >> I can't even ping the default gateway. My configuration shows: >> >> ip addr >> >> 1: lo: 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 brd 127.255.255.255 scope host lo >> valid_lft forever preferred_lft forever >> inet6 ::1/128 scope host >> valid_lft forever preferred_lft forever >> 2: eth0: mtu 1500 qdisc pfifo_fast >> master br0 state UP qlen 1000 >> link/ether 00:1e:8c:f1:68:94 brd ff:ff:ff:ff:ff:ff >> inet 192.168.1.6/24 brd 192.168.1.255 scope global eth0 >> valid_lft forever preferred_lft forever >> inet6 fe80::21e:8cff:fef1:6894/64 scope link >> valid_lft forever preferred_lft forever >> 3: br0: mtu 1500 qdisc noqueue state UP >> link/ether 00:1e:8c:f1:68:94 brd ff:ff:ff:ff:ff:ff >> inet 192.168.1.101/24 brd 192.168.1.255 scope global br0 >> valid_lft forever preferred_lft forever >> inet6 fe80::21e:8cff:fef1:6894/64 scope link >> valid_lft forever preferred_lft forever >> >> ip route >> >> default via 192.168.1.1 dev eth0 proto static >> 127.0.0.0/8 dev lo scope link >> 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.6 >> 192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.101 >> >> I previous (and now current) configuration was DHCP which is where >> probably the 192.168.1.6/24 comes from (and the DHCP scope stops at node >> 100). >> -- >> To unsubscribe from this list: send the line "unsubscribe lartc" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> > >