Difference between revisions of "BridgeInterface"
(Created page with '{{Languages}} ===Maintainer=== Daniel B.<br/> [http://www.firewall-services.com Firewall Services]<br> mailto:daniel@firewall-services.com === Description === ...') |
|||
| Line 31: | Line 31: | ||
| − | **bridgeInterface is the name of the bridge device (usually br0) | + | **'''bridgeInterface''': (br0) is the name of the bridge device (usually br0) |
| − | **ethernetInterface is the real interface you want to bridge. It should allready be set to your actual InternalInterface | + | **'''ethernetInterface''': (eth0|eth1) is the real interface you want to bridge. It should allready be set to your actual InternalInterface |
| − | **tapInterface is a list of tap interfaces to create and add to the bridge. Usually, you'll only need one tap interfcae (tap0) | + | {{Note box|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}} |
| − | **status is the status of the service (should it be started automatically on boot) | + | **'''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 interfcae (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: | Once you're sure everything is ok, just start the service: | ||
| Line 51: | Line 52: | ||
br0 8000.00e04c101418 no eth0 | br0 8000.00e04c101418 no eth0 | ||
tap0 | tap0 | ||
| + | |||
=== Uninstall === | === Uninstall === | ||
yum remove smeserver-bridge-interface | yum remove smeserver-bridge-interface | ||
Revision as of 12:51, 11 March 2009
Maintainer
Daniel B.
Firewall Services
mailto:daniel@firewall-services.com
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
Installation
- install the rpms
yum --enablerepo=smecontribs 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 allready be set to your actual InternalInterface
- 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 interfcae (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
yum remove smeserver-bridge-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
