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

System logs referencing old gateway

Scheduled Pinned Locked Moved Routing and Multi WAN
7 Posts 3 Posters 483 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.
  • S
    srbol
    last edited by Sep 18, 2024, 10:23 PM

    I'm new to pfsense and trying to address system logs that that reference an old gateway "ProtonVPN2."

    For example:

    Sep 18 15:55:25 php-fpm 41885 /rc.newwanip: The gateway: ProtonVPN2 is invalid or unknown, not using it.

    and

    Sep 18 15:55:23 php-fpm 91812 /rc.filter_configure_sync: The gateway: ProtonVPN2 is invalid or unknown, not using it.

    I deleted this gateway a month ago. I created it trying to setup a second VPN connection using WireGuard.

    I'm not exactly sure what these errors mean or how to address them.

    I found this thread that I think is related: https://forum.netgate.com/topic/187125/old-gw-still-referenced-in-logs

    I was not successful in using the command prompt. I also do not know how to edit a configuration file.

    Any help would be greatly appreciated. Thanks in advance for your patience.

    1 Reply Last reply Reply Quote 0
    • J
      JonathanLee
      last edited by Sep 19, 2024, 1:04 AM

      Do you have an ACL or alias for it still?

      Make sure to upvote

      S 1 Reply Last reply Sep 19, 2024, 9:18 AM Reply Quote 0
      • S
        srbol @JonathanLee
        last edited by Sep 19, 2024, 9:18 AM

        @JonathanLee

        Thank you for your quick response!

        I do not think I have any alias that references ProtonVPN2.

        However, I looked through my firewall rules and found this:

        Screenshot 2024-09-19 at 5.13.12 AM.png

        Is the last rule the potential ACL you're referring to?

        Should I disable or delete the last rule?

        S 1 Reply Last reply Sep 19, 2024, 2:16 PM Reply Quote 0
        • S
          SteveITS Rebel Alliance @srbol
          last edited by Sep 19, 2024, 2:16 PM

          @srbol Note how "ProtonVPN2" is not a link? That's because pfSense knows it is invalid. Yes you can disable or delete that rule. That should bypass the error, unless there's another.

          Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
          When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
          Upvote 👍 helpful posts!

          S 1 Reply Last reply Sep 20, 2024, 12:24 AM Reply Quote 0
          • S
            srbol @SteveITS
            last edited by Sep 20, 2024, 12:24 AM

            @SteveITS Thank you for pointing out that "ProtonVPN2" is not a link. That makes complete sense now.

            Earlier today, following your advice, I deleted the rule altogether. The rule was left over from my (failed) attempt to setup a second WireGuard VPN over a month ago.

            So far, I have seen no further errors noted in my system logs. I will continue to check over the next day or two and let you know if I see anything.

            Sincerely appreciate your willingness to help a noob like me.

            S 1 Reply Last reply Sep 20, 2024, 12:30 AM Reply Quote 1
            • S
              SteveITS Rebel Alliance @srbol
              last edited by Sep 20, 2024, 12:30 AM

              @srbol said in System logs referencing old gateway:

              Thank you for pointing out that "ProtonVPN2" is not a link. That makes complete sense now.

              It does, in hindsight. :) Otherwise it's subtle. You're welcome, help someone else someday. :)

              Similar can trigger for, say, pfBlocker-created aliases, if the alias isn't created yet/doesn't load.

              Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
              When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
              Upvote 👍 helpful posts!

              S 1 Reply Last reply Sep 21, 2024, 12:59 AM Reply Quote 1
              • S
                srbol @SteveITS
                last edited by Sep 21, 2024, 12:59 AM

                @SteveITS Final update. The issue definitely seems resolved. Thanks again.

                1 Reply Last reply Reply Quote 1
                7 out of 7
                • First post
                  7/7
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                  This community forum collects and processes your personal information.
                  consent.not_received