ASUS EA-N66 3-1 Ethernet/WiFi extender and Tomato fw wireless router

Discussion in 'Tomato Firmware' started by Dr Strangelove, Sep 27, 2013.

  1. Dr Strangelove

    Dr Strangelove LI Guru Member

    I have an ASUS Ethernet EA-N66 3-1 AP/bride/range-extender which I'm using with a Linksys E4200v1 running latest Toastman Tomato fw.

    The E4200v1 and EA-N66 work well at 15m separation over Ethernet LAN using "Access Point Mode"(Ethernet LAN AP mode) with Tx Power adjustment dropped from 100mW to 50mW to deduce noise and impact on E4200v1 2.4GHz WiFi.
    I'm using a 2.4GHz 40MHz two channel WiFi SSID where both E4200v1 and EA-N66 are using the same channels/SSID.
    Would work better if the EA-N66 was on non overlapping 2.4GHz 40MHz channels, but my neighbors would probably disagree with me on that point.

    No WDS support on the ASUS EA-N66. :(

    Just for fun(what if), I attempted to use the EA-N66 in range extender mode, where the EA-N66 becomes a WiFi re-transmitter to extend/strengthen WiFi signal.

    I could not get the EA-N66 to work in this mode.

    I note the EA-N66 increments it's MAC address by one(+1) in range extender mode.

    In "Repeater mode" I can connect to the EA-N66 and manage it, so, access wise that part works, just not client WiFi access via the EA-N66 in "Repeater Mode".

    I have a Linksys RE1000 (old original version) which works will on 2.4GHz 20/40MHz 1-11 channels with E4200v1 running Toastman Tomato fw as proof of WiFi range extender support.

    Anybody else played around with an EA-N66 3-1 AP/bride/range-extender with any sort of success using a Tomato fw wireless router?

    Thank you in advance for any advise/experiences.
    Last edited: Sep 27, 2013
  2. Dr Strangelove

    Dr Strangelove LI Guru Member

    No dear, this is somewhat embarrassing, ALWAYS do your research before posting... and then only when you've double checked everything. :oops:

    The EA-N66 as a Range Extender is working.

    It uses some seriously weird MAC/ARP addressing, which appears, will have to be left as dynamic.

    It places the br0 as the MAC address of the EA-N66 with the address of the client.
    So in the E4200 arp table (arp -a) sees the EA-N66 MAC address bound to the unit itself and every client that is using WiFi through the device.
    One MAC address and many IP addresses.
    You can see the individual MAC addresses of the clients connecting through the EA-N66 on the device.
    The client MAC addresses are seen on the Linksys E4200, but not bound to an interface/group as seen in status -> Device List

    On my Linksys RE1000, it use the OUI of the Linksys RE1000 and the remaining octets of the client MAC address, thus external LAN devices can identify unique devices using the Linksys RE1000.

    The reason I had problems was(is) I have my client devices listed in a forwarding DNS server on the Linksys E4200 which was/is conflicting when static ARP is employed.

    If I bind the MAC and IP address of the client being advertised via the EA-N66, it's then bound to the br0 interface and not seen as a 'floating' ARP address which is bound on the EA-N66.

    So, without further advise, it seems like dynamic ARP... or nothing with the EA-N66 range extender setup.

    But, it does work. :D


    Bit more reading and the ASUS EA-N66 Version firmware seems to be a bit of a dogs breakfast when it comes to "Extender Mode". It'll work with one client, but additional clients seem to cause IP address conflicts and dropouts with no known way to correct this.
    Last edited: Sep 27, 2013
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice