OpenWrt Forum Archive

Topic: Cannot access Netgear EX2700 extender after flashing OpenWrt

The content of this topic has been archived on 23 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I flashed my Netgear EX2700 extender as per the wiki:

wiki.openwrt.org/toh/netgear/netgear_ex2700

First I changed the Netgear firmware to v1.0.1.8 and then
I flashed OpenWrt 15.05 through the stock interface, as suggested in the wiki.

I tried using telnet:

Microsoft Telnet> open 192.168.1.1 23
Connecting To 192.168.1.1...Could not open connection to the host, on port 23: Connect failed
Microsoft Telnet>

My IPs are:

   IPv4 Address. . . . . . . . . . . : 192.168.1.206
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1

I even tried ssh but from what I understand I cannot ssh into the repeater until I set a password using telnet.

I'm a newbie in this area and I'm really hoping I didn't brick it...
Any input is greatly appreciated. Thanks.

can you ping it?

WWTK wrote:

can you ping it?

Yes. The response is quick (<1ms)

have you tried to connect with web browser?

Is the power led on solid or blinking?

(Last edited by WWTK on 22 Dec 2017, 21:40)

WWTK wrote:

have you tried to connect with web browser?

Yes, nothing happens. From what I've read often the browser interface is not installed and you have to install it through ssh.

WWTK wrote:

Is the power led on solid or blinking?

After a brief period the power LED is solid green. The sequence goes like this...
1) Power LED is orange,
2) Power LED is briefly green,
3) Power LED rapidly flashing orange / green for a couple of seconds,
4) Power LED stays solid green for the rest of the time.

(Last edited by jmichalik on 22 Dec 2017, 21:58)

It sure sounds like it is working.......

Is your pc getting an ip address from DHCP, or is it hard-coded?  If you manually set it, try dhcp and see if it works.

(Last edited by WWTK on 22 Dec 2017, 22:08)

WWTK wrote:

It sure sounds like it is working.......

Is your pc getting an ip address from DHCP, or is it hard-coded?  If you manually set it, try dhcp and see if it works.

I tried both.... with a static IP (router 192.168.1.1 and client 192.168.1.10) and automatic (192.168.1.1 router and client would get assigned to 192.168.1.### - with the last three digits in the hundreds).

I agree. It sounds as if its working. Especially since it is assigning IPs and pinging. But I still can't access it.

what is the ip of your main router?  maybe some kind of arp situation is causing you issues.  You may try disabling all other interfaces except the wired connection to the extender and then reboot the pc to start fresh with dhcp enabled.

WWTK wrote:

what is the ip of your main router?  maybe some kind of arp situation is causing you issues.  You may try disabling all other interfaces except the wired connection to the extender and then reboot the pc to start fresh with dhcp enabled.

Sorry I didn't get back to you quicker... Christmas... and my laptop is currently sent off for repair...

When I wrote the descriptions in the above posts, I did it only connected to the repeater with a lan cable without a connection to my wifi router. But even so, the router has an IP of 192.168.0.1 while the repeater was on 192.168.1.1.

(Last edited by jmichalik on 28 Dec 2017, 02:54)

hmmmm this doesn't really make much sense......  If you are getting an ip address from dhcp then the extender is clearly working. 

Right now I'm at a loss sorry.

This device appears to have an easily accessible serial port if you have a usb->ttl serial cable.  this might show some messages so we can debug further.  They are under 10 bucks and a worthwhile investment for anyone messing with firmware.

WWTK wrote:

hmmmm this doesn't really make much sense......  If you are getting an ip address from dhcp then the extender is clearly working. 

Right now I'm at a loss sorry.

This device appears to have an easily accessible serial port if you have a usb->ttl serial cable.  this might show some messages so we can debug further.  They are under 10 bucks and a worthwhile investment for anyone messing with firmware.

Looks like I'll have to get one. I will get back to this thread once I have one of those cables.

Thank you for taking the time to trouble shoot this with me.

(Last edited by jmichalik on 3 Jan 2018, 23:57)

The discussion might have continued from here.