Josh

Public
  • Content count

    40
  • Joined

  • Last visited

  • Days Won

    11

Community Reputation

5 Neutral

About Josh

  • Rank
    Noteworthy
  1. Is it possible to "burn out" the antennas on these devices? We currently have a WDS system with 4 pairs of these set in WDS-Bridge mode. They are all set point to point, no multi-point is involved. 3 of the pairs have been flawless in performance. The fourth pair, however has been problematic. The client side antenna on the bridge seems to fail, about once a year. This node supports a small office environment with 5 IP phones, 6 PC's, a Server, and 6-10 wireless devices on an AP. I believe the issue is arising in the fact that the server does daily backups to our main server located where our source side antennas are. Is there better device option for this bridge? The two antennas are ~1/4 mile apart, and the ENS500's currently have an RSSI of -61dBm. I am thinking that a pair of EnStation AC's would probably do a better job of handling the volume of data on this bridge, however I am not sure if the distance is to close for those to work efficiently.
  2. The first test would be to see if you get internet inside on a computer while plugged directly in to the ENS202EXT. If your computer connects while wired, then your set up as far as the ENS202 is correct. If it does not connect then there needs to be something changed in the client bridge mode settings, but it sounds as if you have this part right already. The next step would be to set your home router to access point mode with 192.168.43.1 as the gateway. The trick part comes along with an IP address for your router.... Most routers require you to specify a static IP address for the router itself. i.e. 192.168.43.50 as was assigned above. The hard part is that if the Marina router does not have a pool of reserved IP addresses for devices with static IP's then you have a good potential to run into conflicts. If you can talk with the Marina's tech people and see if there is a pool of reserved addresses and if there is one you can have for your outer, that would be the best situation. The other option, if you cannot get assigned a static IP for your router is to allow it to have an IP address assigned to it through DHCP. As an access point, once it has an IP on the correct subnet, it should just pass through all of the information and allow the marina router to handle the DHCP for all the devices associated to your router. Most people find that when you connect a second router downstream from a first router, there are almost always IP conflicts, the easy fix is always one router and a multitude of access points.
  3. I think your easiest solution would be to set your second router to a static IP of 192.168.1.2, (make sure to change the DHCP rules in your pimary router to not assign this address to anything else, i.e. DHCP starts at 192.168.1.3). Then set the second router to access point mode, with the gateway as 192.168.1.1 You will have to disable DHCP on your second router and let the first router handle all of that. you should then be able to ping both sides of the network and should also be getting solid internet through the second router.
  4. I believe the Default Gateway within the ENH500 should be set to 192.168.1.1 So that it looks to your router for internet.
  5. I was once where you are now. Struggling with the right order of steps and learning as I went. EnGenius devices are not the easiest to set up, however they seem to be the most stable and reliable once they are configured correctly.
  6. Yes you will need to turn off the computers built in wifi. Pages 22-23 of the manual have specific instructions for Mac users on how to manually configure an IP address. Once you are not on the routers signal or network, 192.168.1.1 will take you to the ENH500 configuration screen. Provided you are connected directly to the ENH500 through the POE injector. You will know the POE injector is connected correctly if the lights on the ENH500 start blinking immediately. If they do not light up as soon as the ENH500 is connected to the POE Injector, you are most likely on the wrong side.
  7. I think I might have gotten you a little confused with the numbers and addresses. Basically the thing to remember is that no two devices on your network can have the same IP address at the same time. Once you set your Mac's IPv4 to 192.168.1.10, have it connected directly to the ENH500 via the POE injector, and everything is powered on, you will be able to go to 192.168.1.1 in your browser and access the interface of the ENH500. You will then change the default IP address of the ENH500 from 192.168.1.1 to 192.168.1.250. (This is done to avoid the IP Address conflict with your router which already has 192.168.1.1 reserved for itself.) You set the subnet mask as 255.255.255.0, and the default gateway as 192.168.1.1 . (Chapter 8 in the manual linked below.) Here is a link to the EnGenius web page containing the Full owners manual, which usually does not ship with the devices. The quick start guide leaves a lot out in my opinion. This also includes specific instructions for Mac users as well. Also make sure to pay specific attention to the "Accept" button and the "Save and Reload" button. https://www.engeniustech.com/wp-content/uploads/2016/12/ENH500_Manual.pdf At this point you reset your Mac IPv4 settings to DHCP, reconnect everything back to the router and then you can use 192.168.1.250 in a browser, and it will take you to the exact same login page as before. Once you know you have confirmed connectivity through the router, you can then go into the wireless settings and set the mode to Access Point and enable and edit the SSID and password. I hope this helps.
  8. POE side to the ENH500 and LAN side to your MAC. You will need to give your MAC any address other than the one you want to assign to the ENH500. I.e. If the ENH500 will be 192.168.1.250 after you change it, you will have to manually assign your Mac to anything but that. I.e. 192.168.1.10. You won't need to worry about anything in the gateway portion of your IPv4 settings on your Mac while your initially configuring the ENH500. you will also have to set your MAC IPv4 settings back to DHCP or automatic after the initial configuration before you reconnect it to the router so it will be able to see the network again. other wise it looks like you're on the right track. Once you've assigned the ENH500 the address of 192.168.1.250, yes you would then be able to type that address into a browser to access the control panel of the ENH500.
  9. ENH 500 Access Point and Client Bridge

    If your AP and your Gateway have the same IP, it will cause a conflict. The AP should be a different IP address, i.e. 192.168.1.2 or any other unused address available on the router. You'll have to change it manually through the ENH500 UI, by connecting it directly to your computer through the POE injector. You will also have to give your computer a temporary static IP address on the same subnet to allow it and the AP to communicate. However, it sounds as if you are trying to bridge to separate, discrete networks together. If all the devices are not on the same subnet, i.e. 192.168.0.xxx or 192.168.1.xxx, they will not communicate across the bridge. One side will see the network on its side and up to the bridge device on its side, and the other side will see its respective buildings network and up to the bridge on its side. Think of the bridge as a long distance Ethernet wire. It doesn't change any properties of your network, it simply sends it out over a wireless signal. It also seems as if you are trying to do two separate things, is your ENH500 an AP or a bridge? It can handle both sides of the traffic, the mode has to be set correctly.
  10. When he says bypass the router, he means to connect the computer directly to the ENH500. The order would be: Computer > POE injector ("Network" side) > POE injector ("Output" side)> ENH500. This eliminates the address conflict with the router, allowing you to access the UI of the ENH500 at 192.168.1.1. From there you would change the static IP of the ENH500 to any unused address, (i.e. the 192.168.1.250) as recommended above. You will also have to set the "Gateway" IP to the router IP (192.168.1.1), this allows the AP to find the router and thus the internet signal it sends out.. Then you can put your network all back together normally, connect your new ENH500 to the router though the POE injector, and access the AP through the new IP address. DO this at your desk or somewhere the ENH500 is easily accessible, so if you did make an error in addressing, it is easy to get to the physical rest button. Once it is on a wall or mounted up high this becomes more of a chore. As far as the SSID and password goes, that is not as concrete of an answer. In theory, Yes, you should be able to replicate the routers wireless credential settings on the ENH500. Some devices will play nice like that. Your phone, tablet, etc... should switch to the stronger signal once it is in range, and the weaker signal is below a certain threshold. The one drawback is that you don't know exactly where your signal is coming from and if the need to troubleshoot the WiFi arises, you won't know if the issue is with the router or the AP. If identical SSID's do not work, you will have to assign a different SSID on the ENH500. (i.e. the routers SSID is "HOMENET", or "HOUSE", the ENH500 SSID can be as simple as "HOMENET1", or "GARAGE", the passwords can remain the same for simplicity, however that is not a best practice as far as network security is concerned. But your device will remember the credentials once you enter them once, so it's not that much trouble to have two different ones.
  11. Are these settings compatible with the SA5315 and SA2312 sector antennas I have tethered to the device? Also for some reason the 2.4GHz channel seems to have less range than the 5GHz channel. If everything else is the same, (clear line of sight, same client etc...,) shouldn't the opposite be true?
  12. For some reason my ENH1750EXT has stopped sending the internet signal out to the clients. I can go to the tools menu and ping an external site and get roundtrip and ping time results but for some reason when I associate my wireless clients to any of the available SSID's it tells me "no internet connection," is there any other settings I can edit to fix this?
  13. What should my expected line of sight range to an iPhone type client be from each of the AP's the ENH1750EXT alone, as well as connected to sector antennas, as well as the ENS500EXT stand alone as well as paired with a, SA5219. I am ultimately trying to cover an entire golf course with effective WiFi for scoring an public use. I am basing my model off of the campsite case study on the EnGenius home page. That prospective map does not include expected distances or ranges, and outside of the 1.86 mile range of a sector antenna, there are no other ranges given for access points other than "Long Range." I just need to know how far away I can realistically expect an iPhone or iPad client to have effective connectivity. So from there I can anticipate how many EnStation/AP combination relay stations I will need to provide. I am aware that as well as line of sight, distance above the ground also makes a difference, I am anticipating the ENS500EXT/SA5219 combo to be on a mast approximately 15-16 feet in the air, Which will get me above most line of sight obstructions and I plan to sight the masts with clear line of sight to each other, based on current tree locations, and available power sources.
  14. Would an EnStation device be able to be set up as a Client Bridge with a ENS1750EXT? I have already mobilized the ENS1750EXT to the mast on the roof and I want to avoid having to run addtional wires or mounting any thing more on the mast if I can avoid it. The ENS1750EXT would be used as the central hub of the client bridge and the EnStation device would be used as the receiver side of the bridge. From there the signal would be broadcast through an SA5219 paired to an ENS500EXT. I just want to make sure that the EnStation will bridge to the ENS1750EXT or if it would be better to have an EnStation-EnStation pair? Everything I've read says that bridge should be compatible, and more so by using devices from the same manufacturer. The other option is to put the ENS1750EXT into mesh mode and simply associate the EnStation as a client.
  15. I have both #1 wireless SSID's set to the exact same SSID and authentication with band steering enabled. I also have Two additional SSID's on the 2.4Ghz channel, and one other on the 5Ghz channel. I have deleted and reset the settings on the #1 SSID's multiple times to ensure that I didn't type something wrong or mis-enter or mis-click a setting. I understand that from reading other posts in the forums that band steering only works on the #1 SSID slot. The security on both 2.4 and 5Ghz channels is set to WPA2/PSK TKIP+AES. The second SSID on the 2.4Ghz channel is hidden, and is used by only our weather station client. Will Band steering have difficulty or not work at all if there are additional non-identical SSID's in the slots above #1? Right now both channels are set to Access Point operation, and the only other setting that is different is the Channel HT Mode, the 2.4Ghz is set to 20/40Mhz, and the 5Ghz channel is set to 40Mhz.