On Wed, Feb 19, 2014 at 8:23 PM, Digimer lists@alteeve.ca wrote:
On 19/02/14 05:46 PM, Alexander Dalloz wrote:
What is your complete network configuration?
Please see:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/...
Alexander
Iirc, there is/was a bug where the bridge's file name had to sort
[ I'm happy I didn't get bitten by any bug like that! ]
Maybe there _was_ a bug.
I have interfaces that start with a "c" and that alphabetically comes before "ethX" or "pXpY". I haven't seen any problems with this configuration.
I don't have an IP address (and gateway+dns info) on my bridges.
*after* the slaved interfaces. So I always use 'vbrX' instead of 'brX
This "bug" you speak of may be entirely related to your Ethernet bonding though and not the bridging aspect.
'
(virtual bridge). I don't think the actual DEVICE="..." matter, just the file name, but I like to make the match so I just do vbrX for both.
Here is an example of my bridges:
==== vim /etc/sysconfig/network-scripts/ifcfg-vbr2 ==== # Internet-Facing Network - Bridge DEVICE="vbr2" TYPE="Bridge" NM_CONTROLLED="no" BOOTPROTO="none" IPADDR="10.255.50.1" NETMASK="255.255.0.0" GATEWAY="10.255.255.254" DNS1="8.8.8.8" DNS2="8.8.4.4" DEFROUTE="yes" ====
Then an example interface (I use bonds, but this could just as easily be a normal ifcfg-ethX)
==== vim /etc/sysconfig/network-scripts/ifcfg-bond2 ==== # Internet-Facing Network - Bond DEVICE="bond2" BRIDGE="vbr2" NM_CONTROLLED="no" BOOTPROTO="none" ONBOOT="yes" BONDING_OPTS="mode=1 miimon=100 use_carrier=1 updelay=120000 downdelay=0 primary=eth2" ====
Note that the IP moves to the bridge.
hth
Thanks for sharing configs. It's always helpful to see how others are configuring their systems.
-- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos