On Sun, 4 Mar 2018, wes wrote:
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.
Wes, It might be that the router did not properly reboot.
Why move your connection from eth0 to eth1? Did you try all the ports?
Because eth0 on the EdgeRouter is the equivalent to the WAN port on the Linksys and Netgear routers. When configured for the LAN I should be able to connect to it on eth1-4.
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.
When I started I connected to 192.168.1.1 with a static IP address on the laptop. The router's UI displayed and I was able to access the System menu to upgrade the OS and restore the config file. Didn't have an issue connecting.
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 will do this one evening this week. Thinking more about the situation not properly rebooting after the upgrade and restore could well be the issue. That's the first thing I'll check
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.
It is plain text. And saved from the original router that worked for a few days. I'll post results of the do-over. Thanks, Rich _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
