Hi all.
Here is an excerpt from the manual, which seems to state that all LRQing gatekeepers must be explicitly known to the GNUgk (v2.2.1).
Section [RasSrv::Neighbors]
...
Conversely, the gatekeeper will only reply to LRQs sent from neighbors defined in this section.
This behaviour seems to be extending to LCFs received from "unknown"
gatekeepers, which are reported as "Trapped":
2005/01/26 17:06:27.610 2 RasSrv.cxx(1240) RAS Trapped LCF
2005/01/26 17:06:27.610 1 Neighbor.cxx(639) RAS Unknown reply LCF
2005/01/26 17:06:30.617 2 RasSrv.cxx(168) RAS Read from 155.207.12.79:3607
This makes it very difficult for a GnuGK v.2.2.1 to be part of a directory gatekeeper hierarchy, that redirects peripheral gatekeepers to other gkps, without the GNUgk having to know all of them. This was not the case with GNUgk v.2.0.8.
There must be a way aroung this, but I can'g figure it out. Your help is appreciated.
Regards. Dimitris Daskopoulos GRNET/RTS
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________________
List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
