Fix firewall soft-lock when not resolving the domain
Problem
Well, basically huronOS can soft-lock itself due to the order in which the operations of hsync perform. What happens is the following: If the huronOS does not have internet at the moment of resolving the IP of the domain for the directives URL, and the mode it is changing to is 'Contest', the firewall will keep the IP of the directives URL blocked (because it doesn't know which IP to open). When internet is stablished it will resolve the IP of the directives, but only if the date has changed it's status to sync it will re-apply the directives, including the firewall. If the clock is somehow in sync and connection to internet is stablished, the firewall will not be updated and the directivs wont be able to be sync.
Solution
A possible solution to this, would be to take a step before downloading the directives file to ensure that the exception to that IP is present. This will allow that as soon as there's internet, the firewall is updated with the new exception, and the it tries to update the directives file.