oun...@wispa.org [mailto:ubnt_users-boun...@wispa.org]
>> On Behalf Of Brett A Mansfield
>> Sent: Thursday, November 10, 2016 2:25 PM
>> To: Ubiquiti Users Group
>> Subject: Re: [Ubnt_users] EdgeRouter config not applied
>>
>> This is managed exclusively through t
mory.
>>
>> -Original Message-
>> From: ubnt_users-boun...@wispa.org [mailto:ubnt_users-boun...@wispa.org]
>> On Behalf Of Brett A Mansfield
>> Sent: Thursday, November 10, 2016 2:25 PM
>> To: Ubiquiti Users Group
>> Subject: Re: [Ubnt_users] Edge
memory.
>
> -Original Message-
> From: ubnt_users-boun...@wispa.org [mailto:ubnt_users-boun...@wispa.org]
> On Behalf Of Brett A Mansfield
> Sent: Thursday, November 10, 2016 2:25 PM
> To: Ubiquiti Users Group
> Subject: Re: [Ubnt_users] EdgeRouter config not applied
field
Sent: Thursday, November 10, 2016 2:25 PM
To: Ubiquiti Users Group
Subject: Re: [Ubnt_users] EdgeRouter config not applied
This is managed exclusively through the GUI.
Thank you,
Brett A Mansfield
> On Nov 10, 2016, at 12:12 PM, Andy Trimmell
wrote:
>
> Did someone make config changes b
sage-
> From: ubnt_users-boun...@wispa.org [mailto:ubnt_users-boun...@wispa.org]
> On Behalf Of Brett A Mansfield
> Sent: Thursday, November 10, 2016 2:09 PM
> To: Ubiquiti Users Group
> Subject: Re: [Ubnt_users] EdgeRouter config not applied
>
> Quick update, I changed c
Ubiquiti Users Group
Subject: Re: [Ubnt_users] EdgeRouter config not applied
Quick update, I changed config.boot to config.bootold and
config.boot.invalid.~ to config.boot and then rebooted. All is well now.
Anyone have this happen before? Is there a way to prevent it besides
adding this to a
Quick update, I changed config.boot to config.bootold and config.boot.invalid.~
to config.boot and then rebooted. All is well now.
Anyone have this happen before? Is there a way to prevent it besides adding
this to a battery backup?
Thank you,
Brett A Mansfield
> On Nov 10, 2016, at 12:00 PM,
I have a huge customer running on an EdgeRouter Pro. They just had a power
outage and router went back to default. It's running v1.8.0. Here is what I see
in the CLI:
Can I rename that invalid file to config.boot and it will work? Or do I have to
reconfigure from scratch?
Thank you,
Brett A