All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leroy Tennison <leroy.tennison@verizon.net>
To: lartc@vger.kernel.org
Subject: Trying to set up a bridge for KVM
Date: Mon, 08 Jun 2015 03:43:43 +0000	[thread overview]
Message-ID: <55750F6F.5060206@verizon.net> (raw)

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).

             reply	other threads:[~2015-06-08  3:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08  3:43 Leroy Tennison [this message]
2015-06-08 12:09 ` Trying to set up a bridge for KVM Joel Gerber
2015-06-09  3:12 ` Leroy Tennison

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55750F6F.5060206@verizon.net \
    --to=leroy.tennison@verizon.net \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.