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

    [Resolved] IPv6 packet loss

    2.2 Snapshot Feedback and Problems - RETIRED
    3
    6
    2.5k
    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.
    • E
      eskild
      last edited by

      2.2-RC (i386)
      built on Fri Jan 02 14:57:04 CST 2015

      After upgrading to latest snapshot, the system wrongly assumes that ip addresses are constantly changing:

      Jan 3 09:41:08 php-fpm[76625]: /rc.newipsecdns: IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
      Jan 3 09:40:53 php-fpm[89750]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN6_TUNNELV6.
      Jan 3 09:40:52 check_reload_status: Reloading filter
      Jan 3 09:40:52 check_reload_status: Restarting OpenVPN tunnels/interfaces
      Jan 3 09:40:52 check_reload_status: Restarting ipsec tunnels
      Jan 3 09:40:52 check_reload_status: updating dyndns WAN6_TUNNELV6
      Jan 3 09:36:40 php-fpm[7668]: /rc.newipsecdns: IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
      Jan 3 09:36:25 php-fpm[21353]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN6_TUNNELV6.
      Jan 3 09:36:24 check_reload_status: Reloading filter
      Jan 3 09:36:24 check_reload_status: Restarting OpenVPN tunnels/interfaces
      Jan 3 09:36:24 check_reload_status: Restarting ipsec tunnels
      Jan 3 09:36:24 check_reload_status: updating dyndns WAN6_TUNNELV6
      Jan 3 09:34:47 php-fpm[94842]: /rc.newipsecdns: IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
      Jan 3 09:34:32 php-fpm[8971]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN6_TUNNELV6.
      Jan 3 09:34:31 check_reload_status: Reloading filter
      Jan 3 09:34:31 check_reload_status: Restarting OpenVPN tunnels/interfaces
      Jan 3 09:34:31 check_reload_status: Restarting ipsec tunnels
      Jan 3 09:34:31 check_reload_status: updating dyndns WAN6_TUNNELV6
      Jan 3 09:33:15 php-fpm[2665]: /rc.newipsecdns: IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
      Jan 3 09:33:00 php-fpm[41723]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN6_TUNNELV6.
      Jan 3 09:32:59 check_reload_status: Reloading filter

      1 Reply Last reply Reply Quote 0
      • E
        eskild
        last edited by

        Rolled back to:

        2.2-RC (i386)
        built on Sun Dec 28 04:40:24 CST 2014

        but the issue is still present.

        1 Reply Last reply Reply Quote 0
        • JeGrJ
          JeGr LAYER 8 Moderator
          last edited by

          Probably a gateway failure detected? Did you check the routing/gateway log if apinger detects your gateway as down?

          Don't forget to upvote 👍 those who kindly offered their time and brainpower to help you!

          If you're interested, I'm available to discuss details of German-speaking paid support (for companies) if needed.

          1 Reply Last reply Reply Quote 0
          • E
            eskild
            last edited by

            @JeGr:

            Probably a gateway failure detected? Did you check the routing/gateway log if apinger detects your gateway as down?

            Yes, the apinger wrongly detects gw down.
            The status is actually much better using the "Sun Dec 28 04:40:24 CST 2014" snapshot. No apinger alarms for several hours.

            Gw log from "Fri Jan 02 14:57:04 CST 2015" snapshot:

            Jan 3 10:37:54 apinger: alarm canceled: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 10:36:12 apinger: ALARM: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 10:35:12 apinger: alarm canceled: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 10:31:05 apinger: ALARM: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 10:28:59 apinger: alarm canceled: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 10:27:50 apinger: ALARM: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 10:09:03 apinger: alarm canceled: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 10:04:30 apinger: Starting Alarm Pinger, apinger(35311)
            Jan 3 10:02:12 apinger: ALARM: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 09:58:09 apinger: alarm canceled: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 09:57:39 apinger: ALARM: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 09:48:52 apinger: alarm canceled: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 09:47:34 apinger: ALARM: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 09:44:59 apinger: alarm canceled: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 09:42:21 apinger: ALARM: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 09:41:27 apinger: alarm canceled: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 09:40:42 apinger: ALARM: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 09:36:14 apinger: alarm canceled: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 09:34:21 apinger: ALARM: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 09:32:49 apinger: alarm canceled: WAN6_TUNNELV6(2001:470:27:722::1) *** loss ***
            Jan 3 09:24:06 apinger: Starting Alarm Pinger, apinger(36510)

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

              @eskild:

              Yes, the apinger wrongly detects gw down.

              Wrongly? Really?  :o

              1 Reply Last reply Reply Quote 0
              • E
                eskild
                last edited by

                Hmm, I've been testing some more with the "Fri Jan 02 14:57:04 CST 2015" build, and I have not seen the same issues as I did previously today. Must have been a wierd coincidence where "tunnelbroker.net" experienced issues at the same time as I upgraded the FW. I have never exerienced having issues with "tunnelbroker.net" before.

                Anyway, everything seems fine now.

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