Who runs liveGate?
liveGate is a server program that runs on a machine that's already connected to the
Multicast Internet (aka. "MBone").
It is used to provide 'ad hoc' multicast access, via a tunnel,
to client machines that do not
otherwise have MBone connectivity. For example:
- An ISP can use liveGate to provide multicast access to several of its customers,
as a value-added service - i.e., to bring in additional revenue.
(The ISP can also use liveGate's built-in
statistics web server
to monitor its customers' multicast usage.)
- A telecommuter can use liveGate (running at his central office) to provide
multicast access to his home office.
- A network administrator can use liveGate - in combination with
"liveGate for Intranets"
program - to tunnel selected multicast groups/ports across a firewall.
It's important to note, however, that liveGate
is not a full substitute for providing real multicast connectivity to your client(s).
Before running liveGate, you should first try to give your client(s) a proper
If neither of these conditions hold - e.g., your client is a
Windows PC connected to the Internet via a (non-multicast-capable)
dialup connection - then you can use liveGate instead.
(Note that you do not need "root" permission to run liveGate.)
- First check whether the router that each client uses to access the Internet supports,
or can be reconfigured to support, multicast routing
(either directly, or using an
- If not, then check whether your client is running a Unix system
(anywhere on his local network; not necessarily as his router).
If so, he may be able to run
on this system, to tunnel to your (MBone-connected) network
Finally, note that each liveGate client must also run a
(different) 'controller' program that operates
its end of the liveGate tunnel.
Examples of such programs are
the "liveGate for Intranets"
multicast relaying controller,
and the "liveCaster" 'datacaster'.
Return to the main liveGate page