I can't seem to find the right combination. It seems it would be as simple as creating address objects and routing any traffic destined for the remote LAN through the Wireguard server. It makes sense that when the remote peer is connected to the LAN peer that the remote peer is then essentially on the LAN. I suspect I need a better understanding of zones. ![]() However, I am having trouble going from the LAN to the remote peer. They are connected and I am able to remote desktop into the LAN without issue. WireGuard is running on Ubuntu behind the SonicWall and Window 10 on the remote. ![]() ![]() If your SonicWALL is not yet set up, use Option B. I am trying to use WireGuard in the same way as SoniWall's SSL VPN, whereas when the remote peer is connected, I can remote desktop (VNC) to either the SonicWall's LAN from the remote peer or to the remote peer from a client anywhere on the SonicWall's LAN. Task 1 SonicWALL Configuration If you’re familiar with SonicWALLs and already have a working VPN setup on your SonicWALL, you can skip the SonicWALL setup and use Option A. I am having trouble wrapping my head around the last piece.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |