On 6 June 2011 14:07, Dattaram Porob <[email protected]> wrote:
> Good suggestion, but then our application supports dynamic addition of
> trap receivers.
Do the receivers all listen on the standard port? (i.e. 162)
Are they all on particular subnets? (e.g 10.x.y.z)
> So, we would have to modfy iptables rules also
> dynamically; which does not sound like a good idea to me :(
You could try using a somewhat looser firewall rule
e.g.
-A INPUT -p udp --sport 162 -s 10.0.0.0/8 -j ACCEPT
Or possibly a handful of such rules, if you'll have trap
receivers on a number of defined subnets.
If necessary, you could relax the source IP address completely,
and allow UDP traffic from port 162 on *any* machine
-A INPUT -p udp --sport 162 -j ACCEPT
As with much security, you're looking for a balance between
locking things down, and keeping things usable!
Dave
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today.
http://p.sf.net/sfu/quest-dev2dev2
_______________________________________________
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