[Beta] RT-AC3200_3.0.0.4_378_8868

[poor_poor]

Dear all,

RT-AC3200_3.0.0.4_378_8868 - Unofficial beta

Download: http://goo.gl/ihrlO5

Please let me know if you have any issue on this build.

 

[qsyang]

Dear all,

RT-AC3200_3.0.0.4_378_8868 - Unofficial beta

Download: http://goo.gl/ihrlO5

Please let me know if you have any issue on this build.

Thanks for posting the latest beta builds here! Downloaded file size is only 5.4 megs. Is this right? The one prior - 8597 was 38 megs.

 

[RMerlin]

Thanks for posting the latest beta builds here! Downloaded file size is only 5.4 megs. Is this right? The one prior - 8597 was 38 megs.

It should definitely be larger than 5 MB. Try redownloading it.

 

[T-Nation]

Its 38megs, as RMerlin said, try downloading it again.

 

[qsyang]

Thanks guys. Did try multiple times, but all from office, including one just now. Will try again from home later this evening.

 

[zoomee]

Downloading now - sick of getting trend alerts from the official latest firmware lol.
Anyone notice any bugs so far? ta

 

[poor_poor]

Downloading now - sick of getting trend alerts from the official latest firmware lol.
Anyone notice any bugs so far? ta

What kind if trend alerts are you getting from?

 

[zoomee]

Just browsing hexus.net for example gives me AV alerts. Think its ads related. Used to get it on early firmware but it was fixed in later releases until this last official one bud.

Sent from my D6603 using Tapatalk

 

[poor_poor]

Just browsing hexus.net for example gives me AV alerts. Think its ads related. Used to get it on early firmware but it was fixed in later releases until this last official one bud.

Sent from my D6603 using Tapatalk

Hi Zoomee,

Please provide print screen and we will test.

 

[zoomee]

Event number : 1
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

Event number : 2
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

Event number : 3
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

Event number : 4
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

RT-AC3200's AiProtection detected suspicious networking behavior and prevented your device making a connection to a malicious website (see above and the attached log for details).Suggested actions:
1. If you know that the cause of this attempted connection was a proprietary app or program and not a web browser, we recommand that you uninstall it from your device.
2. Ensure your device is up to time in all its operating system patches as well as updates to all apps or programs.
3. You should take this opportunity to check for, and install, any router firmware updates.
4. If you continue to receive such alerts for similar attempted connections, investigation into the cause will be necessary.
Meanwhile, rest assured that AiProtection continues to help kepp you safe on the Internet.

You also can link to trend micro website to download security trial software for your client device protection.
http://www.trendmicro.com/

ASUS AiProtection FAQ:
http://www.asus.com/support/FAQ/1012070/

 

[poor_poor]

Hi Zoomee,

Are you able to visit the site?

 

[zoomee]

Still happening with this beta firmware - will need to hard reset to ensure its properly cleared down first (hard resetting resolved this issue on one of the early firmwares).

EDIT: Yes site is accessible fine. Just keep getting spammed with this alert whilst on it.

 

[poor_poor]

Still happening with this beta firmware - will need to hard reset to ensure its properly cleared down first (hard resetting resolved this issue on one of the early firmwares).

EDIT: Yes site is accessible fine. Just keep getting spammed with this alert whilst on it.

Hi Zoomee,

Please enter GUI and do restore to factory default.

 

[zoomee]

Just performed a hard reset by holding in the reset button at the back. Restored my settings from backup and still getting the same alert email when visiting hexus.net

AiProtection alert! 2015-09-18 11:15:34

Event number : 1
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

Event number : 2
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

Event number : 3
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

Event number : 4
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

RT-AC3200's AiProtection detected suspicious networking behavior and prevented your device making a connection to a malicious website (see above and the attached log for details).Suggested actions:

 

[raphaelogy]

Just performed a hard reset by holding in the reset button at the back. Restored my settings from backup and still getting the same alert email when visiting hexus.net

AiProtection alert! 2015-09-18 11:15:34

Event number : 1
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

Event number : 2
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

Event number : 3
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

Event number : 4
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

RT-AC3200's AiProtection detected suspicious networking behavior and prevented your device making a connection to a malicious website (see above and the attached log for details).Suggested actions:

I have a similar issue with this firmware, again a lot of aiprotection entries in the log. however, mine was about "sending email to...." when the attack was blocked. so far, no issue with the internet connection apart from the aiprotection entries in the log.

will continue to monitor, especially the smart connect.

 

[qsyang]

It should definitely be larger than 5 MB. Try redownloading it.

It was fine for the download from home. The draining of battery with my S5 appeared to have gone as well. We shall see. Thanks again.

 

[RMerlin]

Just performed a hard reset by holding in the reset button at the back. Restored my settings from backup and still getting the same alert email when visiting hexus.net

AiProtection alert! 2015-09-18 11:15:34

Event number : 1
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

Event number : 2
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

Event number : 3
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

Event number : 4
Alert type : Malicious Sites Blocking
Source : Shaba-Laptop (A4:17:31:21:83:F9)
Destination : node.adspdbl.com

RT-AC3200's AiProtection detected suspicious networking behavior and prevented your device making a connection to a malicious website (see above and the attached log for details).Suggested actions:

After visiting the website, please connect with your router over SSH, and run the following command:

bwdpi wrs_url

Post the output here. I will make sure this info is forwarded to the Asus engineer who handles the DPI engine.

 

[zoomee]

1442572724 A4:17:31:21:83:F9 40 Accept en-gb.appex-rf.msn.com
1442572724 A4:17:31:21:83:F9 40 Accept en-gb.appex-rf.msn.com
1442572724 A4:17:31:21:83:F9 40 Accept en-gb.appex-rf.msn.com
1442572724 A4:17:31:21:83:F9 40 Accept en-gb.appex-rf.msn.com
1442571767 A4:17:31:21:83:F9 40 Accept www.google.co.uk
1442571767 A4:17:31:21:83:F9 40 Accept www.google.com
1442571681 A4:17:31:21:83:F9 88 Accept ir-na.amazon-adsystem.co m
1442571680 A4:17:31:21:83:F9 88 Accept z-na.amazon-adsystem.com
1442571680 A4:17:31:21:83:F9 88 Accept z-na.amazon-adsystem.com
1442571680 A4:17:31:21:83:F9 88 Accept ws-na.amazon-adsystem.co m
1442571678 A4:17:31:21:83:F9 88 Accept vma.tgdaily.net
1442571675 A4:17:31:21:83:F9 88 Accept ir-na.amazon-adsystem.co m
1442571675 A4:17:31:21:83:F9 88 Accept ws-na.amazon-adsystem.co m
1442571673 A4:17:31:21:83:F9 41 Accept aax-us-east.amazon-adsys tem.com
1442571673 A4:17:31:21:83:F9 88 Accept ws-na.amazon-adsystem.co m
1442571673 A4:17:31:21:83:F9 88 Accept z-na.amazon-adsystem.com
1442571673 A4:17:31:21:83:F9 88 Accept z-na.amazon-adsystem.com
1442571673 A4:17:31:21:83:F9 88 Accept vma.tgdaily.net
1442571672 A4:17:31:21:83:F9 88 Accept vma.tgdaily.net
1442571671 A4:17:31:21:83:F9 88 Accept vma.tgdaily.net
1442571671 A4:17:31:21:83:F9 88 Accept vma.tgdaily.net
1442571636 A4:17:31:21:83:F9 41 Accept aax-us-east.amazon-adsys tem.com
1442571569 A4:17:31:21:83:F9 88 Accept cm.g.doubleclick.net
1442571569 A4:17:31:21:83:F9 88 Accept ir-na.amazon-adsystem.co m
1442571568 A4:17:31:21:83:F9 88 Accept ws-na.amazon-adsystem.co m
1442571568 A4:17:31:21:83:F9 88 Accept cm.g.doubleclick.net
1442571568 A4:17:31:21:83:F9 88 Accept cm.g.doubleclick.net
1442571568 A4:17:31:21:83:F9 41 Accept aax-us-east.amazon-adsys tem.com
1442571568 A4:17:31:21:83:F9 50 Accept static.ak.facebook.com
1442571568 A4:17:31:21:83:F9 50 Accept static.ak.facebook.com
1442571567 A4:17:31:21:83:F9 50 Accept platform.twitter.com
1442571567 A4:17:31:21:83:F9 88 Accept pagead2.googlesyndicatio n.com
1442571567 A4:17:31:21:83:F9 88 Accept pagead2.googlesyndicatio n.com
1442571567 A4:17:31:21:83:F9 88 Accept ws-na.amazon-adsystem.co m
1442571567 A4:17:31:21:83:F9 88 Accept z-na.amazon-adsystem.com
1442571567 A4:17:31:21:83:F9 88 Accept z-na.amazon-adsystem.com
1442571567 A4:17:31:21:83:F9 88 Accept pagead2.googlesyndicatio n.com
1442571566 A4:17:31:21:83:F9 88 Accept s.moatads.com
1442571566 A4:17:31:21:83:F9 88 Accept s.moatads.com
1442571566 A4:17:31:21:83:F9 88 Accept pagead2.googlesyndicatio n.com
1442571566 A4:17:31:21:83:F9 88 Accept s.moatads.com
1442571566 A4:17:31:21:83:F9 88 Accept vma.tgdaily.net
1442571566 A4:17:31:21:83:F9 88 Accept pagead2.googlesyndicatio n.com
1442571566 A4:17:31:21:83:F9 88 Accept js.moatads.com
1442571566 A4:17:31:21:83:F9 88 Accept pagead2.googlesyndicatio n.com
1442571566 A4:17:31:21:83:F9 88 Accept pagead2.googlesyndicatio n.com
1442571565 A4:17:31:21:83:F9 88 Accept vma.tgdaily.net
1442571564 A4:17:31:21:83:F9 88 Accept vma.tgdaily.net
1442571564 A4:17:31:21:83:F9 88 Accept z-na.amazon-adsystem.com
1442571564 A4:17:31:21:83:F9 88 Accept pagead2.googlesyndicatio n.com
1442571339 A4:17:31:21:83:F9 40 Accept www.google.co.uk
1442571339 A4:17:31:21:83:F9 40 Accept www.google.co.uk
1442571338 A4:17:31:21:83:F9 40 Accept www.google.com
1442571319 A4:17:31:21:83:F9 86 Block node.adspdbl.com
1442571319 A4:17:31:21:83:F9 86 Block node.adspdbl.com
1442571319 A4:17:31:21:83:F9 86 Block node.adspdbl.com
1442571319 A4:17:31:21:83:F9 86 Block node.adspdbl.com
1442571318 A4:17:31:21:83:F9 88 Accept files.adspdbl.com
1442571318 A4:17:31:21:83:F9 88 Accept files.adspdbl.com
1442571318 A4:17:31:21:83:F9 88 Accept files.adspdbl.com
1442571226 30:75:12:7B:2C:CF 40 Accept clients3.google.com
1442571225 30:75:12:7B:2C:CF 40 Accept clients3.google.com
1442571224 30:75:12:7B:2C:CF 40 Accept clients3.google.com
1442571224 30:75:12:7B:2C:CF 40 Accept clients3.google.com

 

[RMerlin]

1442571319 A4:17:31:21:83:F9 86 Block node.adspdbl.com
1442571319 A4:17:31:21:83:F9 86 Block node.adspdbl.com
1442571319 A4:17:31:21:83:F9 86 Block node.adspdbl.com
1442571319 A4:17:31:21:83:F9 86 Block node.adspdbl.com
1442571318 A4:17:31:21:83:F9 88 Accept files.adspdbl.com
1442571318 A4:17:31:21:83:F9 88 Accept files.adspdbl.com
1442571318 A4:17:31:21:83:F9 88 Accept files.adspdbl.com

Thank you. Those are the interesting lines here.

I've pointed Asus at this thread, so hopefully they can take a look at it next week (it's already the weekend in Taiwan).

 

[Puppa]

Those errors might be legitimate, FWIW. I've had a number of popular sites in the past week with infected ads. Turning off the Trend Micro stuff then allowed them through, and Symantec caught them. Infected devices, however, is another story, at least it was a few months ago, and I suspect TM might have gotten pwn'd by the Kaspersky false reports they put out there designed to make competitor's products malfunction, as reported on several security blogs.