Let’s assume you have a server with two Ethernet network interface. You wish to bridge traffic between the interfaces. Here are the commands to setup the bridge: 1. Take eth0 off line ifconfig eth0 down 2. Take eth1 off line ifconfig eth1 down 3. Define a bridge named “bridge01″ brctl addbr bridge01 4. Add eth0 [...]
Let’s assume you have a server with two Ethernet network interface. You wish to bridge traffic between the interfaces. Here are the commands to setup the bridge:
1. Take eth0 off line
ifconfig eth0 down
2. Take eth1 off line
ifconfig eth1 down
3. Define a bridge named “bridge01″
brctl addbr bridge01
4. Add eth0 to the bridge named “bridge01″
brctl addif bridge01 eth0
5. Add eth1 to the bridge named “bridge01″
brctl addif bridge01 eth1
6. Bring up the Ethernet interfaces with no IP addresses:
ifconfig eth0 0.0.0.0 up ifconfig eth1 0.0.0.0 up
7. Bring the bridge online with a single ip address
ifconfig bridge01 192.168.100.101 up
Try to test by ping from one side of the bridge to the other. It may take up to 30 seconds for the ping to start running due to the learning phase on the bridge.
If it fails then double check the above setup. Take a look at the MAC addresse that the bridge sees with:
brctl showmacs br1
Verify that there is no bridge filtering is turned on:
# cd /proc/sys/net/bridge # for f in bridge-nf-*; do echo 0 > $f; done
Also might need to enable IP forwarding in /etc/sysctl or with:
echo "1" > /proc/sys/net/ipv4/ip_forward
If you actually want to be able to filter via iptables, the bridged traffic then turn on bridge-nf for iptables:
echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
Now bridged packets will be passed through the FORWARD chain. So for example to log all packets one could do:
iptables -I FORWARD -j LOG
or to block all UDP traffic:
/sbin/iptables -A FORWARD --protocol udp -j DROP
Additional resources:
