[Maylyn's Review] ASUS RT-AC87U

legolaz

Member
Joined
Aug 4, 2010
Messages
107
Reaction score
0
Just happened again. Lost internet connection and I checked system log. 17:54 was when I lost Internet connection. This time though I had to restart router for it to work.

ec 27 17:53:15 rc_service: ntp 538:notify_rc restart_diskmon
Dec 27 17:53:15 rc_service: waitting "start_dnsmasq" via ...
Dec 27 17:53:29 rc_service: skip the event: restart_diskmon.
Dec 27 17:53:57 RT-AC87U: start httpd
Dec 27 17:53:57 disk monitor: be idle
Dec 27 17:53:58 syslog: Generating SSL certificate...
Dec 27 17:54:01 kernel: br0: received packet on eth1 with own address as source address
Dec 27 17:54:06 qtn: bootcfg.tgz exists
Dec 27 17:54:19 rc_service: udhcpc_lan 632:notify_rc start_dnsmasq
Dec 27 17:54:19 ntp: start NTP update
 

oric1

Senior Member
Joined
Dec 2, 2001
Messages
1,663
Reaction score
17
Just happened again. Lost internet connection and I checked system log. 17:54 was when I lost Internet connection. This time though I had to restart router for it to work.

ec 27 17:53:15 rc_service: ntp 538:notify_rc restart_diskmon
Dec 27 17:53:15 rc_service: waitting "start_dnsmasq" via ...
Dec 27 17:53:29 rc_service: skip the event: restart_diskmon.
Dec 27 17:53:57 RT-AC87U: start httpd
Dec 27 17:53:57 disk monitor: be idle
Dec 27 17:53:58 syslog: Generating SSL certificate...
Dec 27 17:54:01 kernel: br0: received packet on eth1 with own address as source address
Dec 27 17:54:06 qtn: bootcfg.tgz exists
Dec 27 17:54:19 rc_service: udhcpc_lan 632:notify_rc start_dnsmasq
Dec 27 17:54:19 ntp: start NTP update

Maybe you want to try getting help from SNB Forum, lots of gurus there and dedicated forum for ASUS Routers.
 

ASUS@SG

Suspended
Joined
Jul 26, 2011
Messages
7,581
Reaction score
3
Just happened again. Lost internet connection and I checked system log. 17:54 was when I lost Internet connection. This time though I had to restart router for it to work.

ec 27 17:53:15 rc_service: ntp 538:notify_rc restart_diskmon
Dec 27 17:53:15 rc_service: waitting "start_dnsmasq" via ...
Dec 27 17:53:29 rc_service: skip the event: restart_diskmon.
Dec 27 17:53:57 RT-AC87U: start httpd
Dec 27 17:53:57 disk monitor: be idle
Dec 27 17:53:58 syslog: Generating SSL certificate...
Dec 27 17:54:01 kernel: br0: received packet on eth1 with own address as source address
Dec 27 17:54:06 qtn: bootcfg.tgz exists
Dec 27 17:54:19 rc_service: udhcpc_lan 632:notify_rc start_dnsmasq
Dec 27 17:54:19 ntp: start NTP update

Dear legolaz,

What is your main router? and ISP

Best regard,
JK
 

achui

Member
Joined
Jul 17, 2001
Messages
242
Reaction score
0
you mentioned that you are using it as AP, meaning you are cascading from a primary router? A few things to check, if you are using two Wifis (1 router and 1 AP) ...make sure that both the wifi do not use the same channels...you can set the same SSID and password but not the same channels ( for both 2.4 and 5 bands).

And how are the 2 wifis connected...via wire/lan cable?
 

arachnida

Junior Member
Joined
Dec 18, 2014
Messages
12
Reaction score
0
you mentioned that you are using it as AP, meaning you are cascading from a primary router? A few things to check, if you are using two Wifis (1 router and 1 AP) ...make sure that both the wifi do not use the same channels...you can set the same SSID and password but not the same channels ( for both 2.4 and 5 bands).

And how are the 2 wifis connected...via wire/lan cable?

My setup:
Internet -- ISP router -- 87U (as router) -- 87U (as AP) ** WIFI ** iPads and other stuff

On both 87U the NAT accel has been disabled. My basement router has both radios OFF, my AP has both radios ON.

Problem is still the same:

after a few minutes the AP starts slowing down my entire network making my SonoS go nuts and my IP Cams disconnect from the Synology NAS. Also surfing the internet slows down or isn't possible anymore. If I reconnect my old Zyxel AP it works like a charm. So the 87U in AP mode is causing the problems.

The log gets full of :
Dec 27 16:38:35 kernel: net_ratelimit: 726586 callbacks suppressed
Dec 27 16:38:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:40 kernel: net_ratelimit: 707251 callbacks suppressed
Dec 27 16:38:40 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:40 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:40 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:40 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:40 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:40 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:40 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:40 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:40 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:40 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:45 kernel: net_ratelimit: 732187 callbacks suppressed
Dec 27 16:38:45 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:45 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:45 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:45 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:45 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:45 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:45 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:45 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:45 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:45 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:50 kernel: net_ratelimit: 731059 callbacks suppressed
Dec 27 16:38:50 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:50 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:50 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:50 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:50 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:50 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:50 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:50 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:50 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:50 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:55 kernel: net_ratelimit: 731915 callbacks suppressed
Dec 27 16:38:55 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:55 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:55 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:55 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:55 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:55 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:55 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:55 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:55 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:38:55 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:00 kernel: net_ratelimit: 732229 callbacks suppressed
Dec 27 16:39:00 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:00 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:00 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:00 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:00 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:00 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:00 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:00 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:00 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:00 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:05 kernel: net_ratelimit: 731806 callbacks suppressed
Dec 27 16:39:05 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:05 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:05 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:05 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:05 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:05 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:05 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:05 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:05 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:05 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:10 kernel: net_ratelimit: 731372 callbacks suppressed
Dec 27 16:39:10 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:10 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:10 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:10 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:10 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:10 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:10 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:10 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:10 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:10 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:15 kernel: net_ratelimit: 732282 callbacks suppressed
Dec 27 16:39:15 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:15 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:15 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:15 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:15 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:15 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:15 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:15 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:15 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:15 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:20 kernel: net_ratelimit: 731104 callbacks suppressed
Dec 27 16:39:20 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:20 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:20 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:20 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:20 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:20 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:20 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:20 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:20 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:20 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:25 kernel: net_ratelimit: 731107 callbacks suppressed
Dec 27 16:39:25 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:25 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:25 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:25 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:25 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:25 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:25 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:25 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:25 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:25 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:30 kernel: net_ratelimit: 729668 callbacks suppressed
Dec 27 16:39:30 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:30 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:30 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:30 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:30 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:30 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:30 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:30 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:30 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:30 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:35 kernel: net_ratelimit: 477219 callbacks suppressed
Dec 27 16:39:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:39:35 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:46:13 kernel: net_ratelimit: 913 callbacks suppressed
Dec 27 16:46:13 kernel: br0: received packet on vlan1 with own address as source address
Dec 27 16:59:59 ntp: start NTP update
 
Last edited:

legolaz

Member
Joined
Aug 4, 2010
Messages
107
Reaction score
0
1) Aztech 7003
2) Singtel 300 or 500 (can't remember but it's the 2nd fastest)
3) yup using different channels
4) connected via lan cables and a switch

