The config is saved as JSON AFAIK. So it should be relatively easy to see what is going on.
I would recommend enabling DHCP at least for some small address range on the router. At least that way, you will be able to obtain correct IP and network config - then connect to the router when something like this happens. Tomas On Mar 5, 2018 9:05 AM, "wes" <[email protected]> wrote: > On Sun, Mar 4, 2018 at 2:26 PM, Rich Shepard <[email protected]> > wrote: > > > Configuring a new Ubiquity EdgeRouter-X I'm missing a step between > > connecting to the unconfigured router on its default IP address and > > connecting to it on the LAN address. > > > > Connecting the laptop to the router on the 192.168.1.0 network I > upgraded > > the firmware to the newly-released version 1.10, then restored the saved > > config > > file from the old router. Then I rebooted the router, but it did not want > > to > > complete; I don't know what I did incorrectly up to this point. > > > > What you describe is more or less the correct set of steps. There isn't a > missing step I'm aware of. I imagine there is some other problem going on, > but not enough info to determine what. > > > > Resetting the network from 192.168.1.0 to 192.168.55.0 and restarting > the > > laptop after moving the cat5 cable from eth0 on the router to eth1, I > tried > > to connect to it. This failed as the 'network is unreachable.' > > > Why move your connection from eth0 to eth1? Did you try all the ports? > > > > Sure enough, > > there are no routes to the network or a default gateway. > > > > Since you're not using DHCP, you won't find automatically generated routes > nor will a default gateway be set. None of this matters; all that matters > is whether you can ping .1 of whatever network you're on or not. > > I could do a hard reset on the router to default configuration and start > > over upgrading the firmware OS and restoring the saved config file, but I > > need to learn what step I missed between the configuration on the default > > network and connecting to the local LAN network address. > > > > This is a reasonable step, and as you say, the most efficient path to > getting connection to the router. However this doesn't tell us a whole lot. > Sometimes just "doing it again" works, and if we're lucky that will be the > case here. More likely, the same steps will result in the same condition at > the end. > > I wonder what format your router backup file uses. If it's plain text, it > may be useful to us to look it over and see if we can find any obvious > trouble spots. > > -wes > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
