Hello Leroy, First off, use the command `brctl show br0`. This will verify for yourself whether your eth0 interface has properly been bound to your bridge. Another helpful debugging tool is navigating to the /proc/net/bonding directory and then `cat br0`. This will show the slave interfaces to your bond, what type of bonding mode you are using, and whether the bridge is currently up and on which interfaces. I'm not familiar with OpenSuSE, so I can't verify your configuration. But, from the ip addr commands you ran, I can tell you that your configuration doesn't look correct. The IP interfaces should only be bound to your bridged interface. I'm seeing an IP network as well as network routes associated with eth0 instead of br0. Also, in ifcfg-br0 I'm not seeing a network gateway defined which would be necessary to route outside of your home LAN. You'll also want to verify what type of bridge you have configured. For most home LANs, you'll want to use "fault-tolerance/active-backup", as LACP won't work without a supporting northbound Ethernet switch. If your eth0 interface has IP information from previously, you'll want to manually remove the IP address with `ip addr del` and `ip route del`, or, just reboot your home Linux server. Joel Gerber Network Operations Specialist - Telephone Telephone Eastlink Joel.Gerber@xxxxxxxxxxxxxxxx T: 519.786.1241 -----Original Message----- From: lartc-owner@xxxxxxxxxxxxxxx [mailto:lartc-owner@xxxxxxxxxxxxxxx] On Behalf Of Leroy Tennison Sent: June-07-15 11:44 PM To: lartc@xxxxxxxxxxxxxxx Subject: Trying to set up a bridge for KVM 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: <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 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: <BROADCAST,MULTICAST,UP,LOWER_UP> 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: <BROADCAST,MULTICAST,UP,LOWER_UP> 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html ��.n��������+%������w��{.n����j�\�)�� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
