Bitdefender firewall wont allow WSL traffic
Hi there,
I've just installed Bitdefender total security 2020 and I can't seem to get any traffic through WSL2 (windows subsystem for linux). Does anyone know how to allow this or what settings? I've tried a few things but the only thing that works is reverting back to using the Windows Firewall.
Many thanks,
Xephys
Tagged:
2
Comments
Hi Member
Kindly drop an email to bitdefender support at [email protected] regarding your query.
Regards
Flex
(Bitdefender beta tester 2019/ 2020)
Hi there,
Are there any updates on this?
I am experiencing the same issues.
I have the same issue.
Disabling BitDefender firewall fixes it.
Guys, this is ridiculous... We pay for a product that doesn't work as intended and there's not even a response for 2 months regarding this issue. Could you at least tell us whether you're aware of it, you're working on it or you can't do anything about it, since it may be WSL2/Windows related or whatever... Just give us feedback.
Hi Member
Kindly drop an email to bitdefender support at [email protected] regarding your query. These types of issue can only be handled by bitdefender support since they can connect internally with the development team to provide you with a feedback.
Support on forum is limited to basic troubleshooting of the bitdefender products.
Regards
Flex
(Bitdefender beta tester 2019/ 2020)
So yeah... I sent an email, and guess what - nothing!
Nice post. Thanks for sharing this post with us. I got many information from this post. This post was very useful for me. I got many information from this post . Keep sharing this type of post with us. Your all posts are readable. https://jobsflyer.com job search
I also have that issue
Maximum time for support to revert back to any query is 72 hours excluding saturday & sunday.
@Alex D., @Andy_BD kindly have a look.
Regards
Flex
I just renewed my license, and moved my dev env to WSL, if I´d known about this I wouldn't have renewed it
I am experiencing this issue again after 2-3 months. It was working fine until today. :( Do something
Just received an E-Mail that the issue should be resolved with version 25.0.10.52, but it isn't.