Didn't have a problem previously. Only when I switched to the new router. So I doubt it's an overall setup issue. Thx.
 

renderking

Junior Member
Joined
Dec 28, 2014
Messages
8
Reaction score
0
Similar problem here with the network loops... running (2) RT-AC87R's. First one is set to wireless router mode (directly connected to modem). Second one is configured to AP mode only. Both are showing the following error: "kernel: br0: received packet on vlan1 with own address as source address" hundreds of times. It gets gradually worse with time. Network acts like there's a loop on the network, slowing down over the course of a few hours, and eventually killing Internet access before physical intervention required (reboot).

Running latest stable release on both: Version 3.0.0.4.376.2769

Took a chance on Asus here, but am thinking I may have made a mistake after stumbling onto this forum and reading other's comments.

Sonos devices on network if that matters. Any ideas? The network isn't my own, and all i have is remote access too.

-very frustrated.
 

Farish

Member
Joined
Sep 23, 2008
Messages
388
Reaction score
20
Getting the same error with Merlin 376.49

Dec 28 13:16:02 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:02 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:02 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:02 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:02 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:03 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:03 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:04 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:04 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:05 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:07 kernel: net_ratelimit: 3 callbacks suppressed
Dec 28 13:16:07 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:07 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:08 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:08 kernel: br0: received packet on vlan1 with own address as source address

