# Known Issues & Troubleshooting

# Wireguard can connect on some networks, but not others

#### UDP Blocked

There is a chance that UDP connections are blocked on the network that you are on. You will have to do your own research regarding "disguising" UDP traffic; the Wireguard website has some input on this: [https://www.wireguard.com/known-limitations/#tcp-mode](https://www.wireguard.com/known-limitations/#tcp-mode)

#### Same Network Type on Local & Remote Network

This can cause some networking confusion if you are trying to connect to LAN addresses on the remote network.

For instance, if you are locally on a network with IP range of 192.168.0.0/24, connected to Wireguard linking you to a remote network whose IPs are also 192.168.0.0, add the network address of the remote network as an "AllowedIP". For our example above, add `192.168.0.0/24` to the "AllowedIP" list.

For example, if you wanted all connections to be able to connect to the remote network and LAN, your "AllowedIPs" may look something like `::/0, 0.0.0.0/0, 192.168.0.0/24`.

You may also have to uncheck the option "block untunneled traffic" if you are still unable to connect to the remote LAN.