Dave,
I did look at clientaddr but the explanation provided to me back then seemed to indicate a different use. I dont have the email in front of me but I was left with the impression that clientaddr ... specified the client address ... i.e. from the perspective of the polling server... the DESTINATION address. I went back to the documentation and it seems to be what I need. I guess I was confused over the term "client".
Allow me to then confirm the behaviour.
If I use clientaddr from my polling server and do an snmpget or snmpwalk and specify TCP:192.168.1.1:1161 it will create a TCP packet and put 192.168.1.1 in the source IP address and 1161 in the TCP port field.
If a true statement, and a full connection is made (i.e able to listen to the response) then I'm good and appologize for not understanding the documentation as well as I should.
David Lott
President
JDMS, LLC
-------------- Original message --------------
From: "Dave Shield" <[EMAIL PROTECTED]>
> On 11/08/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]>wrote:
> > I need to specify the SOURCE IP address in both my polling / agent
> > environment.
>
> Have you looked at the "clientaddr" configure token, which should
> provide at least part of what you are looking for.
>
> There's also a patch (#1509943) on the SourceForge tracker that feels
> relevant to this requirement. Give those two a whirl, and let us know
> what else might be required.
>
> Dave
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