Mine is just a simple network with only 1 router, 1 NAS and 1 Atlas RIPE on wired connection. Hmmm?
 

renfred89

Arch-Supremacy Member
Joined
Nov 11, 2007
Messages
17,520
Reaction score
17
Dec 28 13:16:02 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:02 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:02 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:02 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:02 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:03 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:03 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:04 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:04 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:05 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:07 kernel: net_ratelimit: 3 callbacks suppressed
Dec 28 13:16:07 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:07 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:08 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 13:16:08 kernel: br0: received packet on vlan1 with own address as source address

Mine is just a simple network with only 1 router, 1 NAS and 1 Atlas RIPE on wired connection. Hmmm?

I dont even have a NAS. And my router runs from ONT. also have that identical entries in my log..
 

ASUS@SG

Suspended
Joined
Jul 26, 2011
Messages
7,581
Reaction score
3
Similar problem here with the network loops... running (2) RT-AC87R's. First one is set to wireless router mode (directly connected to modem). Second one is configured to AP mode only. Both are showing the following error: "kernel: br0: received packet on vlan1 with own address as source address" hundreds of times. It gets gradually worse with time. Network acts like there's a loop on the network, slowing down over the course of a few hours, and eventually killing Internet access before physical intervention required (reboot).

Running latest stable release on both: Version 3.0.0.4.376.2769

Took a chance on Asus here, but am thinking I may have made a mistake after stumbling onto this forum and reading other's comments.

Sonos devices on network if that matters. Any ideas? The network isn't my own, and all i have is remote access too.

-very frustrated.

Dear rederking,

Are you from Smallnetbuilder? Please take note: RT-AC87R not from local Singapore and you might need to check with your local ASUS support team for R model.

We are looking into loop VLAN1 problem and we will resolve it asap.

Meanwhile i would recommend you try our latest unofficial beta firmware.

Unofficial beta firmware: RT-AC87U_3.0.0.4_378_3754

* Hard reset required

Download: http://bit.ly/1Eow3jL

Thank you

Best regard,
JK
 
Last edited:

seowbin

Great Supremacy Member
Joined
Oct 10, 2001
Messages
70,826
Reaction score
463
interesting.. i also kanna , i tot my network got loop but simply too lazy and can't be bothered but apparently a lot of ppl have the same issue :s13:

I have ONT - Asus - HP gigabit switch

Dec 28 13:16:04 kernel: br0: received packet on vlan1 with own address as source address
 

achui

Member
Joined
Jul 17, 2001
Messages
242
Reaction score
0
My setup:
Internet -- ISP router -- 87U (as router) -- 87U (as AP) ** WIFI ** iPads and other stuff

On both 87U the NAT accel has been disabled. My basement router has both radios OFF, my AP has both radios ON.

Problem is still the same:

after a few minutes the AP starts slowing down my entire network making my SonoS go nuts and my IP Cams disconnect from the Synology NAS. Also surfing the internet slows down or isn't possible anymore. If I reconnect my old Zyxel AP it works like a charm. So the 87U in AP mode is causing the problems.

The log gets full of :


Can you confirm that both WiFi are NOT on the same channel? Check for both bands. I have a similar set up too..with 2x AC66U.. 1 as a router and 1 as an AP. I was seeing a lot of these similar messages until i checked and made sure that both wifis are on different channels... I'm seeing way less now. Could you check yours and proof my hunch/theory?
 

arachnida

