@Hollander:
I had the same problem, so I wil do the XML-reinstall as you said, Bill, to see if it fixes anything.
(Disabling portscan preprocessors and rebooting did not solve anything).
What is weird in my case is: it only happens on WAN1 (VDSL), not on WAN2 (Cable);
And, of course, being the noob that I am, I have no clue why my WAN1-IP would be detected as doing a port scan on some remote IP at all.
And, something even more weirder:
Source: 122.225.97.66
Destination: 81.x.x.x. => my WAN
SID: 136:1 ((spp_reputation) packets blacklisted)
And then my WAN gets blocked by Snort, and not the 122.225.97.66 ???
The update to 3.1.5 should fix the WAN IP getting blocked. The bug fixed in that update causes Snort to ignore the new WAN IP change, so that means your new WAN IP does not get put into the default automatic PASS LIST. As for portscan sensitivity, I have a noticed a few more than I used to get many months ago. The GUI package code I maintain has nothing to do with that, however. That is something triggered by the Snort binary that comes from the snort.org folks.
Bill