Hi,
Toni> Having the same problem Joseph had, but on WinNT4.0 with both
Toni> the 00-02-19 and the 00-08-31 binary snapshots. I did not find
Toni> any information on this in the Readme, FAQ and the mail
Toni> archives. So though I'm a newbie, please give me a hint.
well, the answer in in the source:
the session is set up with TnmSnmpCreateSession(), that initializes
the default address with 127.0.0.1 and then binds only to this
address/port combo. therefore with other adresses the port is
unreachable.
a responder session does not have -address configure option. maybe by
accident, maybe by a deeply hidden reason :-)
adding the -address option should cause no harm, because it does not
break the default behavior; a simple patch would be:
--- scotty/tnm/snmp/tnmSnmpTcl.c-merk Wed Jun 28 14:44:33 2000
+++ scotty/tnm/snmp/tnmSnmpTcl.c Sun Jul 15 12:42:41 2001
@@ -198,6 +198,7 @@
};
static TnmTable responderOptionTable[] = {
+ { optAddress, "-address" },
{ optPort, "-port" },
{ optVersion, "-version" },
{ optCommunity, "-community" },
so the responder can listen to the port at any address:
> Tnm::snmp responder -address 0.0.0.0 -port 161 -community public
but then a non-default community string could be wise, but anyway.
Erik
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.
This archive was generated by hypermail 2b29 : Thu Jan 03 2002 - 14:56:27 MET