Added addrgrp cannot found when creating policy...

[wcbenyip]

Hi, I am now working on the FG310B, and try to setting up the policy manually from the conf file of my old FG box. I found that even I add the address group via the GUI or cmd line, the addrgrp is out there without any error when adding the addresses, but finally it always will say: # set srcaddr " Permitted servers for Site_A" entry not found in datasource value parse error before ' Permitted servers for Site_A' Command fail. Return code -3 I think it may be affected by the belong interface of the address inside the group, so I changed every address entry fr. specified interface to ' any' , however, the same error still exist... In the firewall policy, I have the other similar entries which work properly... Anyone can help or have any insight? I thought it maybe the FG bug again.... I am waiting for the suitable moment to reboot the device....

[ede_pfau]

So, what is your FortiOS version? FYI, mine is 4.2.12, and this works:

     config firewall policy
    edit 42
         set srcintf " internal" 
         set dstintf " dmz" 
             set srcaddr " A and B"              
             set dstaddr " Permitted servers for Site_A"              
         set schedule " always" 
             set service " ANY"              
     next
 

The only feature that doesn' t work is the command line completion via TAB. TAB will always stop before the first blank in the object name. But I could enter the address group name manually without any error.

[wcbenyip]

The firmware is 4.0 MR3 Patch 10 (build0639), the latest version. In my case, I tried to type the cmd lines manually (not copy & paste), and also didn' t used tab instead of space. Just don' t know why it' s not working! ################################# After the most magic step - Rebooting, I can now add the addrgrp to the box via cmd line~ Haiz, seems reboot can fix any unknown and unexpected issues...

[RH2]

Get rid of the spaces in your addresses!!!! They will cause you nothing but problems. We had several that we could not delete or edit because of the blanks in their names. We also had random errors when trying to apply changes from the manager. Once we renamed all objects to remove spaces we have had much fewer issues.

[Dave_Hall]

Just a heads up, too regarding spaces. We were upgrading from MR2 to MR3 and ran into this problem. We had to change all the space chars to underscores in the address labels.