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

    Gateway v6 status is Unknown

    Scheduled Pinned Locked Moved 2.3-RC Snapshot Feedback and Issues - ARCHIVED
    5 Posts 4 Posters 1.6k 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.
    • Raul RamosR
      Raul Ramos
      last edited by

      Hi

      After update to built on Fri Dec 18 22:48:37 CST 2015  (amd64) in Hyper-V environment - My gateway state is unknown for Hurricane electric tunnel although IPv6 is working fine. dpinger packet was updated in the process.

      Edited: Is better be precise. Status is Unknown, RTT and Loss is pending.

      Thanks

      pfSense:
      ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
      Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
      NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

      1 Reply Last reply Reply Quote 0
      • luckman212L
        luckman212 LAYER 8
        last edited by

        I had a similar problem in 2.2.5. Try setting an alternate monitor IP on your default IPv6 gateway e.g. one of these public Google DNS servers:

        2001:4860:4860::8888
        2001:4860:4860::8844

        1 Reply Last reply Reply Quote 0
        • Raul RamosR
          Raul Ramos
          last edited by

          Thanks for reply

          Change the monitor IP doesn't change status and de IP at least in the widget. Restart dpinger, same result. I can ping6 gateway IP and DNS v6 IP.

          Little of topic but related. If i do not check Use non-local gateway i have the error "The following input errors were detected:
          The gateway address 2001:470::::1 does not lie within one of the chosen interface's subnets." but it does, triple check it.

          pfSense:
          ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
          Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
          NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

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

            You're not supposed to be able to edit the IP of a dynamic gateway. Since you're triggering that input validation, you did so at some point. Under System>Routing, delete the HE gateway that you have there. Doing so will bring back the proper default dynamic gateway.
            https://redmine.pfsense.org/issues/5694

            The fact the status is unknown is a separate issue I'm looking into now. It's not running a dpinger instance in that case for some reason.

            1 Reply Last reply Reply Quote 0
            • J
              jwt Netgate
              last edited by

              We understand "why" now, and will develop a fix.

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