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

    Could not find IPv6 gateway - but we're not using IPv6

    Scheduled Pinned Locked Moved General pfSense Questions
    11 Posts 3 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.
    • A
      a_null
      last edited by

      version 2.2.3-RELEASE (i386), not running IPv6. Our logs are full of:
      php: rc.filter_configure_sync: Could not find IPv6 gateway for interface (wan).
      and
      php: rc.filter_configure_sync: Could not find IPv6 gateway for interface (opt1).

      Both interfaces comprise a dual-wan with wan-to-opt1 failover set up.

      I found some references to scheduling as the trigger for this, and we are using schedules, but again - not ipv6. BUT - I have also noticed that pfBlockerNG has created ipv6 rules. If I delete these pfb rules individually, will pfblockerNG re-create them? Is that even a possible cause of these log entries over and over?

      \x0

      1 Reply Last reply Reply Quote 0
      • KOMK
        KOM
        last edited by

        Do you actually have IPv6 disabled in System - Advanced - Networking - IPv6 Options - Allow IPv6?

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

          Yep.

          \x0

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

            Also, if I delete the v6 pfblockerNG rules in Firewall/Rules, they are, in fact, re-created. So that's not an option.

            \x0

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

              I went through the pfblockerNG tabs and cleared the ipv6 lists, and that removed all the v6 entries from the firewall rules. I'll let you know how that pans out.

              \x0

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

                It's early yet, but clearing the IPv6 lists from each pfblockerNG tab seems to have corrected it. As a note, clicking on an entry will unselect all but that one entry, and ctrl-click will unselect that entry.

                \x0

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

                  Useless log noise. Ignore. Known bug.

                  P.S. The "disable" checkbox disables nothing. It blocks all IPv6 traffic. Even written there.

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

                    @doktornotor:

                    Useless log noise. Ignore. Known bug.

                    P.S. The "disable" checkbox disables nothing. It blocks all IPv6 traffic. Even written there.

                    The problem with noise is that it makes the signals harder to find - I had an entire screen of nothing but that message.
                    I know it's not some earth-shattering issue, but I had time today to look at it, and I wanted to see if I could alleviate it. I did. Also did the "save" thing on my interfaces to get rid of the "radvd: sendmsg" messages.
                    I like it when I can get to a "C" or a "D" item every now and again.

                    \x0

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

                      Yeah. There's some noise. There's a bug about it. What more you want here? You have the PHP code. Go fix it yourself if you cannot wait.

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

                        @doktornotor:

                        Yeah. There's some noise. There's a bug about it. What more you want here? You have the PHP code. Go fix it yourself if you cannot wait.

                        Dude - if I somehow lent the impression that I was jumping in your Wheaties because I was having some petty log noise, I apologize, but frankly, I don't think I did. I certainly WAS NOT  intentionally attacking you.

                        I posted my issue, I posted that I cleared it up, and I posted what I did to clear it. I do not know why you're doling out this much attitude.

                        \x0

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

                          https://github.com/pfsense/pfsense/pull/1832

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