Outpost Packet Message Manager
AGWPE and Telnet Support
Outpost v2.0 Release Highlights
Outpost v2.0 is now available and delivers 2 new pieces of functionality... AGWPE support and Telnet access for F6FBB BBSs.
AGW Packet Engine
The following are excerpts from Ralph Milnes' KC2RLM website (and an excellent source of information on AGWPE and soundcard support, http://www.soundcardpacket.org/):
"AGWPE is a multi-TNC management utility written by George SV2AGW. Before AGWPE, a packet device such as a TNC or other radio modem could only be used by one program at a time. Likewise, a packet program could only use one packet device at a time. AGWPE changed all that. It lets a program access multiple packet devices at one time, and lets a packet device be shared by multiple programs at one time.
"AGWPE performs this magic by placing the TNC in KISS mode and assuming responsibility for handling most of the logic functions built into the TNC. The TNC is left to handle just tone modulation/demodulation, or modem functions. AGWPE also works with radio modems, such as the YAM and Baycom that already lack logic functions and must rely on the logic functions of a control program such as AGWPE."
More importantly, AGWPE supports sound-card packet, the largest request from the general packet, and Outpost user community. There are 2 versions of AGWPE available for download:
AGW Packet Engine is a free version for the ham radio community
The currently distributed free version (AGWPE.zip, “AGW Packet Engine ver 2004.1108 Win95/98/NT/2k/ME/XP”) works fine with Outpost. See the link below on where to find it.
If you do not plan on using AGWPE with Outpost, there is no overhead added to the existing Outpost operating environment.
For users wishing to try AGWPE, I STRONGLY RECOMMEND that you thoroughly understand how AGWPE works, is set up, and can be confirmed operational before deploying it with Outpost. Please note: AGWPE support is a field of study unto itself and is out of scope in terms of general Outpost Support.
For more information on AGWPE, use your favorite internet search engine with the search string: “description of AGWPE”, or check out these 2 sites…
Also, see the AGWPE HOW-TO message in the Drafts Folder of your v2.0 installation for more information.
The F6FBB BBS supports a Telnet interface in addition to the standard radio/TNC interfaces. Some Emergency Response Teams have exploited this capability within their own EOC. The benefit of this approach is that, when the BBS that is supporting an operational area is also network accessible, a telnet connection could be made from the EOC to the BBS without tying up an additional radio and TNC. While this implementation is typically the case when the BBS is co-located with the EOC, it could be remotely located as well. However, it does rely on the supporting internet infrastructure to be operational to use it (disaster permitting).
If you do not intend to use Telnet with Outpost, there is no overhead added to the existing Outpost operating environment.
For users wishing to use Telnet, consult with your BBS Sysop to determine if Telnet access is available on your BBS, and you are authorized for access. If it is, I STRONGLY RECOMMEND that you understand how Telnet works, is set up, and can be confirmed operational before deploying it with Outpost.
See the Telnet HOW-TO message in the Drafts Folder of your v2.0 installation for more information.
As always, your feedback on this version is important to ensure that the integrity of the emergency response mission of Outpost is maintained. Thanks for your support!
Please send any feedback to
updated: January 15, 2016