Try these keywords: usb, join, realtime, remote, etc

All devices connected to the same SSID broadcasted by the ezhotspot are on the same subnet and not subject to any client isolation.

Ensure your clients are receving the same IP range as assisgned. For example, 192.168.93.X

Ensure the firewall of computers or laptops are not blocking any incoming traffic.

Ensure there are any no other customized Traffic Rules created in the Advanced Dashboard.

Perform a factory reset


Yes, it is possible to use a different directional antenna with a higher dB gain. 2 areas to take note will be:

  1. Ensure the antenna is of the correct frequency. On the V4, only antennas with 2.4Ghz specifications can be used. On the V5, antennas of 2.4Ghz or 5-5.8Ghz specifications can be used. On the V5, ensure it is connected to the correct SMA connector as indicated.

  2. Ensure your the end of your antenna connector is of RP-SMA-Male type to fit correctly to the Ezhotspot device.

It is recommended that only 1 directional antenna be used for transmission with the distance remote wireless hotspot and the original omni-directional pole antenna is used for distribution to wireless device effectively in a 360 degree coverage. Any ports can be used.  

To use Cast or Airplay, both ipad and TV must be connected to the same subnet, which means they must have the range IP address range, for example 192.168.93.X.

If TV is connected to another network,

1. use the Ezhotspot in the Transparent Repeater if repeating the other network wirelessly.

2. use the Ezhotspot as a wireless access point if connecting to the other network with a LAN cable.

From version 4.48 and above, the default wireless key of the wireless repeater is initially the same as the remote network when enabled. However, it can be changed as needed in the advanced dashboard.

However, there is no need and you should never use the transparent repeater function in a public hotspot because it will expose all your devices to the public. Some hotspot providers only offer a simply "wireless key" solution for you to get internet access, without any captive portal solution. It is clearly a very cost-down solution and most probably without client isolation ( a function that prevents other people on the same network to see you). You should be careful and just use the ezhotspot in the default mode, because a firewall is enabled to protect your devices.

In the normal mode, the ezhotspot operates like a wireless router. In the transparent repeater, the ezhotspot operates like a wireless access point. See details in below link.

The Ezhotspot extender runs on OpenWRT operating system with an enhanced EZwizard menu and is dynamically changing with each firmware upgrade to provide more features and security enhancement. Hence, there is no fixed manual and all Ezwizard guides are located online here and upgraded regularly:

In the Advanced Dashboard area, the documentations can be located at the below link:

After a update, the wireless key is reset back to factory default as shown on the label underneath the device. It is also the serial number of the device.

In your wireless setting, forget the ez@XXXXXX network and rejoin back to the ez@XXXXXX using the wireless key as shown on the label.

When the ezhotspot is updated to a newer firmware, the ezhotspot's SSID and wireless key becomes factory default. If you have previously changed your wireless key, you will need to configure the ezhotspot to be using the changed wireless key or configure the Chromecast to join to the ezhotspot with the default wireless key.

The LED is an important aspect to indicate the intensity of the wireless connectivity. When disabled, it will be automatically enabled upon joining to another remote wireless network.

While it maybe slightly unpleasant in view, the best suggestion currently would be to apply a small piece of black electrical insulating tape over the LED. When needed, it can be easily unpeeled to reveal the signal.

The LED disabling in the EZwizard menu will be considered for Future firmware release

If the Green LED stays for more than 1 minute after a firmware upgrade, it may be due to a corrupted firmware in the ezhotspot and that it cannot boot up correctly.

Kindly contact your seller immediately and have the device returned which our sellers have the proper tools to check for any hardware abnormalities, recover and flash the latest firmware to your device.

Check if you followed this guide below:

If problem persists, check the following:

  • correct username or password
  • wireless signal of remote SSID is reasonable with at least 3 green bar
  • check the syslog and kernel log in the Advanced Dashboard which might give some indication whether it is a wireless signal or user authentication problem
    (Note: you need to use a LAN cable connected to the yellow port of the ezhotspot to your laptop to do this check)


Example of System Log showing a successful wireless connection and IP address provided by remote 802.1X network

daemon.notice netifd: Interface 'hotspot24' is enabled kernel: [1430850.493714] wlan0: authenticate with ae:22:15:60:3b:XX kernel: [1430850.505785] wlan0: send auth to ae:22:15:60:3b:XX (try 1/3) kernel: [1430850.507526] wlan0: authenticated kernel: [1430850.508514] wlan0: associating with AP with corrupt probe response kernel: [1430850.514470] wlan0: associate with ae:22:15:60:3b:XX (try 1/3) kernel: [1430850.533675] wlan0: RX AssocResp from ae:22:15:60:3b:XX (capab=0x1411 status=0 aid=1) kernel: [1430850.533910] wlan0: associated kernel: [1430850.534503] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
daemon.notice netifd: Interface 'hotspot24' has link connectivity
daemon.notice netifd: Interface 'hotspot24' is setting up now
daemon.notice netifd: hotspot24 (19281): udhcpc: started, v1.25.1
daemon.notice netifd: hotspot24 (19281): udhcpc: sending discover
netifd: hotspot24 (19281): udhcpc: sending discover
udhcpc: sending select for
udhcpc: lease of obtained, lease time 7200

Example of Kernel Log showing a successful wireless connection but failed authentication with remote 802.1X network 

[ 394.409285] wlan0: authenticated
[ 394.412171] wlan0: associate with a6:17:31:3f:03:XX (try 1/3)
[ 394.417792] wlan0: RX AssocResp from a6:17:31:3f:03:XX (capab=0x411 status=0 aid=3)
[ 394.418064] wlan0: associated
[ 426.698078] wlan0: deauthenticated from a6:17:31:3f:03:a3 (Reason: 23=IEEE8021X_FAILED)
[ 462.391607] wlan0: authenticate with a6:17:31:3f:03:a3
[ 462.404322] wlan0: send auth to a6:17:31:3f:03:a3 (try 1/3)
[ 462.412863] wlan0: authenticated
[ 462.422325] wlan0: associate with a6:17:31:3f:03:a3 (try 1/3)
[ 462.425988] wlan0: RX AssocResp from a6:17:31:3f:03:a3 (capab=0x411 status=0 aid=3)
[ 462.426265] wlan0: associated
[ 486.704237] wlan0: deauthenticated from a6:17:31:3f:03:a3 (Reason: 23=IEEE8021X_FAILED)


If device is on firmware version 4.48, ensure it is updated to ReL 2019-06-16 (a patch to fix reloading of firewall during DHCP renewals from Captive Portal)

  1. Ensure the Ezhotspot has internet access
  2. In the Status Menu, scroll to bottom of screen and check the ReL sub-version. If it does not show ReL 2019-06-16, hit the [Reload page] button until the ReL 2019-06-16 is showed.

Otherwise, if captive portal is always prompted after a period of inactivity, you can use the [Keep Internet Alive] menu in the [Configuration & Status] menu.

You should use the EZhotspot as a  Wireless Access Point by using the Yellow LAN.

By using the Blue WAN port, the Ezhotspot becomes a Wireless Router.

As a Wireless Access point, no configuration of Firewall is required, becuase it is in a bridged mode and all IP addresses should be assigned by your home router.

If required in certain situation, the Ezhotspot may assign IP address to devices from the wired network. Please follow below instructions.

Use the [Transparent Repeater] feature.

Change the default broadcasted SSID ez@XXXXX to something else.

Create additional SSID in [Transparent Repeater] which your apple devices were previously to.

The result is your apple devices will be visible when connected to the V4 or your home router.

First, upgrade to version 4.48.

In the [Gateway Override] feature, adjust the metric value of the WAN Port interface to a higer value than the Wireless connection. This way, whenever you have a wireless connection, the data on the 4G modem connected on the WAN port will not be used.


The V4 uses 2T2R MIMO technology to achieve a physical link rate of 300mbps on the 2.4Ghz.

To obtain "best wifi connection", the few points need to be considered:

  • Does the corresponding remote hotspot supports 2T2R?
  • How many other wireless clients are the hotspot also handling at the same time?
  • Whether your connecting clients to the V4 are also 2T2R ready device?

The V4 primarily objective is the range than the bandwidth, since most hotspot providers will throttle the internet bandwidth to 5~20mbps per user connection. By optimizing the range coverage, it would at least ensure that the throttled bandwidth can be reliable. In a typical campsite, you might be easily contesting with 50 or more other users for internet. The single outdoor antenna provided in the V4 package gives you an added advantage in the range coverage in this case.

Connecting optional MIMO antenna to the V4, generally improves the range coverage but it also depends on the gain of the antenna type and the loss through the cable length. However, the internet bandwidth is not going to exceed what the campsite operator has throttled down to.

It is welcome to post any bugs here so that it can also be ready publicly when there is a solution. The following format is prefered by posting:

  • Device Model
  • Firmware Version
  • Description of issue encountered