Serious Issues With The Firewall

karl77

I have found some issues, some are related:

-I get no internet access if I set Stealth mode on or remote in whatever network (trust, home, public, untrusted, etc).

-Firewall not blocking portscans from the Internet, regardless of network type (trust,home, public, untrusted, etc), although I get pop-up saying it was. I even tried using a long range of ports which enconpasses open and closed ports.

-Ports from 1043 to 1046 are open to the Internet in any network type set in BD (trust, home, public, untrusted, etc).

[svchost.exe]

TCP [::]:1043 [::]:0 LISTENING

[wininit.exe]

TCP [::]:1044 [::]:0 LISTENING

[lsass.exe]

TCP [::]:1045 [::]:0 LISTENING

[services.exe]

UDP 192.168.1.7:137 *:*

-If I try to TCP port scan closed port or ports in my machine from the Internet (using another host), it responds to it with a rst packet. The problem here is not remaining stealth.

-The general rule "block incoming icmp" also blocks outgoing ICMP (eg. in a ping.exe google.com). These outgoing ICMP are not reaching my wifi card. Even if I completely allow ping.exe to use all network resources I still fail to ping.exe any host in the internet.

What I make of all this: blindly blocking ICMP is not a good approach, the protocol is necessary and some ICMP codes should be alowed, especially when they are related to an established connection or when started by me (eg in a ping.exe google.com).

Seriously, this firewall needs to be reshaped to the likes of Kaspersky (more rule custumizing, etc). I loved bitdefender but this firewall module does not make justice to Bitdefender.

Is there any chance of seeing a patch for this in the current version of bitdefender??

karl77

I decided to try bitdefender internet security once more and I found out I had some security services disabled. Those were hindering Bitdefender from doing proper firewall filtering.

Namely: Basic filtering and UAC.

Problem solved.