FRR package 1.1.1_7 on Pfsense 2.6.0 has got Prefix-lists update issues

[ErsanY]

pfsense version: 2.6.0
FRR pfsense package version: 1.1.1_7
Package Dependencies: frr7-pythontools-7.5.1_3  frr7-7.5.1_3

SUMMARY: What we configure on PfSense GUI FRR prefix-list section, is not being saved into the raw config file, into the actual FRR file. (I clicked on the "save" button everywhere) (Rebooting my pfsenses, or moving the traffic to Backup pfsense didn't help.)

DETAILS:
Hi. We have got 2 pairs (A and B) of pfsenses. Each pair works as master/backup.
We use FRR to configure BGP. We use prefix-lists to control received and advertised BGP prefixes.

After upgrading both of the pfsenses to the latest version on pair A, we have realised that not all of the prefixes are received into pfsense route table. I checked the prefix-list, yes the prefixes missing at the route table are indeed configured at the inbound prefix-list at GUI.

I checked the Raw Config on GUI, I saw that some of the prefix-list entries are missing there. I have then connected to FRR via CLI, I said "show ip prefix-list". What I see is that we are missing the last prefix-list sequences there.

We increment the sequence numbers by 5. So the sequence numbers are 5, 10, 15, 20, 25 etc. Normally we are at sequence number 80 on pfsense FRR GUI. But on Raw-Config and on FRR Cli, it shows only up to sequence 50.

Is this a new bug for the latest version?

We have got pair B with the following versions and we don't have any of these problems:
pfsense version: 2.5.2
FRR pfsense package version: 1.1.0_15
Package Dependencies: frr7-pythontools-7.5.1_3  frr7-7.5.1_3

I thought of creating a topic in here before registering this issue at pfsense bugtracker.

[Zawi]

@ersany
if you are using Raw-Config to add commands Gui will not be able to control the configuration .

you need to delete Raw-Config and add the configuration via GUI only.

[Derelict]

@ersany If you wish to look at the FRR config file when using the GUI to configure it (not raw config), Go to Status > FRR, Configuration.

As explained above, using the raw configuration disables the GUI config. You have assumed responsibility for the FRR configuration in that case and changes must be made to the raw configuration instead.