vistafirewallcontrol.freeforums.org

[Chrysalis]

Hi

here is what I did to get these working, is possible to have this default in new version?

on Local+DNS+DHCP+Update(svchost) zone I added a rule I called IPv6 TERODO which allows inbound UDP from port 3544.
on LocalSystem zone I added a rule I called ICMP6(ping/trace) which allows ICMPv6.

Hope that helps others with same problem.

[VistaFirewallControl]

Thank you, the both are added to the defaults and will be available in the next build

[ibelike]

Is this related to this:
?

I'm using the free portable version, so I guess everything I don't personally block should go through.
It's not a big deal, though. It happens when using uTorrent. When I was using Comodo it asked me if I wanted to allow such connections, separately from utorrent.exe connections (I think they go through svchost or something).

[VistaFirewallControl]

As mentioned in the notification WindowsFirewall made the block for System application, the meta application to designate the system core activity.
So a WidowsFirewall related applet should be used to enable the activity.
"ET default Block All" is the filter name from WindowsFirewall.

[ibelike]

Maybe I didn't understand this properly, but is there something that can be done in the free version to enable this traffic?

[VistaFirewallControl]

The problem is not W7FC related at all (regardless Free or Plus version).
If an activity is blocked by WindowsFirewall, WindowsFirewall can be used to enable only.

Are you sure the activity is required for the mentioned application principally?
Even if you do have IPv6 worldwide connectivity the blocked incoming ICMPs can hardly affect the application operability.

[ibelike]

The problem is not W7FC related at all (regardless Free or Plus version).
If an activity is blocked by WindowsFirewall, WindowsFirewall can be used to enable only.

W7FC is the only firewall I'm using right now. Windows Firewall is disabled completely.

Are you sure the activity is required for the mentioned application principally?
Even if you do have IPv6 worldwide connectivity the blocked incoming ICMPs can hardly affect the application operability.

I'm not sure if I need it or if I want to enable this. I think it's uTorrent related, because it seems to happen when I run uTorrent and I get the yellow icon in uTorrent, saying "No incoming connections". It still seems to work fine, tho. (Perhaps I'd be able to connect to more people if that traffic went through.)

As I've said, it's not a big deal for usability, but right now I'm actually curious about this. When I was using Comodo firewall I could let that traffic through (got a "green light" in uTorrent). I'm not 100% sure, but 99.5% sure. So if W7FC has nothing to do with this I wonder what does.. is it a Windows Firewall bug? I did enable Windows Firewall for a short period and tested a little bit (changed some stuff), but then I disabled it after that. Did some setting stay, even after disabling it? I'll have a look myself..

[VistaFirewallControl]

>W7FC is the only firewall I'm using right now. Windows Firewall is disabled completely.

That is not correct, despite the WF GUI is switched off, WindowsFilteringPlatform (the network security core) is up and running and keeps (processes) a lot of filtering rules.
Some of the rules maybe persistent. There is a rule disables all the incoming traffic, which was not explicitly enabled by other rules, for instance. The rule is determined by the firewall policy and can not be configured directly via WF related applet. Anyway the rules marked as “WindowsFirewall:” are unreachable with W7FC. FYI: The typical rules count of WF unconfigured system (without W7FC at all) is about several hundreds, we could provide you with a browsing tool if you would like to investigate yourself.


>I'm not sure if I need it or if I want to enable this. I think it's uTorrent related, because it seems

Reasonably, but there are no strict evidences unfortunately.
The logic could be - the application is the only tries to utilize IPv6, the system, trying to establish v6 connectivity, produces some v6 implicit activity.
Anyway ICMP is hardly managed by user applications directly; typically the functionality belongs to TCP internal stack


>(Perhaps I'd be able to connect to more people if that traffic went through.)

It could theoretically be if there are people with IPv6 connectivity only (without ipv4 connection at all)
Please keep in mind, the activity is ICMP incoming, it’s not a payload traffic anyway, it’s not TCP or UDP, it’s just a control messages (as “host unreachable” for instance)
ICMP type 129 is not specified so it’s hard to reveal the activity purpose precisely.

>As I've said, it's not a big deal for usability, but right now I'm actually curious about this. When I was using Comodo firewall I could let that traffic through (got a "green light" in uTorrent). I'm not 100% sure, but 99.5% sure.

It’s just a sign that mentioned firewall does not control _all_ the traffic or enables a part of the traffic implicitly. Correct?

>.. is it a Windows Firewall bug?

Rather a security policy you did not expect in advance.
The explanation of the blocking could as simple as “do not allow ‘pinging’ me on IPv6, I’m stealth on IPv6", for instance

[ibelike]

Thanks for the explanation.

I actually tried later with only Comodo firewall and I saw that there was still the symbol in uTorrent, which goes against what I thought at first. That symbol then changes to green occasionally, with Comodo and with W7FC as well. uTorrent is very vague with what that means, the popup just says "no incoming connections".
But yeah, the traffic looks ok, from what I can tell. I don't even use torrents much, so perhaps other users who do might give more feedback. But the "blocked" messages definitely only start popping up when using uTorrent.