noa levy wrote:
Thanks!
I forgot to mention, though, that my source port for the SNMP informs is
also random, so I can't match against the destination port for the
incoming packet - does the recent target also maintain a port list or is
it IP addresses only?
How about something like this:
iptables -t nat -A POSTROUTING -p udp --dport 162 -j SNAT --to-source :29999
iptables -t mangle -A PREROUTING -p udp --dport 29999 -j MARK --set-mark 99
iptables -A input -p udp -dport ! 29999 -m mark --mark 99 -j ACCEPT
That 29999 source port is an arbitrary number outside the bounds set in
/proc/sys/net/ipv4/ip_local_port_range. The mark number is also arbitrary.
The overall effect is that your SNMP inform packets will all appear to
come from port 29999. Replies to that port will be marked prior to being
de-SNAT-ed. Now, in the filter table you can ACCEPT marked packets that
have been recognized by de-SNAT and thus no longer have a destination
port of 29999. Any bogus packets sent to port 29999 will still contain
that port number when they hit the filter rule, and thus will not be
accepted.
I have no way to test any of the above, so view it all with appropriate
suspicion.
--
Bob Nichols Yes, "NOSPAM" is really part of my email address.
