BridgeInterface

Languages:

English  • français

Maintainer

Daniel B. from Firewall Services

Version

Contrib 10:

0.2-9

Contrib 9:

0.2-1

smeserver-bridge-interface

The latest version of smeserver-bridge-interface is available in the SME repository, click on the version number(s) for more information.

Description

smeserver-bridge-interface is a small package allowing you to bridge your Internal Interface with one or more virtual tap interfaces. It's main goal is to be used with the new OpenVPN-Bridge contrib, but it has been split in another contrib as it can be used in other situations (if you want to run a virtual machine on your SME Server with qemu for example).

Requirements

• SME Server 7.X
• SME Server 8.X
• SME Server 9.X

Installation

• install the rpms

yum --enablerepo=smecontribs install smeserver-bridge-interface

• for SME9

you have to enable dag and epel directories see bugzilla:8337

yum --enablerepo=smecontribs,epel,dag install smeserver-bridge-interface

• Configure the bridge

Log into your server using SSH, and configure the bridge like you want. For most installation, the default settings should be OK, but you should check it:

db configuration show bridge
bridge=service
    bridgeInterface=br0
    ethernetInterface=eth0
    status=enabled
    tapInterface=tap0

• • bridgeInterface: (br0) is the name of the bridge device (usually br0)
  • ethernetInterface: (eth0|eth1) is the real interface you want to bridge. It should already be set to your actual InternalInterface

	Warning:
	The bridge contrib is not compatible with the NIC bonding option. If you're running in serveronly mode and use NIC bonding, you should disable it before starting the bridge. To do so, you can use the admin console, either by loging in as the admin user, or as root, and then type the command console

• • tapInterface: (tap0,tap1) is a comma separated list of tap interfaces to create and add to the bridge. Usually, you'll only need one tap interface (tap0)
  • status: (enabled|disabled) is the status of the service (should it be started automatically on boot)

Once you're sure everything is ok, just start the service:

/etc/init.d/bridge start

And check with ifconfig that everything is OK (eth0 and tap0 should have IP 0.0.0.0 and running in promiscous mode, br0 should have the IP of your Internal Interface)

You can also check the bridge is correctly configured

brctl show br0

Should output something like:

bridge name     bridge id               STP enabled     interfaces
br0             8000.00e04c101418       no              eth0
                                                        tap0

Uninstall

If you remove this contrib while it's in use, you may have a problem shuting down br0 (waiting for br0 to become free etc...), and you'll have to hard reboot your server. To prevent this you should

• Disable the service

db configuration setprop bridge status disabled

	Warning:
	Remember that if you disable the service, OpenVPN_Bridge will stop working, so if you have it installed, you should disable or remove it too

• Reboot your server, the bridge wont start
• Remove the rpm

yum remove smeserver-bridge-interface

	Warning:
	signal-event post-upgrade;signal-event reboot may be required in case the system looses the internal interface

Source

The source for this contrib can be found in the smeserver CVS on sourceforge.

Bugs

Please raise bugs under the SME-Contribs section in bugzilla and select the smeserver-bridge-interface component or use this link

---