Done some further research about rt_netlink and charon relationship. As described in the docs of Strongswan the option charon.process_route = no helps and is a good workaround if the destination is always reachable over a known specific interface (i think it can be an issue if wan load-balancing etc. is used).

There was some effort to introduce profiling into the system before, but nothing was developed.
The ticket was opened to verify that the timing values displayed in /var/log/vyatta are correct.
The vyos-debug flag enables tracing for actions described in the templates.
This will be a step-by-step walkthrough of the system profiling, as I have found this to have a bunch of non-obvious technical nuances that might get you stuck.

https://github.com/vyos/vyatta-op/pull/55

I've tried with a new spoke and I can't seem to register using `reload-or-restart', although it resolved the lost connectivity issues the opennhrp process needs a full restart. however, if you restart opennhrp daemon it causes different issues and usually the spoke loses connection.

## hub

Thank you, team, for such a quick response to my request. I have not even had the chance to test it yet but trust that this will work perfectly. Again, many thanks!

PR: https://github.com/vyos/vyos-1x/pull/1306

I did this change as you mentioned and it worked, , example:

PR https://github.com/vyos/vyos-1x/pull/1305

@RyVolodya could you recheck it?

Try to replace option restart to reload-or-restart and re-configure from scratch, it may help.
https://github.com/vyos/vyos-1x/blob/363ecfa46cdb8402ea71637717863f01b09f428b/src/conf_mode/protocols_nhrp.py#L107

Hub basic setting :

Yes ,you need to reload the services and it works , here's an basic example with the current configuration :

It is not only for dhcp, any service can be affected to this
There are no many check when we remove interface

@fernando Does it work if you "reload" configuration?