Is there any reason that you want those IP addresses accessing your box
at all?
You can probably block several /8's and make things work better.
John
Scott Vander Dussen wrote:
> Lamer question-
> I have a MT box we use for a public hotspot and logs reveal folks are trying
> to hack the passwo
PA General List"
Subject: [WISPA] MT Lamer question
> Lamer question-
> I have a MT box we use for a public hotspot and logs reveal folks are
> trying to hack the password (from WAN, not actual customers) - IPs trace
> back to China and stuff.. anyhow - is there an easy way to imple
ireless-boun...@wispa.org] On
> Behalf Of Josh Luthman
> Sent: Tuesday, October 27, 2009 9:16 AM
> To: WISPA General List
> Subject: Re: [WISPA] MT Lamer question
>
> I've never seen a rule like this on Mikrotik, but what Butch preaches is a
> proactive approach. I do this
Oh yeah, it's been so long! (: Ok, that's what we did in the past too..
thanks..
`S
-Original Message-
From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf
Of Josh Luthman
Sent: Tuesday, October 27, 2009 9:16 AM
To: WISPA General List
Subject: Re:
> Nick Olsen
> Brevard Wireless
> (321) 205-1100 x106
>
>
>
>
> From: "Scott Vander Dussen"
> Sent: Tuesday, October 27, 2009 12:03 PM
> To: "WISPA General List"
> Subject: [WISPA] MT Lamer question
>
I've never seen a rule like this on Mikrotik, but what Butch preaches is a
proactive approach. I do this on my core router.
Filter rules:
accept input 22/tcp from src.addr list
block all of the input 22/tcp traffic
Repeat for 21, 8291, 80 etc
Add "good" or well known IPs to the src.addr list
Th
http://www.linktechs.net
LIVE On-Line Mikrotik Training
Author of "Learn RouterOS"
-Original Message-
From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On
Behalf Of Scott Vander Dussen
Sent: Tuesday, October 27, 2009 11:03 AM
To: WISPA General List
Subject: [W
, 2009 12:03 PM
To: "WISPA General List"
Subject: [WISPA] MT Lamer question
Lamer question-
I have a MT box we use for a public hotspot and logs reveal folks are
trying to hack the password (from WAN, not actual customers) - IPs trace
back to China and stuff.. anyhow - is there a
Lamer question-
I have a MT box we use for a public hotspot and logs reveal folks are trying to
hack the password (from WAN, not actual customers) - IPs trace back to China
and stuff.. anyhow - is there an easy way to implement a temporary (12 hour) or
so ban on an IP after x attempts? Thanks.
