Blacklisting problem

[ElliotS]

Hi everyone, has anyone else come across this ?
I had a few issues setting up an internal extension with registration and the username/password combo tripped some of the rules in the blacklist.
This resulted in the main router getting locked out !

The IP 192.168.0.1 has been blacklisted for 86400 sec.

I don't understand quite why the router IP has ended up in the logs and blacklisted but I'm worried that if I get spammed or DOS from outside the internal network the same might happen, but obviously I don't want to lessen the rules on the security

Thoughts appreciated?

 

[leejor]

That is a private IP address, so, I have to assume that 3CX is on the same, local LAN...that being the case simply white-list 192.168.0.0, subnet 255.255.0.0

I got tired of local ATA's getting themselves blacklisted, for no apparent reason, every once in a while, and resorted to that.

 

[ElliotS]

Thanks, didn't think it was going to be that simple!

 

[AWS2P]

subnet shouldn't be 255.255.255.0 ?

 

[ElliotS]

yup that's what I've set, thanks

 

[leejor]

I have devices, with static IP's I move between two networks, so I'm used to using the 255.255.0.0. 255.255.255.0 will also work on a single network, but all being local, and not really a security issue it doesn't matter.