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

    Services->RIP is showing PHP error after upgrade to 2.2.4

    Scheduled Pinned Locked Moved pfSense Packages
    10 Posts 2 Posters 1.5k 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
      AlexF
      last edited by

      I had RIP package configured and working.

      I upgraded from 2.2 to 2.2.4.

      Now, Web GUI's Services -> RIP is showing:
        Warning: Invalid argument supplied for foreach() in /usr/local/www/pkg_edit.php on line 447
      and I cannot configure RIP.

      Help?
      pkg_edit.php.txt

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

        Post the output of this from Diagnostics - Command Prompt

        
        print_r($config['installedpackages']['routed']['config']);
        
        
        1 Reply Last reply Reply Quote 0
        • A
          AlexF
          last edited by

          @doktornotor:

          Post the output of this from Diagnostics - Command Prompt

          Here it is:```

          Array
          (
              [0] => Array
                  (
                      [enable] => on
                      [iface_array] => opt1,opt2
                      [ripversion] => 2
                      [passwd] =>
                      [enable_no_ag] => on
                      [enable_no_super_ag] => on
                  )

          )

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

            Reinstall the package and see if it helps?

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

              I've attempted previous firmare downgrades - 2.2 OK, 2.2.1 OK, 2.2.2 OK, 2.2.3 fault, 2.2.4 fault.

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

                What's "fault" ? Are you getting some error somewhere, actually? (No, the foreach warning coming from god knows where is not an error.)

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

                  @doktornotor:

                  What's "fault" ? Are you getting some error somewhere, actually?

                  Yes, as per above:@AlexF:

                  I cannot configure RIP.

                  and I see no RIP advertisements from pfSense (per configuration before the upgrade).

                  @doktornotor:

                  .. the foreach warning coming from god knows where ..

                  as per above:@AlexF:

                  Services -> RIP

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

                    I mean some errors somewhere. Console. System log. "I cannot configure RIP" is not useful, really. Also, I have hard time figuring out how you cannot configure it when you start another thread suggesting the exact opposite, and in fact, it clearly IS configured. ::)

                    @AlexF:

                    I have set up RIP on two connected devices - Pfsense and F5-VE (virtual F5 BIG-IP load-balancer).

                    PFsense redistributes connected routes into RIP.

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

                      @doktornotor:

                      Also, I have hard time figuring out how you cannot configure it when you start another thread suggesting the exact opposite  ::)

                      I downgraded to 2.2 and now 2.2.2 - as stated above, both is ok.

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

                        As shown above, "cannot configure" is just plain false statement. It's configured perfectly fine. Sigh… Doesn't go anywhere, good luck.

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