On Wed, Dec 18, 2019 at 2:37 PM Louis Kowolowski <[email protected]> wrote:
> Sounds like you have more than 1 dhcp server on the same network. this is > a good plan for unpredictable behavior. > If this is not the case, please confirm that you have the laptop cabled > directly to the ER-X. If this is the case, then the subnet its using for > DHCP has changed, perhaps because of the firmware update. Or perhaps the > outcome of selecting WAN+2LAN2. I don’t know what you did here. If you > can’t figure it out, I’d suggest resetting factory defaults and starting > over. > The WAN+2LAN2 wizard is almost certainly what broke it. Rich asked me to configure it, which I did. There was never any mention that WAN+2LAN2 was desirable or desired, so I'm perplexed why Rich would have felt motivated to click on that option. Luckily, he has two, unless he possibly broke both of them at the same time. > > > > On Dec 18, 2019, at 4:22 PM, Rich Shepard <[email protected]> > wrote: > > > > After changing the DHCP lease range (and applying the change) I went to > the > > Wizards tab, selected WAN+2LAN2, and changed the admin username and > > password. Saved and rebooted. Prior to this I used the ubnt/ubnt default > > login to both ping 192.168.55.4 and connect to the ER-X using its eth1 > port. > > > > After changing the login name and password and rebooting I can no longer > > connect to it. Retarting the inet1 daemon several times results in: > > > > Polling for DHCP server on interface eth0: > > eth0: adding address fe80::1a1e:8c7d:d696:a7ab > > eth0: waiting for carrier > > eth0: carrier acquired > > DUID 00:01:00:01:25:64:8a:a1:00:24:d6:45:fa:8c > > eth0: IAID 6f:69:63:ca > > eth0: soliciting an IPv6 router > > eth0: soliciting a DHCP lease > > eth0: offered 192.168.1.38 from 192.168.1.1 > > eth0: leased 192.168.1.38 for 86400 seconds > > eth0: adding route to 192.168.1.0/24 > > eth0: adding default route via 192.168.1.1 > > forked to background, child pid 6968 > > > > Notice this is now back on the 192.16.1.0/24 subnet, no longer on > > 192.168.55.0/24. And when I try to connect to the router at 192.168.1.1 > I'm > > told the network is unavailable. > > > > I'm using a DHCP lease, not a static IP address. > > > > I expected no problems changing the admin name and password and intended > to > > reboot then shut down the router. > > > > Please advise. > > > > Rich > > _______________________________________________ > > PLUG mailing list > > [email protected] > > http://lists.pdxlinux.org/mailman/listinfo/plug > > -- > Louis Kowolowski [email protected] > <mailto:[email protected]> > Cryptomonkeys: > http://www.cryptomonkeys.com/ <http://www.cryptomonkeys.com/> > > Making life more interesting for people since 1977 > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
