Re-reading the FAQ I think if it hits one rule then it won't hit any others. I'm guessing to actually delete the defaults I'd have to do it via terminal and I'm not confident on the commands.
Regardless my main issue is now resolved, thanks all :)
Ah I'm with you thanks!
Gotcha, and I understood that the difference in the rule was the default is marked as TCP traffic whereas my custom one was marked as both. What was confusing me is the Usenet traffic coming in was marked as "TCP" so the default rule should have been applying...
Ok thanks, again just to highlight I am not able to edit any of the original rules and I can't even change the protocol to apply to "Both" for the 119 and 563 rule. I've had to create a new rule which is essentially a duplicate of the existing default rule and configure that to both so it looks...
Ok, they are all default except the bottom one which I added to make my PC considered a gaming device (yes this is the device I'm having issues on). Also the default rules are greyed out and I can't edit them, is that normal?
I'm wondering if anyone is able to help me with my Usenet traffic which is being classed into NNTP category?
I can see it coming in on Port 119 and I have the default rule which is Port 119 and 563 to be classified as "File Downloads" but when I monitor my traffic live my Usenet is getting...