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

    Apinger only working on wan 8/6/13 64bit snapshot

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    54 Posts 14 Posters 19.5k 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.
    • A
      athurdent
      last edited by

      @grandrivers:

      on latest sbapshot
        2.1-RC1 (amd64)
      built on Sun Aug 18 19:11:51 EDT 2013
      FreeBSD 8.3-RELEASE-p9

      my ipv6 tunnel is wrong 0.3 ms instead of 70 ish it normally is

      was fine on the 16th snapshot

      Just upgraded to
      2.1-RC1 (i386)
      built on Thu Aug 22 23:23:02 EDT 2013
      FreeBSD 8.3-RELEASE-p10

      from Aug 1 snapshot.

      My IPv6 tunnel now shows 0.2ms instead of the usual 12-14ms.

      1 Reply Last reply Reply Quote 0
      • K
        kejianshi
        last edited by

        Sounds like whatever is being pinged, it ain’t your gateway…

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

          @kejianshi:

          Sounds like whatever is being pinged, it ain’t your gateway…

          Nice catch, you're right. It should ping out on gif0 but it's just pinging itself on lo0:

          tcpdump -nvvi lo0 icmp6
          tcpdump: listening on lo0, link-type NULL (BSD loopback), capture size 96 bytes
          09:14:14.703602 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 24) 2001:4dd0:xxxx:xxxx::2 > 2001:4dd0:xxxx:xxxx::2: [icmp6 sum ok] ICMP6, echo request, length 24, seq 26906
          09:14:14.703847 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 24) 2001:4dd0:xxxx:xxxx::2 > 2001:4dd0:xxxx:xxxx::2: [icmp6 sum ok] ICMP6, echo reply, length 24, seq 26906
          
          

          According to the config it should not:

          target "2001:4dd0:xxxx:xxxx::1" {
                  description "WAN_SixXS"
                  srcip "2001:4dd0:xxxx:xxxx::2"
                  alarms override "loss","delay","down";
                  rrd file "/var/db/rrd/WAN_SixXS-quality.rrd"
          }
          
          1 Reply Last reply Reply Quote 0
          • K
            kejianshi
            last edited by

            I'd say your follow-up was nicer than my guess - glad it panned out.
            Well - That makes perfect sense now.  :D
            I'd guess knowing that makes it easier for a dev to fix?

            1 Reply Last reply Reply Quote 0
            • D
              doktornotor Banned
              last edited by

              @athurdent:

              Nice catch, you're right. It should ping out on gif0 but it's just pinging itself on lo0:

              Hmmm, indeed… same here. No wonder it shows insane figures, LOL.

              https://redmine.pfsense.org/issues/3161

              1 Reply Last reply Reply Quote 0
              • jimpJ
                jimp Rebel Alliance Developer Netgate
                last edited by

                This should be fixed in the next snapshot (later tonight)

                Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                Need help fast? Netgate Global Support!

                Do not Chat/PM for help!

                1 Reply Last reply Reply Quote 0
                • D
                  doktornotor Banned
                  last edited by

                  Thanks, will test ASAP. :)

                  1 Reply Last reply Reply Quote 0
                  • K
                    kejianshi
                    last edited by

                    Oh - That will make lots of people happy maybe. :)

                    1 Reply Last reply Reply Quote 0
                    • N
                      NOYB
                      last edited by

                      lo0 interface numbers are faster.  Can you please change it back?

                      Appearances are everything.

                      1 Reply Last reply Reply Quote 0
                      • D
                        doktornotor Banned
                        last edited by

                        @jimp:

                        This should be fixed in the next snapshot (later tonight)

                        Fixed in  Aug 26 16:51:36 EDT 2013

                        1 Reply Last reply Reply Quote 0
                        • K
                          kejianshi
                          last edited by

                          So, is your internet nice and laggy again?  haha

                          1 Reply Last reply Reply Quote 0
                          • D
                            doktornotor Banned
                            last edited by

                            @kejianshi:

                            So, is your internet nice and laggy again?  haha

                            Ah yeah, about 3ms slower than localhost. I guess I'll switch back to the buggy one.  :D ;D

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