Changes

From SME Server
Jump to navigationJump to search
127 bytes added ,  07:37, 23 September 2009
m
Line 39: Line 39:  
**'''bridgeInterface''': (br0) is the name of the bridge device (usually br0)
 
**'''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
 
**'''ethernetInterface''': (eth0|eth1) is the real interface you want to bridge. It should already be set to your actual InternalInterface
{{Warning 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}}
+
{{Warning 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. 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)
 
**'''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)
 
**'''status''': (enabled|disabled) is the status of the service (should it be started automatically on boot)

Navigation menu