"
We had our primary internet service and while attempting to get a backup circuit activated and connected, I lost access to the Webgui from outside and inside the network. It it appears to have happened when I disabled the down WAN interface.
I was still able to get the network up and working with our new circuit after I completed the provider's circuit activation but still cannot gain access to the webgui.
I tried accessing the webgui from the new WAN2 interface (I had setup all the access rules before I realized that the circuit had not yet been activated)
The root password isn't working so I am going to have to wait until I can boot into single user mode so I can try to rollback the config to before I made the change but I need help.
I have never seen a firewall that essential can break itself with no warning like this. Is there a failsafe way to ensure this cannot occur in the future?
Once I get access to the filesystem, I can backup the change versions of the xml and try to provide more details of what change was made that killed this.
I would really like the ability to apply changes in RAM instead of writing to disk as a default. This way if something breaks, a simple reboot will restore to the most recently saved config like most other routers.
I was still able to get the network up and working with our new circuit after I completed the provider's circuit activation but still cannot gain access to the webgui.
I tried accessing the webgui from the new WAN2 interface (I had setup all the access rules before I realized that the circuit had not yet been activated)
The root password isn't working so I am going to have to wait until I can boot into single user mode so I can try to rollback the config to before I made the change but I need help.
- Where is the auto-created backups stored in the file system?
- How can I roll it back from the console so I can go back to before i disabled the interface? My last backup is over a year old)
- How can I identify why this happened?
I have never seen a firewall that essential can break itself with no warning like this. Is there a failsafe way to ensure this cannot occur in the future?
Once I get access to the filesystem, I can backup the change versions of the xml and try to provide more details of what change was made that killed this.
I would really like the ability to apply changes in RAM instead of writing to disk as a default. This way if something breaks, a simple reboot will restore to the most recently saved config like most other routers.