Junior Member
Joined
Dec 18, 2014
Messages
12
Reaction score
0
Can you confirm that both WiFi are NOT on the same channel? Check for both bands. I have a similar set up too..with 2x AC66U.. 1 as a router and 1 as an AP. I was seeing a lot of these similar messages until i checked and made sure that both wifis are on different channels... I'm seeing way less now. Could you check yours and proof my hunch/theory?

Hello,

my first internet router firewall in the basement, not used as AP, has both radios OFF. The only router sending out signals on the 2.4 and 5 GHz band is the one configured as AP in my living room. (Different SSIDs.)

If I put my Zyxel AP in place of the ASUS AP I don't get these messages, same channel (7), same SSID but only 2.4 GHz hence the reason I wanted to upgrade to a simultanious dual band AP.

Even without the ASUS AP connected I sometimes, but very rare, see the same loop message in the log of the firewall router. But when it occurs it is only one or two messages, not hunderds.

regards,
arachnida
 

legolaz

Member
Joined
Aug 4, 2010
Messages
107
Reaction score
0
For me the main problem is the loss of Internet connection even though device is still connected to the wifi. On reconnection, it will than work again.
 

ahduck

Member
Joined
Sep 26, 2007
Messages
255
Reaction score
2
I'm still getting bootloop issues after updating to Merlin's latest 376.49.4

Not sure why there is also a (694) But that is my iPad2.

There are total of 4 PCs, 1 laptop, 3 Samsung Androids, 1 Blackberry and the 1 iPad which is the only device with the dhcp log.

But at least this version, I not encountering any freezing of streaming video from server. any older version of Merlin's, Asus Stable or Beta I do encounter freezing or skipping just like Youtube buffering videos.

gtFdskL.jpg
 

ASUS@SG

Suspended
Joined
Jul 26, 2011
Messages
7,581
Reaction score
3
Hi,
I understand that after hard reset (the WPS button reset?) we are ok to import the settings downloaded from the router before upgrade?

Regards

Dear ankhazam,

I won't recommend you restore your setting file from older firmware.

Why don't screenshot all the configure settings?

Some code or settings will be change during firmware update, unless you are restore setting from same version of firmware.

Best regard,
JK
 

Farish

Member
Joined
Sep 23, 2008
Messages
388
Reaction score
20
Getting same error after upgrading to Merlin 376.49_4

Dec 28 20:18:22 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:22 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:22 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:24 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:25 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:26 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:27 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:28 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:29 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 21:18:22 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 22:18:21 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 23:18:19 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:16 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:16 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:16 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:16 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:16 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:17 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:17 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:18 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:19 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:21 kernel: net_ratelimit: 2 callbacks suppressed
Dec 29 00:18:21 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:21 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:22 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:23 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:25 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:27 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 01:18:15 kernel: br0: received packet on vlan1 with own address as source address

Was hoping the _4 solved the problem. :(
 

renderking

Junior Member
Joined
Dec 28, 2014
Messages
8
Reaction score
0
Dec 28 20:18:22 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:22 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:22 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:24 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:25 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:26 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:27 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:28 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 20:18:29 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 21:18:22 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 22:18:21 kernel: br0: received packet on vlan1 with own address as source address
Dec 28 23:18:19 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:16 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:16 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:16 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:16 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:16 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:17 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:17 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:18 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:19 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:21 kernel: net_ratelimit: 2 callbacks suppressed
Dec 29 00:18:21 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:21 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:22 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:23 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:25 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 00:18:27 kernel: br0: received packet on vlan1 with own address as source address
Dec 29 01:18:15 kernel: br0: received packet on vlan1 with own address as source address

Was hoping the _4 solved the problem. :(

Thanks for sharing your results. C'mon Asus, I can be understanding to some of the 'premium' features having kinks initially, but the overall basic routing features should always be rock solid at this price point. A router at a fraction of this cost is more stable out of the box than what I've been experiencing with this "flagship model". /rant over :mad:
 
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ. Forum members and moderators are responsible for their own posts.

Please refer to our Community Guidelines and Standards, Terms of Service and Member T&Cs for more information.
Top