Gargoyle Forum

I have an engenius 2610 and I was able to go into the web config a couple of times but now I can ping it while it is booting but then I get destination host unreachable.

Looks like this is Atheros based - does it have a redboot?

If it has redboot - and un-responsive, best thing you could do
is completely wipe the flash and re-flash a fresh build.

On my Fonera, I always do an " fis init -f " to wipe the nvram.
That cleans off everything except the redboot info

Then re-flash the current 1.1.2 and re-input your settings.

I would NOT re-load any old config, just in case something
from an old backup config is causing the issue.

I have a 2610 with the same problem. It works fine with engenius software, but i need to use it as a bridge/repeater which is not available with factory firmware. So searching for a solution I came across Gargoyle, which offers what I need. So I flashed the unit using FonFlash and it took the new firmware with no problems. I put in the default password and then a new password and time zone and that works OK, the unit resets after each change. The problem
starts when I try to edit any other information, pressing "save changes" just gives me a spining wheel of dots on the screen and it hangs there. I have to power cycle the 2610 to regain control, sometimes it saves the information I have put in, or other times I loose communication with the unit completely (no IP). At this point I cannot ping the unit. If I run a 'ping -t' and power cycle the unit I will get about 10 seconds of ping returns after it reboots and then I loose the ping returns.

I have tried v1.0.16, v1.1.6 and 1.1.7 with the same results. FonFlash works even though I cannot get the webpage to load, so I am able to reflash the unit, and I have now twice returned it back to Engenius factory software without any problems. But I would prefer the Gargoyle as it has the repeater mode that I need. My knowledge of Linux is zero, so modifying source files would be
difficult for me, but any help will be appreciated. Thankyou...exe2

I've had a report on this device that rebooting doesn't work properly with Openwrt (and therefore Gargoyle). Entering repeater mode is one of the few changes that actually requires a reboot. If you do something else (like, say, add a port forward or a quota) do you still see this issue? That will tell me if this is associated with the previously-reported reboot problem or if it is something else.

OK Eric, thankyou for your reply. This what I found out, you are correct, I can change the settings as long as I dont change anything that needs a reboot. I was able to set quotas, configure the wireless and change the password, but when I select wirelessbridge/repeater that is when the problem starts..I get the window saying its saving the settings and device restarting. It just hangs there, and the progress bar at the bottom of the screen is continually trying to load and I cannot ping the unit. After about 2 minutes I power cycled the unit and again no ping or webpage.

I left the unit for about ten minutes and checked again and I now had a ping and the webpage opened with the new settings....great. I programed the unit in repeater mode, bridge IP 192.168.1.25 and repeater 192.168.1.202 and assigned the SSID's and wep keys to work with my ADSL wireless router. I then saved the settings and again lost contact with the unit. This time I left it for about 10 minutes, but still nothing, but when I ran my IP Scan on the unit I was getting IP's from the other stations on my network but not the two IP's I had assigned (1.25 and 1.202), which suprised me. I tried the internet and it works at good speed, but I cannot log into the unit using the web browser and my IP scanner does not detect either of the static IP's i have set. I connect to the 2610 using a lan cable through the power inserter

So I have the unit working but I am not able to change any settings from my local PC, to do that I will have to reflash. Next I will check that I can connect via wireless to the unit....maybe that way I can access the settings. I am giving you all this information hoping it will be of use to you. Thankyou for your interest in this. exe2

PS I uploaded this post via the 2610.

More info...yes I was able to connect via wireless to the internet.I was also able to open the bridge (1.25) and make changes to the config. So I came back to my LAN computer and that is now working on 1.25 as well. So it seems there is a time lag between making changes and having the system working ... maybe 10 or 15 minutes (but that is ok, I can live with that)

Also, using the wireless connection I made some changes to the settings, NTP server and time zone and again when I save the settings I loose contact with the unit, but the internet started working after about 5 minutes, the Gargoyl config page took longer to appear.. aprox 10 minutes.As long as I know I have to wait for these time lags I can use the firmware, I was afraid it was not going to work at all. I'm really pleased as I now have the unit working as I
required.

The transmit power setting is shown as MAX 18dBm, the 2610 is capable of 600mw, when it says "MAX" is it going to give me the 600mw or just the 18db"s ?? I tried the 'custom' setting with 23dBm (400mw) but I get an error message.

When I do a backup of the system I get a zip file, but it will not open as I get an "error reading header" message, is this related to my current problem

??
Thankyou ...exe2

Fixed my backup file problem, I installed 7-Zip and it unpacks fine, no more error messages. I'm still interested in the power level question, am I running at full (600mw) or some lower level??

Thankyou...exe2

exe2

I am using a eoc1650 which I think is basically the same board & it works without too many problems. I am using gargoyle 1.1.8.

I certainly don't have the long pauses while the unit saves changes that you describe.

I do have the 'won't reboot' problem but (as Eric said) that is a known issue with openwrt & these units & I just powercycle it. I think there is a patch on the openwrt site for this...

David

Note that this reboot issue should be fixed in 1.2.0.

Eric

Good... what's the ETA for 1.2?

David