Mine never actually did exist as a live IP. In my case they were in my DMZ using private range 10. SELECT dstip FROM accounting WHERE dstip = '10.149.239.2' List the Columns in database \d accountingĬonfirm the ips that you see in the webgui. So there is a link below which is where I sourced my initial investigation from but the suggested command didn’t work for me so I had to figure it out.įirst login to postgres from a root SSH prompt psql -U postgresĬonnect to the reporting database \c reporting Long Term Solution Delete Entries From Database Temporary Workaround Reset IP Countġ) Login to unit via SSH (you must have the “loginuser” and “root” user passwords/SSH keys set via the web interface).ħ) Type “user_limit_exceeded$” and hit enterĪt this point the IP table will be flushed out and the unit should no longer be in violation of the license. Therefore the permanent option is jump into the postgres database and tidy up the offending IPs.
There is a problem however in that the first set of commands just perform a temporary reset and it will keep coming back to annoy you for a week until it gets flushed out. I knew the limit was nonsense because only 4 devices existed but still needed to reset the firewall count as it’s behaviour is to indiscriminately block random addresses over the 50 count. I now realised I had caused this issue using nmap to scan my /24 DMZ network.
I was using UTM9’s web protection for quite some time and suddenly starting receiving emails to say I’d reached the 50 IP address limit. If you’ve got the Sophos UTM up and running in your home network then you may come across this issue at some point.
0 kommentar(er)
