|
| Home | FAQ | Download |
| User Guide | Applications | Internals |
| License | Publications | Contact |
|
|
This is a compilation of the most frequently asked questions about the Antigone framework. Please report any bugs, inconsistencies or omissions you find in this FAQ to irrer@eecs.umich.edu. This document will be updated as needed. Please check the Antigone home site for more recent update before sending email.
Antigone is a secure group middleware layer designed to enable the flexible definition and implementation of a wide range of group security policies. The core of Antigone is a suite of micro-protocol implementing mechanisms that provide the fundamental services required for secure group communication. By composing the mechanisms and their features, a developer may implement the exact policy desired.
For more detailed information, see the HTML Antigone manual included with the distribution or on the home web-site at antigone@factotem.com.
The source for Antigone is freely available from the home web-site at antigone@factotem.com. Additionally, installation and development documentation are available.
The source distribution includes a full HTML manual including and overview of Antigone, development notes, and API description. At this moment, the manual is unfinished, but will be completed in the near future.
First check this FAQ carefully and view the antigone email list archive (instructions for accessing the archive are available from contact page). If you still are unable to resolve your problem, or if you have suggestions or comments, forward them to the Antigone mailing list also available on the contact page.
The following is required to build the Antigone libraries
Once multicast support has been enabled, you will need to add a route for multicasting. Valid multicast address range from 224.0.0.0 to 239.255.255.255. So, a route should contain, at the very least, the range of addresses you wish to use for multicasting. The following describes the commands used by two UNIX versions to enable multicast routing. See your local man page for specific route command arguments.
Linux:
% route add -net 224.0.0.0 netmask 240.0.0.0 dev eth0
SunOS:
% route add -net 224.0.0.0 -netmask 240.0.0.0 -interface hme0
NOTE: Depending on the system configuration, the device name of your interface may differ from those listed above. NOTE: On many systems, you must have root access to modify host routing table.