07-27-2006 10:43 PM - edited 03-10-2019 03:08 AM
With an INLINE solution, what is the best way to deny p2p connections from source IP addresses? There are several choices.
deny-attacker-inline - do not transmit this packet and future packets from the attacker address for a specified period of time.
deny-connection-inline - do not transmit this packet and future packets on the TCP Flow.
deny-packet-inline - do not transmit this packet
deny-attacker-victim-pair-inline - do not transmit this packet and future packets on the attacker/victim address pair for a specified period of time.
deny-attacker-service-pair-inline - do not transmit this packet and future packets on the attacker address victim port pair for a specified period of time.
We would like to deny the connection for the p2p application but not deny the source altogether.
Solved! Go to Solution.
07-27-2006 11:13 PM
If the Signature is using a TCP based engine then I would use deny-connection-inline. If the Signature uses something like UDP then it would be best to use deny-packet-inline.
Hope that helps,
Jonathan
07-27-2006 11:13 PM
If the Signature is using a TCP based engine then I would use deny-connection-inline. If the Signature uses something like UDP then it would be best to use deny-packet-inline.
Hope that helps,
Jonathan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide