Hi coder,
Currently the agent (5.1) on windows system which have multiple IP addresses
returns a response for which the source address is different then the
destination address in the request message (using udp ipv4), this creates
problems with firewalls.
1. Is there anything I've missing? Was it changed in 5.2.x ?
2. If this is the designed behaviour, what would be the best way to change
it? Idealy I would like to pass to the UDP transport layer a source address
as well as a destination, but I can't find an appropriate API to use. For
now all I can come up with is a brute force approch, at snmp_read save the
destination address in aglobal var, and use this var in the UDP transport
when sending responses. I don't like to use global vars, so other options
will be welcome.
3. What about traps? currently I don't need to support them, but I would
like to get your opinions whether there needs to be a "source address"
optional token for the trap destination configuration.
Thanks,
Mark.
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.10.25/102 - Release Date: 14.09.2005
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
