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

[AlexF]

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

[doktornotor]

Post the output of this from Diagnostics - Command Prompt

print_r($config['installedpackages']['routed']['config']);

[AlexF]

@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
        )

)

[doktornotor]

Reinstall the package and see if it helps?

[AlexF]

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.

[doktornotor]

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

[AlexF]

@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

[doktornotor]

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.

[AlexF]

@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.

[doktornotor]

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