WireGuard Configuration

Comments

2 comments

  • Avatar
    James Willhoite

    The allowedIps in the WireGuard Config file will only allow access to that ipaddress. That is a "Split-Tunnel" in that all traffic except the AllowedIPs will go through the Default Route. 

    Example, if your NAS is ipaddress 192.168.0.10 then in the AllowedIPs you put just that 192.168.0.10/32 and bring the tunnel up. You should only be able to ping that address and nothing else.

    If you keep the AllowedIPs as 0.0.0.0/0 then this will route ALL Traffic through the VPN tunnel. You can then go in to either that Clients Profile on the Firewalla UI and block traffic to a specific LAN, but allow 192.168.0.10 .....

    I do this for my Work. I have a Connection FROM my Work to my WireGuard VPN with the AllowedIPs = 192.168.2.0/24 which says that only traffic destined for that IP subnet is allowed to go through that VPN... but in the Firewalla UI (For that Client's Profile) I say block all access to my 192.168.2.0/24 lan. Then put in the Allow rules for the specific IP addresses my Work Network is allowed to access....

    0
    Comment actions Permalink
  • Avatar
    JS

    Hi James,

    Thank you for your response.

    Yes that is exactly what I am doing now. Just that by doing this way, the config file is sent across to my peers and they are able to edit and change the AllowedIPs to 0.0.0.0/0 therefore there is no controls.

    If i were to follow your method, it meant that my Synology NAS have to be on the 192.168.0.10 and the rest of my devices to be on 192.168.2.x am I right?

    0
    Comment actions Permalink

Please sign in to leave a comment.