Hi there,
We had an incident this afternoon when a user scanned an IP that was not included in his access list, and it rebooted the firewall. I used his account and tried to scan a few other IPs that were not included in the access list, all were successful. I tried to change default deny to default reject in the rule file, and the result was the same. Is it a known problem? how was it able to reboot the firewall? Thanks.
YanYan
We had an incident this afternoon when a user scanned an IP that was not included in his access list, and it rebooted the firewall. I used his account and tried to scan a few other IPs that were not included in the access list, all were successful. I tried to change default deny to default reject in the rule file, and the result was the same. Is it a known problem? how was it able to reboot the firewall? Thanks.
YanYan