Avast blocking all traffic through openvpn tap adapter

Avast Free Antivirus / Premium Security
1

Yesterday I updated Avast Internet Security to version 12.1.2272 build 12.1.3076.0 on a Windows 7x64 pc. Since then all traffic running through my openvpn connection is being blocked. If I look in the firewall logs I can see the various network connections being blocked under the “Public/High Risk Zone” rule.

If I look in the avast firewall Settings > Network Profiles I have 2 network adapters, both with the same mac address, both with the profile listed as Private. I see no way to add the openvpn adapter to the network profiles list, nor can I see where I can set this adapter the Private profile.

I’ve added application rules to the firewall but they are still being blocked.

The openvpn ip’s are within the 10.0.0.0/10.255.255.255 range in the “Friends” list.

I’ve repaired the avast install from the windows add/remove programs option but the issue persists.

Anyone know how I can allow this traffic? It was working fine for years on the previous version of avast.

2

Anyone have any advice? I’ve opened a support ticket with Avast but they have been unable to resolve the issue.

3

Welcome to the forum.I’ve reported this to Avast and asked for assistance. I use the free version so am not familiar enough with the firewall module
which isn’t included in the free version.

4

I have exactly the same problem.

5

Thanks for the reply! At least it’s not only me having the problem. I’m still working with Avast Support but have yet to resolve the issue. I’ll post here if the come up with something but I suspect it’s not a config issue & that there is a bug in the software.

6

You can try this: (not sure if it will work, it is from another link, but looks promising)

1. Open Avast Internet Security.
2. Click on ‘firewall’,
3. On the firewall settings click onto ‘expert settings’.
4. Click ‘packet rules’
5. Select ‘add new entry’ and enter ‘VPN’
6. Enter the following action, ‘allow protocol: all - direction: in/out’
7. Add the server ip address(es).
8. Click ‘OK’. You should now be able to connect to the VPN.

7

Thanks for the tip but it doesn’t resolve the issue. The problem appears to be that all VPN traffic is being considered part of the “Public/High Risk Zone”. Any firewall rule I create is only applied to the “Private” zone as that is what is assigned to the NIC. Still working with support on this but no resolution yet.

8

Avast support has confirmed this is a bug and will be fixed in the next release.

We found where the issue is and it's now fixed in our internal build. It will be released at the end of this month. For now, please, disable Avast Firewall, when you are connecting to VPN.