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

    Ipv6 *.pfsense.org is down

    Scheduled Pinned Locked Moved Forum Feedback
    12 Posts 4 Posters 2.8k 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.
    • C
      Cino
      last edited by

      its also been reported in the package board

      https://forum.pfsense.org/index.php?topic=75265.msg421979#msg421979

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

        Huh problem again.
        I cannot reach *.pfsense.com or *.pfsense.org via IPv6 link…

        What`s up :) ?

        1 Reply Last reply Reply Quote 0
        • jdillardJ
          jdillard
          last edited by

          should be fixed now  :D

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

            Yes it is.
            Thank you.

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

              and down again  ::)

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                100% IPv6 #fail.

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

                  yup but it`s different trouble from last time…
                  now they have nice little loop :)

                  14  148 ms  148 ms  148 ms  2001:438:ffff::407d:20ca
                  15  149 ms  149 ms  149 ms  2610:160:11::4
                  16  149 ms  148 ms  148 ms  2610:160:11::1
                  17  149 ms  149 ms  149 ms  2610:160:11::4
                  18  148 ms  148 ms  148 ms  2610:160:11::1
                  19  150 ms  149 ms  149 ms  2610:160:11::4
                  20    *        *        *    Request timed out.
                  21  149 ms  149 ms  150 ms  2610:160:11::4
                  22    *      149 ms  149 ms  2610:160:11::1
                  23  150 ms  150 ms  149 ms  2610:160:11::4
                  24  149 ms  149 ms    *    2610:160:11::1
                  25  150 ms  149 ms  149 ms  2610:160:11::4

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

                    Sure looks like it… this is really getting old... Can you please setup IPv4 failover if IPv6 is unreachable in pfsense? Maybe create a ipv4.files.pfsense.org DNS entry that only routes to the IPv4 address. This way we can manually add it to pkg_mgr_settings.php when needed.

                    I'd be yelling at the ISP right now

                    
 Traceroute output:

 1  2604:2000:450:b0::1  10.578 ms  31.438 ms  16.876 ms
 2  2604:2000:0:4::c243  12.400 ms  9.563 ms  12.615 ms
 3  2604:2000:0:4::2a82  17.296 ms  12.923 ms  11.938 ms
 4  2001:1998:0:8::aa  16.033 ms  13.666 ms  16.109 ms
 5  2001:1998:0:4::102  14.547 ms  14.524 ms
    ge-11-1-0.pr0.dca20.tbone.rr.com  12.971 ms
 6  2001:1998:0:8::2b6  14.972 ms  18.031 ms  13.079 ms
 7  ae4.er2.lga5.us.above.net  15.251 ms  16.761 ms  19.422 ms
 8  xe-0-3-0.cr2.lga5.us.above.net  12.805 ms  14.262 ms  17.043 ms
 9  ae4.cr2.dca2.us.above.net  26.451 ms  20.806 ms  21.624 ms
10  ae14.cr2.iah1.us.above.net  73.008 ms  63.215 ms  56.214 ms
11  ae2.cr2.dfw2.us.above.net  57.900 ms  63.289 ms  62.745 ms
12  ae7.er2.dfw2.us.above.net  61.500 ms  62.023 ms  61.219 ms
13  2001:438:ffff::407d:20ca  65.547 ms  63.151 ms  67.750 ms
14  2610:160:11::4  68.036 ms  64.903 ms  64.069 ms
15  2610:160:11::1  60.320 ms  63.522 ms  62.102 ms
16  2610:160:11::4  66.893 ms  59.873 ms  63.148 ms
17  2610:160:11::1  63.486 ms  61.748 ms  62.151 ms
18  2610:160:11::4  67.382 ms  64.710 ms  66.959 ms


                    
Pinging files.pfsense.org [2610:160:11:11::81] with 32 bytes of data:
Reply from 2610:160:11:11::81: TTL expired in transit.
Reply from 2610:160:11:11::81: TTL expired in transit.
Reply from 2610:160:11:11::81: TTL expired in transit.
                    1 Reply Last reply Reply Quote 0
                    • M
                      maverick_slo
                      last edited by

                      seems like one of the routers lost BGP partner :)

                      1 Reply Last reply Reply Quote 0
                      • DerelictD
                        Derelict LAYER 8 Netgate
                        last edited by

                        Still having issues with IPv6, lest anyone think it's fixed.

                        Chattanooga, Tennessee, USA
                        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                        Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

                          fixed :)

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