> I am hoping to be able to set up a firewall > between the computer the code will be running on and an SNMP device. I > therefore would like to be able to open just one port. The problem is > that it seems the library chooses an arbitrary source port on the local > computer
Yes - that's fairly standard for most network services. The port at one end of the connection will be fixed, the other will be semi-random. Any sensible firewall configuration should be able to deal with this - allowing through traffic *to* that particular port but not worrying about the source port. If there's only one management system that needs to use SNMP, then you could set up a rule allow netman-host:* <-> agent:161 > (I can specify the remote port, or leave it as default of 162 > no worries). If you're talking about GET/SET requests, then you should be using port 161. Port 162 is used for SNMP traps, not GET/SET requests. Dave ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Net-snmp-users mailing list [EMAIL PROTECTED] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
