[Maylyn's Review] ASUS RT-AC87U

[renfred89]

So u never dump the 87U in the end right ?.....

I was deciding the unit past few days ... and drop by Challenger 3 times to check out other routers.

on 29 Dec , I can count it have about 7 units of AC87U , 2 units of X6 and 4 units of WRT1900, plenty of Axtech 2400.

Yesterday I pick up the last unit of AC87U, the 2x X6 , 4x WRT all still there .

I guess the choice is very clear...

By the way I cannot find the CPU Temp in the configuration pages.... still finding... I can only see the load...

you can only see the temperature using telnet.

i didn't dump it. just let it rest in the box for a while and i tested on other routers..

Wah u monitor the stock level? LOL

 

[trichard]

..............

Yeah ... I believe from 29Dec (night time) to 1Jan ot much chance to restock ..
hence the stock at the shelf should be a good count of how much people buying.

I have tested DIR 880 / Aztech 2400.

The coverage range is really ..... the Au87U is at siting room. I close my Master room dooor and go into the master room toliet, close the door also (over 2 walls )... and at extreme corner.....

The previous 2 no more signal ... this one still can get 2 bar ..........

 

[renfred89]

..............

Yeah ... I believe from 29Dec (night time) to 1Jan ot much chance to restock ..
hence the stock at the shelf should be a good count of how much people buying.

I have tested DIR 880 / Aztech 2400.

The coverage range is really ..... the Au87U is at siting room. I close my Master room dooor and go into the master room toliet, close the door also (over 2 walls )... and at extreme corner.....

The previous 2 no more signal ... this one still can get 2 bar ..........

you're the second guy who tested the coverage in toilet...

why do you need internet access in toilet???

Aztech 2400? you mean aztech 7008 is it? I'm waiting to lay my hands on it and test the performance. Internal antennas are always weaker than your 4 external antennas of ac87u...

 

[trichard]

you're the second guy who tested the coverage in toilet...

why do you need internet access in toilet???

Aztech 2400? you mean aztech 7008 is it? I'm waiting to lay my hands on it and test the performance. Internal antennas are always weaker than your 4 external antennas of ac87u...

Watch Youtube while doing business ..........

Yes Aztech 2400 ... signal strength is similar to the DIR 868 if you test before (at least for my home infrastructure)

But 5Ghz does not have 80Mhz BW (I tested DIR865 / 868 / 880 and this setting can be adjusted 20Mhz/40Mhz/80Mhz , but Aztech cannot find this setting for 80Mhz , only can find 20Mhz for 2.4Ghz and 40Mhz for 5Ghz) . I tested the download speed on S5/Note3/XMNOTE4G all cannot reached the speed of 868 even....

I guess can give this Aztech a miss....

 

[Dr_ARCHer]

why do you need internet access in toilet???

My wife don't like me to play games when the kids are around. The toilet is the only place where I get to play. Bring my tablet in and stay there for half an hour.

And my kids think I always have diarrhea because I do this several times a day.

 

[trichard]

My wife don't like me to play games when the kids are around. The toilet is the only place where I get to play. Bring my tablet in and stay there for half an hour.

And my kids think I always have diarrhea because I do this several times a day.

................

I have found a issue with the AC86U with the latest official FW.

On my Dell Office laptop E6230 , the SSID will suddenly disappear ... .and reappear after a few second ... breaking my VPN .

not sure it is the laptop ..... no chance to verify on the phone did the SSID also disappear or not...


Updated : Ok my Toshiba first time encounter limited connection on 5ghz .... disconnect and reconnect back good....

I read a post that set to AP will resolve 5ghz issue .... But not true I am in AP mode ..

 

[BadEnglish]

Latest firmware Same old problem

Wasted 2 hrs of configuration and testing time.
Latest 3.0.0.4.378_3754 official firmware still have the same bug.

Upgraded firmware:
Reset Router
Configure


Jan 2 18:02:27 kernel: br0: received packet on eth1 with own address as source address
Jan 2 18:03:09 kernel: br0: received packet on eth1 with own address as source address
Jan 2 18:09:47 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:47 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:47 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:47 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:48 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:48 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:48 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:48 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:49 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:49 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:05 kernel: net_ratelimit: 6 callbacks suppressed
Jan 2 18:12:05 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:05 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:05 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:05 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:05 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:06 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:06 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:06 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:06 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:07 kernel: br0: received packet on vlan1 with own address as source address



How many more hours of my time is need to work this over rated router ?

 

[kevincheong]

Got the same problems with the new FW ........
Firmware Version:3.0.0.4.378_3754

Jan 1 23:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 00:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 01:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 01:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 01:36:42 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 01:36:43 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 01:36:45 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 01:36:47 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 02:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 03:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 03:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 04:36:39 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 05:36:38 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 05:36:38 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:37 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:39 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:40 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:42 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:44 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:46 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:48 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:50 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:38 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:39 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:40 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:42 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:43 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:44 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:45 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 08:37:22 ntp: start NTP update
Jan 2 14:36:39 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 14:36:40 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 14:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 14:36:42 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 14:36:43 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 14:36:44 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 14:36:45 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 14:36:46 kernel: br0: received packet on vlan1 with own address as source address

 

[renfred89]

Wasted 2 hrs of configuration and testing time.
Latest 3.0.0.4.378_3754 official firmware still have the same bug.

Upgraded firmware:
Reset Router
Configure


Jan 2 18:02:27 kernel: br0: received packet on eth1 with own address as source address
Jan 2 18:03:09 kernel: br0: received packet on eth1 with own address as source address
Jan 2 18:09:47 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:47 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:47 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:47 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:48 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:48 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:48 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:48 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:49 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:49 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:05 kernel: net_ratelimit: 6 callbacks suppressed
Jan 2 18:12:05 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:05 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:05 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:05 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:05 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:06 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:06 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:06 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:06 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:07 kernel: br0: received packet on vlan1 with own address as source address



How many more hours of my time is need to work this over rated router ?

this is something new. i don't have this in my log..

 

[ASUS@SG]

Dear all,

We are working on new firmware to resolve vlan loop issue.

Best regard,
JK

 

[topcow75]

Dear all,

We are working on new firmware to resolve vlan loop issue.

Best regard,
JK[/QUOTE/]

Why like that?

Jan 2 18:02:30 RT-AC87U: start httpd
Jan 2 18:02:30 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jan 2 18:02:30 kernel: klogd started: BusyBox v1.17.4 (2014-12-26 15:58:02 CST)
Jan 2 18:03:12 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Jan 2 18:03:12 kernel: sizeof forward param = 160
Jan 2 18:03:27 kernel: Stop the IPS/AppID engine...
Jan 2 18:03:27 kernel: Stop the IPS/AppID engine...
Jan 2 20:00:25 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 20:00:25 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 20:00:26 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 20:00:26 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 20:00:27 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 20:00:27 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 20:00:29 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 20:00:29 kernel: br0: received packet on vlan1 with own

 

[maylyn]

Wasted 2 hrs of configuration and testing time.
Latest 3.0.0.4.378_3754 official firmware still have the same bug.

Upgraded firmware:
Reset Router
Configure


Jan 2 18:02:27 kernel: br0: received packet on eth1 with own address as source address
Jan 2 18:03:09 kernel: br0: received packet on eth1 with own address as source address
Jan 2 18:09:47 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:47 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:47 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:47 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:48 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:48 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:48 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:48 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:49 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:09:49 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:05 kernel: net_ratelimit: 6 callbacks suppressed
Jan 2 18:12:05 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:05 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:05 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:05 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:05 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:06 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:06 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:06 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:06 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 18:12:07 kernel: br0: received packet on vlan1 with own address as source address

How many more hours of my time is need to work this over rated router ?

Got the same problems with the new FW ........
Firmware Version:3.0.0.4.378_3754

Jan 1 23:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 00:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 01:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 01:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 01:36:42 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 01:36:43 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 01:36:45 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 01:36:47 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 02:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 03:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 03:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 04:36:39 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 05:36:38 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 05:36:38 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:37 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:39 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:40 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:42 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:44 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:46 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:48 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 06:36:50 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:38 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:39 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:40 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:42 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:43 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:44 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 07:36:45 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 08:37:22 ntp: start NTP update
Jan 2 14:36:39 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 14:36:40 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 14:36:41 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 14:36:42 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 14:36:43 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 14:36:44 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 14:36:45 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 14:36:46 kernel: br0: received packet on vlan1 with own address as source address

Dear all,

We are working on new firmware to resolve vlan loop issue.

Best regard,
JK

Why like that?

Jan 2 18:02:30 RT-AC87U: start httpd
Jan 2 18:02:30 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jan 2 18:02:30 kernel: klogd started: BusyBox v1.17.4 (2014-12-26 15:58:02 CST)
Jan 2 18:03:12 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Jan 2 18:03:12 kernel: sizeof forward param = 160
Jan 2 18:03:27 kernel: Stop the IPS/AppID engine...
Jan 2 18:03:27 kernel: Stop the IPS/AppID engine...
Jan 2 20:00:25 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 20:00:25 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 20:00:26 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 20:00:26 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 20:00:27 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 20:00:27 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 20:00:29 kernel: br0: received packet on vlan1 with own address as source address
Jan 2 20:00:29 kernel: br0: received packet on vlan1 with own

Please refer to the quoted. ASUS TW RD are working hard getting it fixed and resolved.

Just got this!

Dec 31 17:29:12 kernel: br0: received packet on vlan1 with own address as source address

So I guess not. Better luck in the new year.

You are confusing two completely different issues.

The "Dead loop on virtual device vlan2, fix it urgently" error (note the different wording) was an issue that was specific to the RT-AC87U. This is the issue that Asus fixed in this build.

What you are experiencing is about a packet having identical source and destinations - that issue has been in the firmware for years, and has not been fixed by Asus yet.

Really, for years? When this problem occurs on my AC87 in AP mode my LAN goes completly down. Do you mean customers have been living with this issue for years? I'm already fed up after a few weeks!

I hope to change my routers for a Netgear next week, due to the NY period the RMA service is slowed down in the shop where I bought the units. Never ASUS again!

But I liked your modifications and added features to the original FW, hope ASUS will solve this issue in 2015.

Now i now its nothing to worry about i am happy, good luck with Negear i moved to Asus because the Asus routers are far better supported.

It took a while for the N66 firmware to mature, just give Asus a chance with the AC87,

Regards

PS RMerlin, thanks for the .5 update

Not necessarily, a simple web search shows that this message has appeared quite often over the years. Often in relation to people using virtual machines and appears to be related to MAC addresses assigned to them resulting the broadcast MAC address (I'm not clear on this) being the same for multiple interfaces.

If there are no virtual machines involved the impression is that the warning is harmless but when vms are involved people have reported broadcast storms.

So it might not be a problem for most routers but I believe the 87U runs a separate independent sub-system for the 5Ghz wireless so perhaps that is similar to running a vm and is a problem for the 87U.

But in reality I'm just guessing from a few posts I read.

They aren't necessarily related to one another. I occasionally get these in my own router log as well, but it never affected connectivity.

Source ~> SmallNetBuilder Forums - View Single Post - ASUS RT-AC87 Firmware - Official Releases

SmallNetBuilder Forums - View Single Post - ASUS RT-AC87 Firmware - Official Releases

SmallNetBuilder Forums - View Single Post - ASUS RT-AC87 Firmware - Official Releases

SmallNetBuilder Forums - View Single Post - ASUS RT-AC87 Firmware - Official Releases

 

[trichard]

Dear all,

We are working on new firmware to resolve vlan loop issue.

Best regard,
JK

Hi There

I guess the missing 5G SSID and Limited connection still not yet have solution so soon ?

 

[ankhazam]

Now I'm getting a little bit irritated.
Did a wipe, manually re-input all the settings for the latest stable firmware and even though, every 24 hours - after my ISP's forced, remote PPPOE WAN disconnect the router reboots!!!

 

[trichard]

Anyone know how to manually set the time / date of the 86U instead of the NTP ?

 

[garyng08]

Anyone did any setting for the Asus Download Master. I am using the default FW: 3.0.0.4.376_2769 on my AC87. The BT download speed is damn slow. Any tweak to help?

 

[thiamhui]

Anyone know how to manually set the time / date of the 86U instead of the NTP ?

Just remove the NTP server, I think…

 

[phayze]

If we were to resetup everytime we upgrade or hard reset, Asus should remove the save settings option. The setting is no use even we backup/save settings.

It is very troublesome if we resetup everytime when we upgrade/update firmware.

But still you can't restore from saved settings..

 

[ASUS@SG]

If we were to resetup everytime we upgrade or hard reset, Asus should remove the save settings option. The setting is no use even we backup/save settings.

It is very troublesome if we resetup everytime when we upgrade/update firmware.

Dear phayze,

Only for major upgrade firmware then require hard reset.

374 to 376 < Require hard reset>
374 to 374 < Don't need to hard reset, unless driver recommend hard reset.>

A special firmware is design to test Vlan loop issue and we still testing on the root cause.

We will release a unofficial beta firmware to solve Vlan loop soon.

Best regard,
JK

 

[trichard]

The limited connection at laptop due to the laptop WiFi card driver?