Minor HM-NG gotcha: Copying an existing user profile that has a firewall defined results in invalid config

  • 1
  • Question
  • Updated 3 years ago
  • (Edited)
Just in case anybody else happens to hit this while giving HM-NG a go...

While testing/prodding, I was encountering an issue with HM-NG where invalid configuration was being generated that would not apply cleanly to APs.

After attempting to apply a full configuration, I would get the following:

CLI command failed: ip-policy outIP1428760312083

This was initially puzzling... Looking at the what HM-NG was attempting to apply, the error was occurring because it was trying to define a firewall (ip-policy) with the same name twice - which will fail. It should only have done so once... So why had it ended up doing this?

Further digging showed that a firewall (ip-policy) presently gets internally linked/referenced when you use the Copy button to duplicate an existing user profile that has a firewall defined.

The intention is, I expect, that the copy button should be duplicating the firewall (ip-policy) 'behind the scenes' to create an entirely independent copy. Presently, it does not do so leaving things in an odd state when you use the function - breaking subsequent config generation.

Once realised, the issue is easily worked around by deleting the duplicated user profile and recreating it from scratch.

I'm pretty sure this will get fixed in a subsequent update making this perhaps esoteric issue soon moot. I just wanted to document it in the interim in case others encounter it in the early days of their HM-NG testing/deployment.


Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes

Posted 3 years ago

  • 1

There are no replies.