I am new to ARDEN and am installing a small lab network with three GL-AR300M16 routers to learn how it works.
Everything seems to have installed properly. The nodes are communicating between themselves just fine. I can connect to all three nodes with my laptops and can communicate between them.
My problem is that I cannot connect the WAN port to my home router. I get the same result on all three. I see the connection light on home router, but I am not getting an address from DHCP.
Prior to upgrading them with the ARDEN firmware, all three connected to my home router using the initial GL-iNet firmware just fine..
Am I missing something, or will this just not work on these low-end routers. The documentation is pretty straight forward, and I think I did it right.
Any help will be greatly appreciated.
Thanks,
Len
W2LJR
Yes, My laptop PC is plugged into the LAN port of the GL-AR300M16 and is receiving a DHCP address from it. The WAN port is configured for DHCP and is connected to my Home Router. I see the link light on my home Router, but I do not see that the GL-AR300M16 is getting a DHCP address.
I tried configuring a Static IP Address on the WAN interface of the GL-AR300M16 in the same subnet as my home network, but that didn't work either.
Prior to installing the ARDEN software, I tested the GL-AR300M16 and I was able to get a DHCP address form my Home Router on the WAN interface.
Thanks again,
Len
W2LJR
"Attention
Be sure to uncheck the Keep Settings checkbox, since GL.iNet settings are incompatible with AREDN® firmware."
I have used my AR300M16 as a (WAN/LAN) router without issue.
73, Chuck
Me too!
I have not been using my AR300M16's WAN port for several months.
I plugged my AR300M16's WAN port into my Home Router's LAN,
got lamps, got no DHCP address.
:-|
73, Chuck
Hi, Ian and the AREDN developers:
Thanks
73, Chuck
Thank you
Len
W2LJR
I have attached screen shots of all my configuration.
Thanks,
Len
W2LJR
Had the same issue even after installing nightly build -- wiped config and now WAN is getting DHCP
Thank you so much. Setting the AR300M16 back to "First Boot" fixed the problem.
I really appreciate all the help I received from everyone.
Thanks again and 73,
Len
W2LJR