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

    VPN established but no traffic through the tunnel

    2.0-RC Snapshot Feedback and Problems - RETIRED
    7
    25
    11.8k
    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

      From a shell or SSH session ( option 8 ) or from Diagnostics -> Command -> Shell command

      1 Reply Last reply Reply Quote 0
      • E
        eri--
        last edited by

        upgrade to latest snapshot.

        1 Reply Last reply Reply Quote 0
        • J
          jzsjr
          last edited by

          Okay.  I wasn't sure if it was a command or located in sysctl.conf (but there is nothing really in that file).

          thanks,
          Jim

          1 Reply Last reply Reply Quote 0
          • J
            jzsjr
            last edited by

            Thanks Sullrich.  Those commands did the trick.

            Ermal, not sure what is up with the auto updater now but this is what I get:

            Auto upgrade aborted.

            Downloaded SHA256:

            Needed SHA256: bad9308e0d492d9701e60766cf747777024b005cdad4819bba193fa8d7a6dfa8

            Also I don't know where the 2.0 files are now for a manual upgrade.  When I go to the old listing under _1 I see 1.2.1 files.

            thanks,
            Jim

            1 Reply Last reply Reply Quote 0
            • E
              eri--
              last edited by

              Those 1.2.1 files should be the 2.0 updates not sure why they are called 1.2.1!

              1 Reply Last reply Reply Quote 0
              • J
                jzsjr
                last edited by

                Sullrich & Ermal,

                Latest snapshot shows:

                $ sysctl net.enc
                net.enc.out.ipsec_bpf_mask: 0000000000
                net.enc.out.ipsec_filter_mask: 0x00000002
                net.enc.in.ipsec_bpf_mask: 0000000000
                net.enc.in.ipsec_filter_mask: 0x00000001

                Should they show what Sullrich suggested earlier in this thread?
                thanks,
                Jim

                1 Reply Last reply Reply Quote 0
                • E
                  eri--
                  last edited by

                  To me it is just those not set are considered debugging options, tcpdump in enc0. So while debugging makes sense you enable those otherwise it is just 'overhead'.
                  Since 2.0 allows you to set such values from the gui i consider them unnecessary.

                  1 Reply Last reply Reply Quote 0
                  • J
                    jzsjr
                    last edited by

                    I am using:
                    2.0-ALPHA-ALPHA
                    built on Fri Apr 3 21:18:02 EDT 2009
                    FreeBSD 7.1-RELEASE-p4

                    and still afflicted with the vpn tunnel staying up but no data passing.  There was a fix provided by Sullrich earlier in this thread and I hope still works though I'm not real sure what it does.  This is happening to a colleague of mine too.  We have used both the full install on a server base and the embedded install with the same results.  The vpn will work wonderfully for hours and then just stop passing data.  I have gotten to the point where I merely reboot the racoon service now.  I have recently updated so I'll apply the commands below and see how they go again.  I was hoping someone could explain what these commands accomplish and why they might not be permanently changed in a release.

                    sysctl net.enc.out.ipsec_bpf_mask=0x00000002
                    sysctl net.enc.out.ipsec_filter_mask=0x00000002
                    sysctl net.enc.in.ipsec_bpf_mask=0x00000001
                    sysctl net.enc.in.ipsec_filter_mask=0x00000001

                    thanks,
                    Jim

                    1 Reply Last reply Reply Quote 0
                    • A
                      Accounts
                      last edited by

                      is this still going on in current snapshots? I wanted to update to check NAT redirection but fear ipsec problems since all is good as of my current march 22 build with ipsec.

                      1 Reply Last reply Reply Quote 0
                      • J
                        jzsjr
                        last edited by

                        yes.  I posted the current release I am using.

                        Jim

                        1 Reply Last reply Reply Quote 0
                        • J
                          jzsjr
                          last edited by

                          I just had an RDP session and outlook connected to an exchange server data stop.  The tunnel was still showing open.  Is there any logs I can send in?

                          thanks,
                          Jim

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