3,250
edits
Changes
Jump to navigation
Jump to search
Line 3:
Line 3: − + − − mailto:daniel@firewall-services.com Line 17:
Line 15: + + + + + + Line 38:
Line 42: − + − + − + Line 60:
Line 64: + + + + + + + Line 68:
Line 79: + + + + + +
→Bugs
===Maintainer===
===Maintainer===
[[User:VIP-ire|Daniel B.]]<br/>
[mailto:daniel@firewall-services.com[[User:VIP-ire|Daniel B.]]] from [http://www.firewall-services.com Firewall Services]
[http://www.firewall-services.com Firewall Services]<br>
=== Version ===
=== Version ===
=== Requirements ===
=== Requirements ===
*SME Server 7.X
*SME Server 7.X
*SME Server 8.X
*SME Server 9.X
=== Installation ===
=== Installation ===
*install the rpms
*install the rpms
yum --enablerepo=smecontribs install smeserver-bridge-interface
*for SME9
yum --enablerepo=smecontribs install smeserver-bridge-interface
yum --enablerepo=smecontribs install smeserver-bridge-interface
**'''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 allready 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
{{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}}
{{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 interfcae (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)
=== Uninstall ===
=== 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 box|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
yum remove smeserver-bridge-interface
{{Warning box|signal-event post-upgrade;signal-event reboot may be required in case the system looses the internal interface}}
=== Source ===
=== Source ===
and select the smeserver-bridge-interface component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-bridge-interface|title=this link}}
and select the smeserver-bridge-interface component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-bridge-interface|title=this link}}
{{#bugzilla:columns=id,product,version,status,summary |sort=id |order=desc |component=smeserver-bridge-interface|noresultsmessage="No open bugs found."}}
===Changelog===
Only versions released in smecontrib are listed here.
{{ #smechangelog: smeserver-bridge-interface}}
----
----
[[Category:Contrib]]
[[Category:Contrib]]
[[Category:Administration:VPN]]