TC1977
TC1977
That's because macOS doesn't send LAN traffic through the VPN, by default.
Well, one way to do it would be to modify the WIreGuard client config on your Windows machine to exclude local IPs. I'm using this [from the WireGuard mailing list...
So my first question, given recent reports of [Wireguard problems with macOS 10.15](https://github.com/trailofbits/algo/issues/1629), is what version of macOS you're running, and what version of Wireguard client you're running.
@ShantanuNair You could try checking the WireGuard client logs. On your Mac, open the WireGuard app, and at the bottom of the windowpane with your listed connections the little gear...
So what jumps out at me is about 13 seconds of repeated `Failed to send data packet` messages, despite attempts to activate and deactivate the tunnel: ``` 2019-11-24 18:44:00.872541: [NET]...
IPsec is said to be slower than WireGuard, but shouldn't be _that_ much slower. I wouldn't be surprised at all if your IPsec connection is also screwed up. It might...
Run with `./algo -vvv` please? You might get a more detailed error code.
The only hint I could find anywhere is to make sure you're logging into DO from an IP that has a reverse DNS configured. Not sure where I saw that.
~~Don't forget to `sudo netfilter-persistent save` after changing the iptables rules.~~ This only applies if you change the iptables rules by using the `sudo iptables -A...` and `sudo ip6tables -A...`...
Don't forget to open up port 80 on the Algo server (and the cloud firewall, if applicable) if you want to access the Pi-hole web interface.