Jump to content

mpr

Public
  • Content count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mpr

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. We've recently been starting to use the new ENS500EXT-AC in place of the ENS500EXT. It has some improvements but the boot and connectivity times have increased tremendously. The ENS500EXT in bridge mode could connect to our AP in about 45 seconds from a cold boot. The new ENS500EXT-AC can take over five minutes to perform the same connection. What settings can be adjusted to minimize the boot time? Are there any plans to speed up the boot process?
  2. I can't find it any more. Maybe they've fixed it so the capwap middle step is no longer needed? I have no idea. The current version is: https://www.engeniustech.com/wp_firmware/ENS620EXT-int-v3.0.1.1_c1.8.53.bin Versus: ENS620EXT-int-3.0.0.33_C1.8.53.bin
  3. Did you try resetting the AP? Maybe you changed some obscure setting on it accidentally, like setting it to operate outside a green mode channel.
  4. Is this it? https://www.engeniustech.com/wp_firmware/ens500ext-fcc-v1.5.100.0.bin
  5. So given the silence, am I assume that Engenius cannot/will not provide a fix?
  6. When is the fix for this going to drop? The issue has been out for several weeks now and we need to get our customers patched ASAP. https://www.engeniustech.com/engenius-products/outdoor-wireless-ap-ens500ext
  7. Ok after taking a break from this I have done some more investigation and believe we are on to something here! On my machine, I usually run a DHCP server in addition to the static IPs. So I'll have, for example, 192.168.1.59 and 192.168.59.1 as my static IPs. I'll also have a DHCP server dishing out IPs in the 192.168.59.200-255 range. So I break out another fresh radio (this time ENS500EXT-AC) and this one, out of the box, I can't ping it at 192.168.1.1. I run traceroute on it anyway though: traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 60 byte packets 1 192.168.59.247 (192.168.59.247) 0.735 ms 0.565 ms 0.617 ms 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * Ahh here we go! The device is actually at 192.168.59.247. It's gotten a DHCP address, but is still responding (kinda?) to 192.168.1.1. I'm guessing this is a new behavior in firmware version "1.0.0 + 1.8.53". I'd suggest in the next firmware to update it to not use DHCP, or to amend the manual @ https://www.engeniustech.com/engenius-products/enturbo-outdoor-5-ghz-11ac-wave-2-wireless-access-point/ to note that it will come up in DHCP by default.
  8. We're gonna have another one of our team try it tomorrow with a 3rd radio and see if he has any better luck. I've updated firmware so many times on these things though it's just hard for me to fathom that I could be screwing it up somehow. laireV do you know if the set of radios you've been updating from was on 1.0.0.29, or something more recent?
  9. Ok so I set aside RADIO1 as a brick and pulled grabbed a new ENS620EXT I had just provisioned. Firmware version 1.0.0.29 according to the Javascript in the admin interface. * Began the firmware upgrade steps with a factory reset. Held reset button for ~30 seconds. Removed power. Waited 30 seconds. Applied power again. Device comes up at 192.168.1.1. Good so far. * Uploaded ENS620EXTaddCAPWAP.bin. SHA256 sum of that file I have is: ac119efb30dd1c05054f79f71f9415d88410cc4f1f9c501e43c9660752f4d375 * Firmware upgrade timer starts at 600 seconds. I let it be and come back and can get to the device fine at 192.168.1.1. The admin page shows its version to be "1.0.0 + 1.8.53". * Proceed with second factory reset. Held reset button for ~30 seconds. Removed power. Waited 30 seconds. Applied power again. Device does NOT come up at 192.168.1.1. So I've got two bricks now. Unless I'm doing something really wrong, or we have a box of bad radios, I have to suspect there could be a bug in the firmware upgrade process from 1.0.0.29 to the latest.
  10. I tried doing the thirty second reset (stopwatch in front of me). That entails plugging in the device and letting it boot completely (several minutes). Then I push the pin in and hold for thirty seconds. Release. Check to see if the lights go out. This doesn't seem to work--the light patterns don't change. But I find that if I hold the reset button for 28 or 29 seconds (just a hair under 30) then release, that does make the light patterns change. I pull the power immediately as soon as the lights go out (this was suggested to me by an Engenius support person over the phone). Wait 30 seconds. Then power the device back up. But after the reset the device never comes back up at 192.168.1.1. The light patterns are power(ON), LAN1(ON and blinking OFF every second or so), LAN2(off), 5G(ON every second), 2.4G(ON every second). Now I know it's gonna be tempting to say I have my IP address on my own machine wrong or whatever, but just minutes earlier after the first factory reset things were fine and I could reach 192.168.1.1. And I can reach other Engenius equipment I have in the office (mostly ENS500EXT) just fine. Can anyone else actually confirm that they've taken an ENS620EXT from firmware version 1.0.0.29 to 3.0.0.33_C1.8.53 using the six steps described in the README?
  11. I have a set of ENS620EXT radios and was attempting to upgrade one to the latest firmware. Downloaded version 3.0.0.33 from the site, as a RAR file. Unpacked it and found these instructions: 1) Factory Rest the ENS620EXT 2) Upload the ENS620EXTaddCAPWAP.bin file first to the ENS620EXT 3) Factory Reset the ENS620EXT 4) Upload the ENS620EXT-int-3.0.0.33_C1.8.53.bin to the unit 5) Factory reset unit 6) The unit should be ready to work with EWS switch or ezMaster Network Managment Software. A bit more than I'm used to seeing, but I began following it step by step. Steps 1 and 2 went fine, but after doing the factory reset in step 3, the device no longer boots and I can't ping it at 192.168.1.1 (except for a few brief seconds when it powers up). Has anyone successfully performed this firmware update? From looking at the Javascript code on another radio, I believe the exact version of the current firmware I'm on is 1.0.0.29.
  12. Yes I'm running Linux and have two static IPs on the interface: 192.168.1.59 and 192.168.61.1. I'm briefly able to ping the device at 192.168.61.10 when I reboot it, and I also was able to do a software reset of a third ENS620EXT device and connect to it just fine at 192.168.1.1. So I'm pretty confident I have my routes setup correctly here. The fact is though I have not been able to successfully hard reset a ENS620EXT model yet.
  13. Another note, when I was configuring the IP address to 192.168.61.10 I seem to recall leaving the Gateway field blank. My coworker here said the ENS500EXT used to require you to enter a gateway even if you didn't intend to use it. Could it be the device is somehow locking up from that?
  14. We also have a third radio that I am able to reach and log into. I'm having trouble getting the hard reset to work for it also though! I push and hold the reset button for >10 seconds, release, and it reboots, but then comes up with the existing settings--not the defaults. There must be something more to the reset sequence than what is described in the docs for other devices...
  15. I was logging into one of our new ENS620EXT units and after finishing the WIFI changes I updated the IP address to 192.168.61.10. We do this sort of change all the time on our old ENS500EXT units. However after doing the reset I am unable to find the unit at the given IP address. I've quadruple checked my routes and had another person look them over so I'm pretty sure it's not a route issue. So I try a hardware reset. I push the reset button in for >10 seconds, release it. The lights all flash off, then they all flash on, then into various patterns. During this process I am running pings to 192.168.1.1 and 192.168.61.10. Oddly enough, 192.168.61.10 does come up for a few seconds: ...From 192.168.61.59 icmp_seq=398 Destination Host Unreachable 64 bytes from 192.168.61.10: icmp_seq=399 ttl=64 time=999 ms 64 bytes from 192.168.61.10: icmp_seq=400 ttl=64 time=0.329 ms 64 bytes from 192.168.61.10: icmp_seq=401 ttl=64 time=0.532 ms From 192.168.61.59 icmp_seq=437 Destination Host Unreachable... But then it stops. The end result on my lights is the Power light is solid red and the 5G light is blinking steadily at a slow rate. Any ideas? Does anyone have an exact sequence of steps for doing a hardware reset on this model?
×

Important Information

By using this site, you agree to our Terms of Use.