Need help with port-forwarding (Virgin Media Hub 3.0) - Hardware & Software

Long story short, I'm trying to host a server in source games for me and a friend to play together, most specifically No More Room in Hell at the current time, but once sorted it should be fine globally. I'm on Virgin Media, with a SuperHub 3.0, and using COMODO firewall. [IMG]http://i.imgur.com/VHlkqw4.png[/IMG] These are the port-forwarding settings on my router, and [IMG]http://i.imgur.com/OjKI85I.png[/IMG] this is my firewall's global rulesets. Under "Portsets" tab I've also listed 27000-27030. What am I missing here? My brother's on the same network, and can host Tabletop Simulator just fine (11155). I have windows firewall disabled, and COMODO's firewall is set to "training" mode. The router's firewall is active, and apparently needs to be for port forwarding to function in the first place. And yet, despite all this my game's still not visible over the internet, and can't be connected to via my external IP. I'm wondering if that last rule on the screenshot from COMODO has anything to do with it, but it's there by default.

Narrowed it down to being my firewall actually. I know disabling it works (I "closed" it before, apparently that makes no difference), but what actual rule it is blocking it, or whatever I have to set, I have no clue.

I'm not the best with networking stuff, but "Block IP In From MAC [B]Any[/B] to MAC [B]Any[/B] Where Protocol is [B]Any[/B]" sounds like it's blocking quite a lot, it's probably that

Yeah, that rule was there by default, don't know why. Got rid of it, put my firewall back into "normal" mode and it works fine now.

The SuperHub has a firewall built in. You really don't need to run something like Comodo on your machine unless you're totally paranoid. Windows Firewall will do just fine.

[QUOTE=Morbo!!!;52516587]Yeah, that rule was there by default, don't know why. Got rid of it, put my firewall back into "normal" mode and it works fine now.[/QUOTE] That's there as an implicit deny all at the end. It's a rule that's processed last and should be there, otherwise you're opening up everything to everything.

[QUOTE=benbb;52520675]The SuperHub has a firewall built in. You really don't need to run something like Comodo on your machine unless you're totally paranoid. Windows Firewall will do just fine.[/QUOTE] [QUOTE=Levelog;52526669]That's there as an implicit deny all at the end. It's a rule that's processed last and should be there, otherwise you're opening up everything to everything.[/QUOTE] I'm getting conflicting messages here. I do have the hub firewall on, and I do have COMODO on, but without that last rule. I haven't yet confirmed if it works without it, I should probably check that anyway. [editline]2nd August 2017[/editline] Yeah, works fine without that rule. The question is if I failed to properly make it an exception in the firewall but what a blag matey

[QUOTE=Morbo!!!;52531259]I'm getting conflicting messages here. I do have the hub firewall on, and I do have COMODO on, but without that last rule. I haven't yet confirmed if it works without it, I should probably check that anyway. [/QUOTE] benbb was referring to both, Levelog referring only to Comodo. No conflict. Sounds like you got it working though.

[QUOTE=SataniX;52531520]benbb was referring to both, Levelog referring only to Comodo. No conflict. Sounds like you got it working though.[/QUOTE] It's whether this "otherwise you're opening up everything to everything." is made up for by this "The SuperHub has a firewall built in"

Yeah. Basically you can get rid of Comodo, I was looking at your post incorrectly when I said that. The SuperHub almost definitely has an implicit deny as well, just doesn't show it. Can't think of any firewall device that doesn't.

Thanks fellas