BitDefender Firewall Feature breaks Hyper-V Switch
Greetings, no matter what I've done, I've been unable to get Bitdefender to work with the Default Hyper-V (Or any other "Private" Hyper-V) Switch for that matter.
I've had to disable the product's firewall.
Bridging the connection works, however this is ill suited for cases where I need to do large file transfers between the VM and Host.
I had once contacted support about this many months ago but didn't really get anywhere and ended up giving up due to frustration.
Currently using Total Security 26.0.16.69
Comments
-
The issue can only be resolved by support team and maybe it will have to be shared with the bitdefender developers.
Generate bitdefender support tool logs (https://www.bitdefender.com/consumer/support/answer/1733/)
Generate bitdefender connectivity logs (https://www.bitdefender.com/consumer/support/answer/9689/)
Share the logs & your query with bitdefender support team by dropping them an email at bitsy@bitdefender.com
The support team will reply back to your query within next 24-48 hours excluding weekends.
Regards
Life happens, Coffee helps!
Show your Attitude, when you reach that Altitude!
Bitdefender Ultimate Security Plus (user)
0 -
Hmm, I was hoping I would be able to avoid that but doesn't sound like it. I don't feel that I've had great success with bitdefender support in the past and find myself reluctant to open a support ticket due to the time zone difference and I currently have limited free time.
0 -
@Alexandru_BD, @Mike_BD - Kindly check on this.
Regards
Life happens, Coffee helps!
Show your Attitude, when you reach that Altitude!
Bitdefender Ultimate Security Plus (user)
1 -
Hello @kiyomaka and welcome to the Community!
Try to create a rule to allow on port 135 in Bitdefender firewall.
For more context regarding the firewall, check the following articles:
If the rule doesn't solve the issue, it will be necessary to get in touch with the Support teams for further investigation.
Let us know how it goes.
Regards
Premium Security & Bitdefender Endpoint Security Tools user
1 -
elieve I figured out the issue, Bitdefender appears to be breaking the NAT adapter within Hyper-V by dropping the DHCP request packet, such as the one below.
This specific packet was sent from a VM trying to obtain an IP Address
81 13.698982 0.0.0.0 255.255.255.255 DHCP 356 DHCP Request - Transaction ID 0xadba0e9b
I was able to resolve the issue by creating a rule as follows.
All Applications
Network: Home/Office
Proto: UDP
Direction: Inbound
Local IP: 255.255.255.255
Local Port: 67
Remote IP: 0.0.0.0
Remote Port: 68
Is there perhaps a way to apply this rule to the Hyper-V Daemon/Network service itself opposed to a global host level rule?
1 -
There might be a way to apply the rule, but only if you can find the service of that Hyper-V in the firewall rules list..
Our engineers can take a look, if necessary. Should you require their assistance, you can get in touch with the Support Teams by choosing one of the contact methods available here:
https://www.bitdefender.com/consumer/support/
Regards
Premium Security & Bitdefender Endpoint Security Tools user
1
