What's new
By:

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

[EA-N66] Disconnect after first boot

O

obfuscator

Occasional Visitor
Hi all,

I have an issue with my EA-N66 device. I use it as a bridge to connect my PC to my wireless network router RT-N66U. The issue is, it always disconnects after a few minutes (4-5 min) after the first boot-up. Then after the second boot-up (unplug/plug from/to power source) the connection keeps up the whole time. I always unplug the EA-N66 from the power source at the end of the day, that it does not emit any radiation at night ('cause it is placed in my bedroom). Thus, I have to boot it every day, but every day I have the same issue with the first boot-up. Enclosed you will find my setup:

Code: 
--- RT-N66U ---
Merlin Firmware: 374.42
IP: 192.168.1.1
DHCP Server: enabled
scheduled to disable antennas from 2:00 to 7:00 AM

--- EA-N66 ---
Firmware: 1.0.1.8k
IP: 192.168.1.2 (static)
DHCP Override: disabled

--- PC ---
IP: 192.168.1.3 (static)

--- Other devices ---
Client DHCP enabled

What can cause that issue?

If you need any other information, just ask. Thanks in advance.
 
Last edited:
Same here

Got one of these connected in AP-mode to my second computer. Bought one of these since I run Linux on that computer, and have had on and off sucess with "normal" wireless adapters.

As Obfuscator says, after first boot it runs great for a couple of minutes. Then after 5-10 minutes network traffic stops, and after a while I'll get the error "Lost connection to wired network". The adaptor is still lit up, so I'm guessing it's still connected, and the small lights where you plug in the ethernet cable is still blinking.

Sometimes, but not very often, the connection comes back after a couple of minutes ( 2-5 ). But mostly I just unplug the powercable from the EA-N66, and let it connect again. This time the connection stays stable until I shut down the system, and disconnect the power, until the next time I use that system.

I'm not sure if the EA-N66 loses connection to my wireless, or if loses connection on the wired connection. Since I can't access the unit's GUI/Admin site I'm gussing it's the wired connection:confused:.

Since I don't use that computer on a dayly basis, I never put much time into the problem, since it's easy to "fix" (unplu/plug in), but if there's some real fix for it, that would be terrific:)
 
Nice to hear that I am not the only person with this issue.

Today, I have tried to analyze the issue with telnet (connected to EA-N66 bridge) after the EA-N66 disconnected. The result is that I can ping my PC which is connected by cable with the EA-N66 but I can not ping the router via WLAN. However, iwconfig says that the link quality is good and has the right ESSID. Enclosed are some telnet outputs which could be useful for you:

Code: 
# iwconfig
eth2      no wireless extensions.

lo        no wireless extensions.

ra0       Ralink STA  ESSID:"ANY SSID"  Nickname:"RT3883STA"
          Mode:Managed  Frequency=2.437 GHz  Access Point: D8:50:E6:94:CD:D0
          Bit Rate=117 Mb/s
          RTS thr:off   Fragment thr:off
          Encryption key: ANY ENCRYPTION KEY [2]   Security mode:restricted   Security mode:open
          Link Quality=97/100  Signal level:-68 dBm  Noise level:-94 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

br0       no wireless extensions.

# ifconfig
br0       Link encap:Ethernet  HWaddr AC:22:0B:95:BC:2C
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1354 errors:0 dropped:0 overruns:0 frame:0
          TX packets:904 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:262979 (256.8 KiB)  TX bytes:73877 (72.1 KiB)

eth2      Link encap:Ethernet  HWaddr AC:22:0B:95:BC:2C
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:24609 errors:0 dropped:0 overruns:0 frame:0
          TX packets:33190 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3814279 (3.6 MiB)  TX bytes:28821492 (27.4 MiB)
          Interrupt:3

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING MULTICAST  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

ra0       Link encap:Ethernet  HWaddr AC:22:0B:95:BC:2C
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:42750 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24439 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:31328671 (29.8 MiB)  TX bytes:4815036 (4.5 MiB)
          Interrupt:4

# brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.ac220b95bc2c       no              eth2
                                                        ra0

# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 br0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         0.0.0.0         0.0.0.0         U     0      0        0 br0
 
Hm, I still can not figure out why the EA-N66 hangs for the first 5-10 min. Am I the only one with this issue?

Here is a log of pinging my gateway/router (N66U) with the IP 192.168.1.1 from my PC (static IP: 192.168.1.3) which is connected with the bridge EA-N66 (static IP: 192.168.1.2, DHCP override: off):

Code: 
Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=327ms TTL=64
Reply from 192.168.1.1: bytes=32 time=349ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=68ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=21ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1522ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3125ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=2294ms TTL=64
Reply from 192.168.1.1: bytes=32 time=868ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=66ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=331ms TTL=64
Reply from 192.168.1.1: bytes=32 time=124ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=77ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=76ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=283ms TTL=64
Reply from 192.168.1.1: bytes=32 time=44ms TTL=64
Reply from 192.168.1.1: bytes=32 time=352ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=826ms TTL=64
Reply from 192.168.1.1: bytes=32 time=803ms TTL=64
Reply from 192.168.1.1: bytes=32 time=880ms TTL=64
Reply from 192.168.1.1: bytes=32 time=931ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1380ms TTL=64
Reply from 192.168.1.1: bytes=32 time=927ms TTL=64
Reply from 192.168.1.1: bytes=32 time=787ms TTL=64
Reply from 192.168.1.1: bytes=32 time=695ms TTL=64
Reply from 192.168.1.1: bytes=32 time=894ms TTL=64
Reply from 192.168.1.1: bytes=32 time=893ms TTL=64
Reply from 192.168.1.1: bytes=32 time=779ms TTL=64
Reply from 192.168.1.1: bytes=32 time=850ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1372ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=3356ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=393ms TTL=64
Reply from 192.168.1.1: bytes=32 time=375ms TTL=64
Reply from 192.168.1.1: bytes=32 time=160ms TTL=64
Reply from 192.168.1.1: bytes=32 time=80ms TTL=64
Reply from 192.168.1.1: bytes=32 time=676ms TTL=64
Reply from 192.168.1.1: bytes=32 time=866ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1122ms TTL=64
Reply from 192.168.1.1: bytes=32 time=348ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 130, Received = 98, Lost = 32 (24% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 3356ms, Average = 300ms
Control-C

At the end, the connection remains at a stable state with a good ping. What the heck is going on? Are there so few people with an EA-N66 in this forum?

Btw the ping, at the time the connection to the internet is messed up, from my PC to the bridge is okay. Only from bridge to router, there seems to be an issue. I also checked the link quality to my router at the place of the bridge with my laptop and inSSIDer Home which outputs a score of 95. Hence the link quality should not be the problem.

One issue I could solve in my network was a DHCP issue which caused sometimes limited access notifications on some PCs/laptops with DHCP enabled. Another bridge (Netgear WNCE2001) which is connected on a printer acted as DHCP server which stopped some clients from getting their IP from the router. Now only one DHCP is on my local net, I checked it with the tool "rogue checker".

EDIT: I am still waiting for a new firmware for the EA-N66 which is long overdue.
 
Last edited:
I have inspected the behavior again. My steps:

  • Cleared the router system log via my smartphone. Kept window open and refreshed the log repeatedly.
  • Started my PC, waited until I am on my desktop.
  • Opened console and run `ping 192.168.1.1 -t`.
  • Plugged in the EA-N66 and observed the ping. Additionally I also observed the system log of the EA-N66 in the browser on my PC.

Result: Again same behavior as above (see ping log of previous post). Furthermore I read a log message in the EA-N66 which says:

Code: 
Jan  1 00:09:20  WAN Connection: WAN was exceptionally disconnected.
Jan  1 00:09:22  WAN Connection: WAN was restored.

But that is not true from the viewpoint of the router. The router logged no further messages.

EDIT: The LEDs of the EA-N66 kept on, no blinking.
 
Last edited:
I haven't found any news on the problem, but I thought i would fill in some information.
Like you, I have tried pinging the router. Works ok for a couple of minutes, then it just says "timeout". The connection never came back, had to unplug/plugin the power for it to return.
From my experience, the connection never comes back by itself if I keep trying to load a page/refresh. It's like there has to be no network traffic for it to reconnect:confused:
The adapters lights stay on, and solid, even when it drops the connection.
And like you, I haven't found anything strange in the routers log. Maybe it on the router side?
I have the same one as you (rt-n66u). One thing I found a little strange, is that I gave the adapter its own ip ( not dhcp), but the router doesn't give the ea-66 the ip I specified. Have removed it from the static ip side, but it still disconnects:mad:
I apologise in advance for any spelling or grammatical errors. English is not my first language
 
It's nice to hear that I am not the only one with this issue and if you read the amazon.com reviews some also report it. But ASUS doesn't do anything about it, very sad. The device was not that cheap. So I sent a technical support ticket yesterday to ASUS which points to this thread. I am curious about how or if ASUS will answer to this ticket.
 
You must log in or register to reply here.

Similar threads

L
ASUS RT-AX58U - devices kicked-off wifi over 60 times a day
2
Replies
21
Views
3K
ColinTaylor
C
J
Problem with registering hostname to Asus router
Replies
6
Views
492
ColinTaylor
C
J
Cannot connect to the Guest Network Wifi, Will not Connect to the Guest Network Wifi
Replies
3
Views
413
dave14305
dave14305
R
Asus Tuf AX6000 disconnections
Replies
9
Views
2K
ronins
R
P
Asus zenwifi XT8 not getting 1000mbit connection
Replies
3
Views
622
Philip Rohrhuber
P

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 1,282 (members: 21, guests: 1,261)
Back
Top
✖