Firewalla blocking Teamviewer over VPN

VPN
1

I have a server running with network traffic routed via a wireguard VPN. This morning I had a few instances of an alarm tripping noting that the VPN disconnected and reconnected, but it seemed to have righted itself after a few hours. The kill switch was engaged so it was no big deal. I tried to access via teamviewer - the machine showed online - but it ultimately wouldn’t connect. I remoted in from another machine on the network and verified that the machine was accessible locally. I also verified in Firewalla that the site flow was being blocked, but the diagnosis didn’t point back to any rules.

I created a rule to always allow the teamviewer.com domain to access that machine. Now attempts to access via Teamviewer are blocked, but it references my rule to always allow traffic to teamviewer.com as the reason for blocking the flow.

Any ideas?

2

Interesting…

I had rebooted multiple times and had the same results. I just disconnected from the VPN and connected to a different VPN and was able to access both with and without the allow rule. Reconnected to the original VPN and all seems to be working again.

I guess I’ll settle for ‘it’s fixed’. Still wondering what caused the weirdness…

3

Are you using a third party VPN? or using Firewalla VPN Server? If you are using a third party VPN server, highly likely the block is the target accepting the VPN

4

It is a third party vpn… but the disconnect-reconnect routine resolved it.

5

Very likely when you disconnect and reconnect, the 3rd party VPN changed your source IP address. And some of the IP addresses used by that VPN service is likely black listed by team viewer.