I think I've found a bug... nothing I configured in
/etc/sysconfig/network worked. However, a little "post processing"
solved the problem (I can ping google.com again! For some reason, even
with the broken configuration, I could ping 192.168.1.1, just no
further). I tested the below, found it to work and finally put it in
/etc/init.d/after.local to get networking to work on boot (I have no
idea when openSuSE implemented after.local - why do they have to be
different?).
ip route del 192.168.1.0/24 dev eth0
ip route del default dev eth0
ip route add default via 192.168.1.1 dev br0 proto static
ip addr del 192.168.1.8/24 dev eth0
Now the ip commands look like
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 169.254.9.142/16 brd 169.254.255.255 scope link eth0:avahi
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 br0 proto static
default dev eth0 scope link metric 1002
127.0.0.0/8 dev lo scope link
169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.9.142
192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.101
I wouldn't disagree with anyone who says the solution is ugly. I don't
know (among a lot of things I don't understand about this issue) why
eth0 got an RFC 3927 IP address and frankly I don't care. Anything not
explicitly listed in the original four ip commands was "done for me"
(like the 'metric 1002'). Next stop: does KVM actually work with this
configuration...
--
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
