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

    Hamachi

    General pfSense Questions
    10
    51
    29.4k
    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.
    • S
      sullrich
      last edited by

      You need to setup a advanced outbound rule that maintains the same source and destination port for Hamachi.

      This has been covered in their forum with the OpenBSD thread.

      1 Reply Last reply Reply Quote 0
      • C
        Cyrandir
        last edited by

        CrashX, did you figure this out?  If so, could you share your wisdom?  I simply dont have time to go digging through their stuff trying to figure it out right now.

        Thanks in advance

        1 Reply Last reply Reply Quote 0
        • C
          CrashX
          last edited by

          Unfortunately no. I messed with it quite a bit as did my friend with pfsense.
          The OpenBSD thread at Hamachi doesn't really help much as it isn't saying what goes where in pfsense, but is more generic to BSD.
          So I don't kow what else to try. I will probably just end up switching back to a Linux box with shorewall, unless someone has a specific walk through for Hamchi over pfsense.

          1 Reply Last reply Reply Quote 0
          • S
            sullrich
            last edited by

            Visit NAT -> Outbound.

            Create a new rule.

            Then see this screenshot.

            1 Reply Last reply Reply Quote 0
            • C
              Cyrandir
              last edited by

              Thx for the help sullrich, and I'll implement tonight or tomorrow

              1 Reply Last reply Reply Quote 0
              • C
                CrashX
                last edited by

                I tried the setting from the screen shot, field for field and still no luck. Besides the outbound NAT entry provided, is there a setting somewhere else that needs to be set?

                1 Reply Last reply Reply Quote 0
                • S
                  sullrich
                  last edited by

                  That should be it, the rule matches what was said in the forum.

                  Make sure you change 10.0.250.69 to your private ip of your workstation.

                  Also restart Hamachi.

                  1 Reply Last reply Reply Quote 0
                  • B
                    billm
                    last edited by

                    Also, depending on the speed of your machine, it could take a couple seconds to actually update the rules.  We give the user back control and spawn off a process to create rules in the background.  This can take some time depending on shaper rules and speed of machine.

                    –Bill

                    pfSense core developer
                    blog - http://www.ucsecurity.com/
                    twitter - billmarquette

                    1 Reply Last reply Reply Quote 0
                    • M
                      MikaelS
                      last edited by

                      I have also encountered  this problem  :-\

                      I have done the advanced outbound nat rule as Sullrich did it (only changed IP to 192.168.0.2).

                      Hamachi have been configured with the magic option port 12975.

                      No extra portforwards or firewall rules an im on BETA 1

                      My states show med (192.168.0.2 is the computer with hamachi and 81.XX.134.139 is my public ip at the moment):

                      self tcp 64.34.106.33:12975 <- 192.168.0.2:3308                                             FIN_WAIT_2:FIN_WAIT_2
                      self tcp 64.34.106.33:12975 <- 192.168.0.2:3309                                             ESTABLISHED:ESTABLISHED
                      self tcp 192.168.0.2:3309 -> 81.XX.134.139:61521 -> 64.34.106.33:12975        ESTABLISHED:ESTABLISHED
                      self tcp 192.168.0.2:3308 -> 81.XX.134.139:60332 -> 64.34.106.33:12975        FIN_WAIT_2:FIN_WAIT_2
                      self udp 64.34.106.33:43961 <- 192.168.0.2:12975                                           NO_TRAFFIC:SINGLE
                      self udp 64.34.106.33:11711 <- 192.168.0.2:12975                                           NO_TRAFFIC:SINGLE
                      self udp 64.34.106.74:3713 <- 192.168.0.2:12975                                             NO_TRAFFIC:SINGLE
                      self udp 82.165.226.212:3892 <- 192.168.0.2:12975                                         NO_TRAFFIC:SINGLE
                      self udp 192.168.0.2:12975 -> 81.XX.134.139:57157 -> 64.34.106.33:43961      SINGLE:NO_TRAFFIC
                      self udp 192.168.0.2:12975 -> 81.XX.134.139:50945 -> 64.34.106.33:11711      SINGLE:NO_TRAFFIC
                      self udp 192.168.0.2:12975 -> 81.XX.134.139:64298 -> 64.34.106.74:3713        SINGLE:NO_TRAFFIC
                      self udp 192.168.0.2:12975 -> 81.XX.134.139:60112 -> 82.165.226.212:3892    SINGLE:NO_TRAFFIC

                      1 Reply Last reply Reply Quote 0
                      • B
                        billm
                        last edited by

                        @MikaelS:

                        I have also encountered  this problem  :-\

                        I have done the advanced outbound nat rule as Sullrich did it (only changed IP to 192.168.0.2).

                        Hamachi have been configured with the magic option port 12975.

                        No extra portforwards or firewall rules an im on BETA 1

                        My states show med (192.168.0.2 is the computer with hamachi and 81.XX.134.139 is my public ip at the moment):

                        self tcp 64.34.106.33:12975 <- 192.168.0.2:3308                                            FIN_WAIT_2:FIN_WAIT_2
                        self tcp 64.34.106.33:12975 <- 192.168.0.2:3309                                            ESTABLISHED:ESTABLISHED
                        self tcp 192.168.0.2:3309 -> 81.XX.134.139:61521 -> 64.34.106.33:12975        ESTABLISHED:ESTABLISHED
                        self tcp 192.168.0.2:3308 -> 81.XX.134.139:60332 -> 64.34.106.33:12975        FIN_WAIT_2:FIN_WAIT_2
                        self udp 64.34.106.33:43961 <- 192.168.0.2:12975                                          NO_TRAFFIC:SINGLE
                        self udp 64.34.106.33:11711 <- 192.168.0.2:12975                                          NO_TRAFFIC:SINGLE
                        self udp 64.34.106.74:3713 <- 192.168.0.2:12975                                            NO_TRAFFIC:SINGLE
                        self udp 82.165.226.212:3892 <- 192.168.0.2:12975                                        NO_TRAFFIC:SINGLE
                        self udp 192.168.0.2:12975 -> 81.XX.134.139:57157 -> 64.34.106.33:43961      SINGLE:NO_TRAFFIC
                        self udp 192.168.0.2:12975 -> 81.XX.134.139:50945 -> 64.34.106.33:11711      SINGLE:NO_TRAFFIC
                        self udp 192.168.0.2:12975 -> 81.XX.134.139:64298 -> 64.34.106.74:3713        SINGLE:NO_TRAFFIC
                        self udp 192.168.0.2:12975 -> 81.XX.134.139:60112 -> 82.165.226.212:3892    SINGLE:NO_TRAFFIC

                        Hmmm, that certainly looks like the NAT isn't working right.  I'll take a look.

                        –Bill

                        pfSense core developer
                        blog - http://www.ucsecurity.com/
                        twitter - billmarquette

                        1 Reply Last reply Reply Quote 0
                        • B
                          billm
                          last edited by

                          Uhhh, NAT rules are like filter rules, first match.  I'm betting you have the default NAT from LAN to WAN rule first.  Please re-order them.

                          –Bill

                          pfSense core developer
                          blog - http://www.ucsecurity.com/
                          twitter - billmarquette

                          1 Reply Last reply Reply Quote 0
                          • M
                            MikaelS
                            last edited by

                            Yes you where right about the order of the rules, this is now fixed but still no luck  :'(

                            I reseted my states and tested a couple of times but no luck.
                            The only thing i have done is magic option in hamachi (12975) and the advanced outbound nat.
                            This is correct?

                            My states:

                            self tcp 64.34.106.33:12975 <- 192.168.0.2:1328                                            ESTABLISHED:ESTABLISHED
                            self tcp 192.168.0.2:1328 -> 81.XX.134.139:57915 -> 64.34.106.33:12975       ESTABLISHED:ESTABLISHED
                            self udp 64.34.106.33:43961 <- 192.168.0.2:12975                                          NO_TRAFFIC:SINGLE
                            self udp 64.34.106.33:11711 <- 192.168.0.2:12975                                          NO_TRAFFIC:SINGLE
                            self udp 64.34.106.74:3713 <- 192.168.0.2:12975                                            NO_TRAFFIC:SINGLE
                            self udp 82.165.226.212:3892 <- 192.168.0.2:12975                                         NO_TRAFFIC:SINGLE
                            self udp 192.168.0.2:12975 -> 81.XX.134.139:57234 -> 64.34.106.33:43961      SINGLE:NO_TRAFFIC
                            self udp 192.168.0.2:12975 -> 81.XX.134.139:59478 -> 64.34.106.33:11711      SINGLE:NO_TRAFFIC
                            self udp 192.168.0.2:12975 -> 81.XX.134.139:61194 -> 64.34.106.74:3713        SINGLE:NO_TRAFFIC
                            self udp 192.168.0.2:12975 -> 81.XX.134.139:51526 -> 82.165.226.212:3892    SINGLE:NO_TRAFFIC

                            1 Reply Last reply Reply Quote 0
                            • C
                              CrashX
                              last edited by

                              I too only have the Advanced Outbound NAT set up and the Magic Option in Hamachi set. I have the Hamachi outbound rule above the the default rule and still have the same results.

                              self  tcp  192.168.10.50:1400  ->  66.93.XXX.XXX:59271  ->  64.34.106.33:12975    ESTABLISHED:ESTABLISHED
                              self  tcp  64.34.106.33:12975  <-  192.168.10.50:1400        ESTABLISHED:ESTABLISHED

                              1 Reply Last reply Reply Quote 0
                              • S
                                sullrich
                                last edited by

                                Isn't hamachi using UDP?  Perhaps my screenshot was wrong in this regard.  Please remove nat+firewall rules and start over but use UDP.

                                Scott

                                1 Reply Last reply Reply Quote 0
                                • C
                                  CrashX
                                  last edited by

                                  I don't see that Outbound Nat let's you choose between UDP and TCP.

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    sullrich
                                    last edited by

                                    Well then verify the outbound rule is the first in the list before all other rules.

                                    1 Reply Last reply Reply Quote 0
                                    • M
                                      MikaelS
                                      last edited by

                                      @sullrich:

                                      Well then verify the outbound rule is the first in the list before all other rules.

                                      Thats what i have done (hamachi NAT rule is at top).
                                      But it isent working.
                                      No Firewall rules needed?? or anything else?

                                      Happy new year to all!

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        sullrich
                                        last edited by

                                        Okay, time to install this beast.

                                        Can you tell me how we can get a tunnel connected for testing?

                                        1 Reply Last reply Reply Quote 0
                                        • C
                                          CrashX
                                          last edited by

                                          I created one for testing.

                                          Network name: pfsense
                                          Password: pfsense

                                          1 Reply Last reply Reply Quote 0
                                          • C
                                            CrashX
                                            last edited by

                                            It should turn green if the connection is good. Yellow if there is a problem.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post