AccessGrid.org

Configuring a Unicast Bridge

A Unicast Bridge allows sites that do not have functioning Multicast to participate within an Access Grid Session. Through the Venue Client, users can connect to your Unicast Bridge that has been configured. This guide is designed to demonstrate how to configure a Bridge for either AG 2.x and AG 3.x, or alternatively, how to configure 2 separate bridges for both AG 2.x and AG 3.x.

Prerequisites:

  • Each venue client must previously been started with profile information filled out and certificates installed (if required);

  • Hostname must be configured in /etc/hosts; and
  • Hostname must be configured in DNS;

Troubleshooting

If you are unable to connect to the Bridge, or the "vic" streams or participants within "rat" are missing, ensure the firewall (iptables [if used]) has been configured correctly. The section “Security” (http://www.accessgrid.org/node/772) details how to configure the firewall correctly.

Installation

AG 2.x

For Access Grid Version 2, a configuration file needs to be created which lists all of the Venue Servers and Venues you wish to supply a Unicast Bridge too.

If we name the configuration file BridgeServer24.cfg, then the following provides an example of what the file should look like:

name = <Bridge Name>
location = <Bridge Location>
qbexec = /usr/bin/QuickBridge
BRIDGESERVER = <Bridge Server Name>
#use this port range for the bridge server as a whole
portMin = 20000
portMax = 20100

#<Venue Name>
[Venue Address]
type = Venue

#<2nd Venue Name>
[2nd Venue Address]
type = Venue

For each <####>, will need to be replaced with a Name or address you would like to use.

An example file I use is:

[BridgeServer]
name = CQU
location = JasTest4
qbexec = /usr/bin/QuickBridge
BRIDGESERVER = CQU
#use this port range for the bridge server as a whole
portMin = 20000
portMax = 20100

#CQU
[https://vv2.ap-accessgrid.org:8000/Venues/000000f7ae2d27460081004e009d00a8385]
type = Venue

#APAG Lobby
[https://vv2.ap-accessgrid.org:8000/Venues/default]
type = Venue

AG 3.x

For Access Grid Version 3, you simply point the bridge to a Registry, which will then enable anyone who uses your AG3 Venue client to connect to the bridge. The Caveat is that the Venue Client, by default (Currently), only displays the closest 10 Bridges. Therefore, if more than 10 bridges are registered, it may be possible for some sites to not be able to see your Bridge.

Start-up Shell Scripts

The following shell scripts can be used if you wish to simply start the various unicast bridges. They have specifically been designed to shutdown all current bridge processes and start the requested bridges. These shell scripts can also be used in conjunction with “cron” so that the bridges can be used to restart every day, week or month.

For starting the AG 2.x Bridge (only), the following shell script file BridgeServer24.sh can be used:

killall -9 QuickBridge
killall -9 BridgeServer24
BridgeServer24 -c <location/of/Configuration/file>

For starting the AG 3.x Bridge (only), the following shell script file BridgeServer.sh can be used:

killall -9 Bridge
killall -9 BridgeServer
Bridge -p 20200 -u http://www.accessgrid.org/registry/peers.txt -n "<Bridge Name>" -l "<Location>"

If you wish to start both AG 2.x and AG 3.x Bridges, the following shell script file Bridge.sh can be used:

killall -9 QuickBridge
killall -9 Bridge
killall -9 BridgeServer24
BridgeServer24 -c ./BridgeServer24.cfg &
Bridge -p 20200 -u http://www.accessgrid.org/registry/peers.txt -n "Bridge" -l "Rockhampton, Queensland, Australia" &

Note that this example has the <Bridge Name> and <location> that I currently use.

 

login or register to post comments