Yeah, you do not need UC for that. The UniFi front ends tend to be a bit
terse, and Ubiquiti tries to
"move" you to the UC. But with a single or even just two it is not worth
it. Enjoy and press on...
On Fri, Dec 27, 2019 at 11:13 PM Rich Shepard
wrote:
> On Fri, 27 Dec 2019, Chuck Hast
On Fri, 27 Dec 2019, Chuck Hast wrote:
I have several UniFi devices I have to deal with ended up installing the
UniFi controller on a Raspberry Pi and dealing with them that way. If you
are just dealing with the Edge router probably no big deal but if you have
more of their devices you might
On Fri, 20 Dec 2019, Russell Senior wrote:
You need to configure your laptop with a static IP, at least until you get
the DHCP server on the ERX running again.
I had it set to 192.168.1.101 with dhcp turned off.
More when I have it.
Rich
___
PLUG
On Fri, Dec 20, 2019 at 1:18 PM Rich Shepard
wrote:
> On Fri, 20 Dec 2019, Russell Senior wrote:
>
> > Did you restore the config I sent you, like I suggested?
>
> I need to be able to communicate with the router to do this. It was the
> next
> step after setting a username and password. But
On Fri, 20 Dec 2019, Russell Senior wrote:
Did you restore the config I sent you, like I suggested?
I need to be able to communicate with the router to do this. It was the next
step after setting a username and password. But after saving the change and
rebooting, and rebooting the laptop,
On Fri, Dec 20, 2019 at 9:02 AM Rich Shepard
wrote:
> On Thu, 19 Dec 2019, Russell Senior wrote:
>
> > Success?
>
> No. I was able to log in using ubnt/ubnt and change login name and
> password.
> Saved change and rebooted. Tried logging in again and it rejected both
> ubnt/ubnt and the new
On Thu, 19 Dec 2019, Russell Senior wrote:
Success?
No. I was able to log in using ubnt/ubnt and change login name and password.
Saved change and rebooted. Tried logging in again and it rejected both
ubnt/ubnt and the new login name/password. ip showed no 192.168.0.0/16 LAN
address for eth0
Success?
On Wed, Dec 18, 2019 at 6:20 PM Rich Shepard
wrote:
> On Wed, 18 Dec 2019, Russell Senior wrote:
>
> > First, restore the config I sent you.
>
> The only difference between the one I had saved here and the one you sent
> is
> in the config.boot files. Your's adds a dhcp section and
Thanks for going through this systematically and with care Russell,
On my part, I admit that I really did not pay attention to 2lan versus
2lan2 difference. I thought it is just a typo. I am sorry if I caused
confusion.
-T
On Wed, Dec 18, 2019, 20:35 Russell Senior
wrote:
> First, restore the
On Wed, 18 Dec 2019, Russell Senior wrote:
First, restore the config I sent you.
The only difference between the one I had saved here and the one you sent is
in the config.boot files. Your's adds a dhcp section and restores the
default login name/password. I can change that in the user tab
First, restore the config I sent you.
You'll need to restart your network, since you'll get a 192.168.55.x
address after the ERX restarts.
Read this: https://dl.ubnt.com/guides/edgemax/EdgeOS_UG.pdf
In particular, see Chapter 10 which covers users.
I'm not sure where you'd set a hostname for
I matched the configuration you sent me, exactly, with the two exceptions I
explicitly mentioned. The wizard was not needed and is what stomped on the
configuration I had set up, and indeed was probably not what you wanted. As
Tomas suggested, the wizard you clicked on was probably to set up one
On Wed, 18 Dec 2019, Rich Shepard wrote:
So, I'll read how to reset it to factory defaults and start from scratch.
As the Dell now accepts leases on eth0 I'll be able to re-do the wizard,
services, and system configurations.
Tomorrow I'll do a hard reset, connect Dell and ER-X on wlan0 and
On Wed, 18 Dec 2019, Russell Senior wrote:
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.
On Wed, 18 Dec 2019, Louis Kowolowski 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
On Wed, 18 Dec 2019, Russell Senior wrote:
Why "selected WAN+2LAN2"?
Because that uses eth0 as the WAN port and bridges eth1-4 for the LAN. The
original er-x was set up that way.
Rich
___
PLUG mailing list
PLUG@pdxlinux.org
On Wed, Dec 18, 2019 at 2:37 PM Louis Kowolowski
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,
I would check if you are connected to the router through the correct port.
If you are accidentally on wrong port you might not be able to access the
configuration service.
You mentioned wan+2lan - so I would expect that you end up with wan on one
port, lan1 on another port and lan2 on the third
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
Why "selected WAN+2LAN2"?
On Wed, Dec 18, 2019 at 2:23 PM Rich Shepard
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
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.
21 matches
Mail list logo
