Re: [pfSense-discussion] Limiting access through table virusprot

2006-08-01 Thread Thomas ├śksnes
Robert Mortimer wrote: Am Mittwoch, den 26.07.2006, 18:38 -0700 schrieb krt: You can do a connection limit on a rule with a specific proto/port, i.e. simultaneous client connection limit/max state entries per host/max new connections per second. Yes I know that already. Take a look at the

RE: [pfSense-discussion] Limiting access through table virusprot

2006-07-31 Thread Robert Mortimer
Am Mittwoch, den 26.07.2006, 18:38 -0700 schrieb krt: You can do a connection limit on a rule with a specific proto/port, i.e. simultaneous client connection limit/max state entries per host/max new connections per second. Yes I know that already. Take a look at the created rulebase and

Re: [pfSense-discussion] Limiting access through table virusprot

2006-07-27 Thread Scott Ullrich
On 7/26/06, Peter Allgeyer [EMAIL PROTECTED] wrote: [snip] There's another table for sshlockout, but it's not referenced anywhere in a ruleset. Don't know, if useful for anything, nor if it's a stub already for a general solution to SSH brute force attacks. This works with our ssh lockout

Re: [pfSense-discussion] Limiting access through table virusprot

2006-07-27 Thread Peter Allgeyer
Am Mittwoch, den 26.07.2006, 18:38 -0700 schrieb krt: You can do a connection limit on a rule with a specific proto/port, i.e. simultaneous client connection limit/max state entries per host/max new connections per second. Yes I know that already. Take a look at the created rulebase and

Re: [pfSense-discussion] Limiting access through table virusprot

2006-07-26 Thread krt
You can do a connection limit on a rule with a specific proto/port, i.e. simultaneous client connection limit/max state entries per host/max new connections per second. Just place that rule above your more specific permissive rule in your ruleset, as rules are parsed top down. Peter