Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    One tunnel for remote access

    Scheduled Pinned Locked Moved WireGuard
    30 Posts 4 Posters 2.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K
      korr2221 @thebabufrik
      last edited by

      @thebabufrik I'm using the 192.168.1.x range for my main network.

      1 Reply Last reply Reply Quote 0
      • K
        korr2221 @thebabufrik
        last edited by

        @thebabufrik got it to connect but now I can't reach my other devices. Screenshot 2022-02-12 104441.jpg

        thebabufrikT 1 Reply Last reply Reply Quote 0
        • thebabufrikT
          thebabufrik @korr2221
          last edited by

          @korr2221 change allowed-ips with 0.0.0.0/0, can you reach your other devices?

          M K 3 Replies Last reply Reply Quote 0
          • M
            mcury Rebel Alliance @thebabufrik
            last edited by

            I followed this guide: https://docs.netgate.com/pfsense/en/latest/recipes/wireguard-ra.html

            Its working perfectly, I can access all the networks I have in my .conf file.
            Using the SPIT tunnel method.

            Note that only full tunnel needs outbound NAT and 0.0.0.0/0 in allowed-ips.

            dead on arrival, nowhere to be found.

            1 Reply Last reply Reply Quote 0
            • K
              korr2221 @thebabufrik
              last edited by

              @thebabufrik tried, no luck.

              1 Reply Last reply Reply Quote 0
              • K
                korr2221 @thebabufrik
                last edited by

                @thebabufrik yeah I tried both split and full tunnel :( and I followed the same thing. I have no idea where I could have gone wrong. I just upgraded wireguard on it and now that interface with the handshake is no longer there.

                M 1 Reply Last reply Reply Quote 0
                • M
                  mcury Rebel Alliance @korr2221
                  last edited by mcury

                  @korr2221 said in One tunnel for remote access:

                  @thebabufrik yeah I tried both split and full tunnel :( and I followed the same thing. I have no idea where I could have gone wrong. I just upgraded wireguard on it and now that interface with the handshake is no longer there.

                  double check the keys in pfsense and in the client.. maybe regenerate them and reapply ?

                  dead on arrival, nowhere to be found.

                  K 1 Reply Last reply Reply Quote 0
                  • K
                    korr2221 @mcury
                    last edited by

                    @mcury I did. I mean it's green and the handshake is successful for a reason I think? Going to retry but I think it's something with the firewall or routing. Do I need to create static routing so I can see my LAN on the other subnet for me to see it?

                    M K 2 Replies Last reply Reply Quote 0
                    • M
                      mcury Rebel Alliance @korr2221
                      last edited by

                      @korr2221 said in One tunnel for remote access:

                      @mcury I did. I mean it's green and the handshake is successful for a reason I think? Going to retry but I think it's something with the firewall or routing. Do I need to create static routing so I can see my LAN on the other subnet for me to see it?

                      No, no static route required.

                      Follows my configuration:

                      Firewall WAN rule:
                      4494a4f2-fed6-4748-99d0-d62b0d8c1857-image.png

                      Wireguard allow rule:
                      4b855fbe-3edc-4a4b-a1f8-cc40a1e65b70-image.png

                      Tunnel setup:
                      b291ce3e-e95d-4931-8147-bc85907cda0f-image.png

                      Peer setup:
                      bf047904-b0e0-49a1-8435-02c7a4561d00-image.png

                      Wireguard app in my phone:
                      c8802248-46cb-4408-aa8e-db5c7ca56022-image.png

                      dead on arrival, nowhere to be found.

                      1 Reply Last reply Reply Quote 0
                      • K
                        korr2221 @korr2221
                        last edited by

                        @korr2221 the weirdest thing ever. So I reinstalled WG twice, and all i did was change the order of the allowed IPs. Where I would put 0.0.0.0/0 in the middle. Suddenly it works now.

                        M 1 Reply Last reply Reply Quote 0
                        • M
                          mcury Rebel Alliance @korr2221
                          last edited by

                          @korr2221 said in One tunnel for remote access:

                          @korr2221 the weirdest thing ever. So I reinstalled WG twice, and all i did was change the order of the allowed IPs. Where I would put 0.0.0.0/0 in the middle. Suddenly it works now.

                          Weird indeed.. full tunnel is that you want? If so, you need an outbound NAT as well.
                          Only 0.0.0.0/0 won't work.

                          dead on arrival, nowhere to be found.

                          K 1 Reply Last reply Reply Quote 0
                          • K
                            korr2221 @mcury
                            last edited by korr2221

                            @mcury i didn't really need full tunnel, but for whatever reason that made it work adding the 0.0.0.0/0 scope. Can someone explain? LOL.

                            I know I needed to adjust the NAT if I want full tunnel. But at this point it works and I am happy.

                            Just checked my NAT settings, ZERO NAT rules. No idea what's going on.

                            M 1 Reply Last reply Reply Quote 0
                            • M
                              mcury Rebel Alliance @korr2221
                              last edited by

                              @korr2221 said in One tunnel for remote access:

                              @mcury i didn't really need full tunnel, but for whatever reason that made it work adding the 0.0.0.0/0 scope. Can someone explain? LOL

                              0.0.0.0/0 will route everything that is connected to wireguard through the tunnel, including internet access, but you would also need an outbound NAT created.

                              Split tunnel (0.0.0.0/0 not included in allowed-ips) you will only gain access to the networks included in allowed-ips.
                              Full tunnel (0.0.0.0/0 included in allowed-ips), wireguard connections will be routed to the internet as well.

                              dead on arrival, nowhere to be found.

                              K 1 Reply Last reply Reply Quote 0
                              • K
                                korr2221 @mcury
                                last edited by

                                @mcury just realized my LAN works but can't access public sites. It works without the 0.0.0.0/0 I'm guessing adding it in the middle did something and now it works like it's supposed to. But still having trouble with public sites. Odd...

                                K M 2 Replies Last reply Reply Quote 0
                                • K
                                  korr2221 @korr2221
                                  last edited by

                                  @korr2221 nevermind. Changed my DNS from comcast to 1.1.1.1 now all is working normally. WHAT? :3

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    mcury Rebel Alliance @korr2221
                                    last edited by mcury

                                    @korr2221 said in One tunnel for remote access:

                                    @mcury just realized my LAN works but can't access public sites. It works without the 0.0.0.0/0 I'm guessing adding it in the middle did something and now it works like it's supposed to. But still having trouble with public sites. Odd...

                                    Do you want to use the Internet from pfsense while connected to wireguard?
                                    Or the phone Internet?

                                    dead on arrival, nowhere to be found.

                                    K 1 Reply Last reply Reply Quote 0
                                    • K
                                      korr2221 @mcury
                                      last edited by

                                      @mcury it doesn't matter. I know if I want to use the internet from pfsense it is full tunnel and if I want from my phone it's split tunnel. But after changing my dns my split tunnel works correctly now. Odd!

                                      M 1 Reply Last reply Reply Quote 0
                                      • M
                                        mcury Rebel Alliance @korr2221
                                        last edited by

                                        @korr2221 It doesn't matter? Really? Ok then.

                                        dead on arrival, nowhere to be found.

                                        K 1 Reply Last reply Reply Quote 0
                                        • K
                                          korr2221 @mcury
                                          last edited by

                                          @mcury well i mean for some people it would. but for me, I just wanted to have remote access. haha.

                                          M 1 Reply Last reply Reply Quote 0
                                          • M
                                            mcury Rebel Alliance @korr2221
                                            last edited by

                                            @korr2221 said in One tunnel for remote access:

                                            @mcury well i mean for some people it would. but for me, I just wanted to have remote access. haha.

                                            So, you just want to access local resources? That's all?
                                            Remove 0.0.0.0/0 from the allowed ips configuration file, and leave the configuration in pfsense exactly as I posted above.

                                            dead on arrival, nowhere to be found.

                                            K 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.