The bridge-utils package contains a utility needed to create and manage bridge devices. This is useful in setting up networks for a hosted virtual machine (VM).
This package is known to build and work properly using an LFS-7.10 platform.
Download (HTTP): http://sourceforge.net/projects/bridge/files/bridge/bridge-utils-1.5.tar.gz
Download MD5 sum: ec7b381160b340648dede58c31bb2238
Download size: 36 KB
Estimated disk space required: 1 MB
Estimated build time: less than 0.1 SBU
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/bridge
Enable the following options in the kernel configuration and recompile the kernel if necessary:
[*] Networking support ---> [CONFIG_NET]
Networking options --->
<*/M> 802.1d Ethernet Bridging [CONFIG_BRIDGE]
Install bridge-utils by running the following commands:
patch -Np1 -i ../bridge-utils-1.5-linux_3.8_fix-2.patch && autoconf -o configure configure.in && ./configure --prefix=/usr && make
Testing the results requires running the six shell scripts in the
tools/
directory. Two of the tests
require two ethernet ports. Some tests will not preserve the
current network configuration. See tests/README
for details.
Now, as the root
user:
make install
To automate bridge creation and configuration, install the
/lib/services/etc/bridge
service
script included in the blfs-bootscripts-20160902 package.
make install-service-bridge
The bridge
script depends on the
commands /sbin/ifup and /sbin/ifdown and the service
script ipv4-static from
the LFS bootscripts
dated January 27, 2012 or later.
The following configuration file will create a bridge device at boot time and attach the eth0 device to it. If more than one device is desired, use a space separated list of INTERFACE_COMPONENTS. This configuration is useful when planning to run a virtual machine such as kvm/qemu.
Other SERVICE combinations are possible, for example, SERVICES="bridge dhcp". In that case, the address parameters are not needed, but do not interfere if present. The bridge service may also be used alone, but will require additional subsequent configuration.
Do not run a parallel configuration for a device in the
INTERFACE_COMPONENTS list. For instance, in the example below,
do not configure /etc/sysconfig/ifconfig.eth0
to run at boot
time. The command ifdown
br0 followed by command ifup eth0 will work, but
don't try to have both up at the same time.
cat > /etc/sysconfig/ifconfig.br0 << "EOF"
ONBOOT=yes
IFACE=br0
SERVICE="bridge ipv4-static" # Space separated
IP=192.168.1.32
GATEWAY=192.168.1.1
PREFIX=24
BROADCAST=192.168.1.255
CHECK_LINK=no # Don't check before bridge is created
STP=no # Spanning tree protocol, default no
INTERFACE_COMPONENTS="eth0" # Add to IFACE, space separated devices
IP_FORWARD=true
EOF
All addresses should be changed to meet your circumstance.
Last updated on 2016-09-05 17:31:16 -0700