[RT-AC68U] A dose of Quicksilver

[Dijkstra88]

Asus released a tool to make the ddr ram speed to work from 555mhz to 666 mhz. Just used the update tool and it worked. Look for it at utilities. You must install first the latest firmware (306)

 

[ronan_zj]

Asus released a tool to make the ddr ram speed to work from 555mhz to 666 mhz. Just used the update tool and it worked. Look for it at utilities. You must install first the latest firmware (306)

Do you feel anything different when you overclock to 666?

 

[delancyst]

I gave it another go with USB3.0 Interference disabled, still no luck.
The hdd powers up together momentarily with the router during the boot process, and would stay off afterwards - showing no USB devices detected.

Jan 1 08:00:11 kernel: JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
Jan 1 08:00:11 kernel: usbcore: registered new interface driver usbfs
Jan 1 08:00:11 kernel: usbcore: registered new interface driver hub
Jan 1 08:00:11 kernel: usbcore: registered new device driver usb
Jan 1 08:00:11 kernel: SCSI subsystem initialized
Jan 1 08:00:11 kernel: Initializing USB Mass Storage driver...
Jan 1 08:00:11 kernel: usbcore: registered new interface driver usb-storage
Jan 1 08:00:11 kernel: USB Mass Storage support registered.
Jan 1 08:00:11 kernel: ufsd: driver (8.6, Sep 25 2013 18:09:24, LBD=ON, delalloc, acl, ioctl, ugm, rwm) loaded at bf5eb000
Jan 1 08:00:11 kernel: NTFS (with native replay) support included
Jan 1 08:00:11 kernel: optimized: speed
Jan 1 08:00:11 kernel: Build_for__Asus_RT-AC56U_k2.6.36_2013-01-18_U86_r195788_b2
Jan 1 08:00:11 kernel: xhci_hcd 0000:00:0b.0: xHCI Host Controller
Jan 1 08:00:11 kernel: xhci_hcd 0000:00:0b.0: new USB bus registered, assigned bus number 1
Jan 1 08:00:11 kernel: xhci_hcd 0000:00:0b.0: irq 112, io mem 0x18023000
Jan 1 08:00:11 kernel: xhci_hcd 0000:00:0b.0: Failed to enable MSI-X
Jan 1 08:00:11 kernel: xhci_hcd 0000:00:0b.0: failed to allocate MSI entry
Jan 1 08:00:11 kernel: usb usb1: No SuperSpeed endpoint companion for config 1 interface 0 altsetting 0 ep 129: using minimum values
Jan 1 08:00:11 kernel: hub 1-0:1.0: USB hub found
Jan 1 08:00:11 kernel: hub 1-0:1.0: 1 port detected
Jan 1 08:00:11 kernel: [xhci-hub] usb2mode:[0]
Jan 1 08:00:11 kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jan 1 08:00:11 kernel: ehci_hcd 0000:00:0a.1: EHCI Host Controller
Jan 1 08:00:11 kernel: ehci_hcd 0000:00:0a.1: new USB bus registered, assigned bus number 2
Jan 1 08:00:11 kernel: ehci_hcd 0000:00:0a.1: irq 111, io mem 0x18021000
Jan 1 08:00:11 kernel: ehci_hcd 0000:00:0a.1: USB 0.0 started, EHCI 1.00
Jan 1 08:00:11 kernel: hub 2-0:1.0: USB hub found
Jan 1 08:00:11 kernel: hub 2-0:1.0: 2 ports detected
Jan 1 08:00:11 kernel: hub 1-0:1.0: over-current change on port 1
Jan 1 08:00:11 kernel: [xhci-hub] usb2mode:[0]
Jan 1 08:00:11 kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jan 1 08:00:11 kernel: ohci_hcd 0000:00:0a.0: OHCI Host Controller
Jan 1 08:00:11 kernel: ohci_hcd 0000:00:0a.0: new USB bus registered, assigned bus number 3
Jan 1 08:00:11 kernel: ohci_hcd 0000:00:0a.0: irq 111, io mem 0x18022000
Jan 1 08:00:11 kernel: hub 3-0:1.0: USB hub found
Jan 1 08:00:11 kernel: hub 3-0:1.0: 2 ports detected
Jan 1 08:00:11 kernel: hub 2-0:1.0: over-current change on port 1
Jan 1 08:00:11 kernel: usbcore: registered new interface driver usblp
Jan 1 08:00:11 kernel: hub 2-0:1.0: over-current change on port 2
Jan 1 08:00:11 kernel: usbcore: registered new interface driver asix
Jan 1 08:00:11 kernel: usbcore: registered new interface driver cdc_ether
Jan 1 08:00:11 kernel: usbcore: registered new interface driver net1080
Jan 1 08:00:11 kernel: usbcore: registered new interface driver rndis_host
Jan 1 08:00:11 kernel: usbcore: registered new interface driver zaurus
Jan 1 08:00:11 kernel: device vlan1 entered promiscuous mode

 

[Dijkstra88]

Do you feel anything different when you overclock to 666?

The router feels faster with the 666mhz DDR ram overclock compared with stock 522mhz. But need more testing.

Send from my GT-I9505 with Tapatalk 4

 

[RMerlin]

USB3 support still seems to be a bit wonky. Even my drive that usually worked decided not to be mounted anymore. This is something I know Asus has improved in their newer builds.

I'll try enabling one of the USB-related option Asus has implemented, and which I'm unsure if they are using or not in their release firmware. Will see if it makes a difference, if it does I will re-issue an update for the AC68 with that option enabled.

But in the end, those issues probably won't be fully addressed until Asus does, and I integrate their newest code.

 

[Sohee]

I got conflicting reports on this, as other people said it was not working for them. Check the Tools -> Sysinfo page to confirm that nothing disabled HW acceleration due to incompatibility (such as QOS or Traffic Monitoring).

no, nat loopback doesn't work with hw acc on.
but loopback works with hw acc AND jumbo frame on.
its loopback speed is too low. under 100mbps.

235, 291, 306 will crash, if you try loopback with hw acc on.

 

[miodzicho]

I have tried to apply ebtables rules in firewall-start script located in jffs :

#Block DHCP between OpenVPN TAP
ebtables -I FORWARD -i tap21 -p IPv4 --ip-protocol udp --ip-destination-port 67:68 -j DROP
ebtables -I FORWARD -o tap21 -p IPv4 --ip-protocol udp --ip-destination-port 67:68 -j DROP
ebtables -I INPUT -i tap21 -p IPv4 --ip-protocol udp --ip-destination-port 67:68 -j DROP
ebtables -I OUTPUT -o tap21 -p IPv4 --ip-protocol udp --ip-destination-port 67:68 -j DROP
#Block UPnP between OpenVPN TAP
ebtables -I FORWARD -i tap21 -p IPv4 --ip-protocol udp --ip-destination-port 1900 -j DROP
ebtables -I FORWARD -o tap21 -p IPv4 --ip-protocol udp --ip-destination-port 1900 -j DROP
ebtables -I INPUT -i tap21 -p IPv4 --ip-protocol udp --ip-destination-port 1900 -j DROP
ebtables -I OUTPUT -o tap21 -p IPv4 --ip-protocol udp --ip-destination-port 1900 -j DROP

Unfortunatelly this is rebooting router, doing infinite reboot loop.
Even applied first lines are doing reboot.

I would like to filter traffic on VPN like on older rt-n66u but it seems impossible.
Anyone have noticed this ?

 

[canuckle]

So sorry if this is a twit question, but is it the alpha or beta file we're supposed to be using from the download site?

 

[svott]

So sorry if this is a twit question, but is it the alpha or beta file we're supposed to be using from the download site?

Maybe neither. Merlin's RT-AC68U directory currently has a
RT-AC68U_3.0.0.4_374.34_2.zip that appears to be the latest (stable?) release as of this message. In the archive you'll find a change log near the end of the readme file so you can compare releases if you're not sure which one to install.

This brings up another curiosity. What do all the numbers in the version mean? I can't find a post on here or a Wiki about it. The first five numbers seem to be static and the sixth seems to be an incrementing build number. But is there a way to understand what features/fixes from an Asus release are contained in a Merlin release?

 

[RMerlin]

Maybe neither. Merlin's RT-AC68U directory currently has a
RT-AC68U_3.0.0.4_374.34_2.zip that appears to be the latest (stable?) release as of this message. In the archive you'll find a change log near the end of the readme file so you can compare releases if you're not sure which one to install.

This brings up another curiosity. What do all the numbers in the version mean? I can't find a post on here or a Wiki about it. The first five numbers seem to be static and the sixth seems to be an incrementing build number. But is there a way to understand what features/fixes from an Asus release are contained in a Merlin release?

It used to be easy to do, but not any more since Asus started using extended numbers Previously, 3.0.0.4.374 was telling you all you needed to know about which Asus codebase was used. Then they started using the "extendno" value at the end, which added a new digit that can be different depending on if it's for a MIPS or an ARM device (that leads to, for example, 374.971 being older than 374.306).

Since I switch back and forth between MIPS and ARM codebases as I go with whichever is newest, that would have made things very confusing if I started also mentionning the extendno in my version numbers (which are already too long for my taste). Therefore what I do now is document in the README which code I am basing a release on.

If looking for the Asus changelog for a specific extendno (for example, 374.971), check either the RT-N66U or RT-AC68U - the two models I mostly check for updated GPLs.

 

[RMerlin]

As for what each number is for:

3.0 = the firmware kernel (not to be confused with the Linux kernel)
0.4 = the filesystem version (Asus used to increment it on major feature changes, like the N66 jumping to 64K nvram between 0.3 and 0.4)
374 = the release version, aka serial number
971 = the extendno (akin to a build version, if you will)

I wanted to simplify the numbering in my builds, but those numbers are referred to in various places in the code, so it wouldn't be prudent to do so.

 

[nurv2600]

HFS+ support?

So, I see in the latest firmware release for the RT-AC68U from Asus they've added HFS+ support for Mac volumes. We've loved the 68U in the office, but at my house I use an Airport Extreme to host a HFS+ formatted Drobo, with far too much data to backup somewhere else temporarily to reformat NTFS. After using the router at work, I'd love one at home, but need HFS+ support. Your readme file states it's based off 3.0.0.4.374.979 which doesn't mention adding this feature. Does your latest release add this, or would I have to stick with the stock firmware? Is it a feature you're planning on implementing?

 

[RMerlin]

So, I see in the latest firmware release for the RT-AC68U from Asus they've added HFS+ support for Mac volumes. We've loved the 68U in the office, but at my house I use an Airport Extreme to host a HFS+ formatted Drobo, with far too much data to backup somewhere else temporarily to reformat NTFS. After using the router at work, I'd love one at home, but need HFS+ support. Your readme file states it's based off 3.0.0.4.374.979 which doesn't mention adding this feature. Does your latest release add this, or would I have to stick with the stock firmware? Is it a feature you're planning on implementing?

HFS was added with GPL 374_291, which I haven't merged in yet.

 

[steve7929]

I flashed the latest news _2 build this morning and my wifi speeds onboth 2.4 & 5 fixed have drastically come down from 35mbps download to just 5mbps or less. Am I the only one having issues with this build?

 

[ronan_zj]

I flashed the latest news _2 build this morning and my wifi speeds onboth 2.4 & 5 fixed have drastically come down from 35mbps download to just 5mbps or less. Am I the only one having issues with this build?

I lost 5G signal sometimes, and overclock doesn't work, and I think next new build will be better

 

[RMerlin]

I flashed the latest news _2 build this morning and my wifi speeds onboth 2.4 & 5 fixed have drastically come down from 35mbps download to just 5mbps or less. Am I the only one having issues with this build?

As compared to what version? There has been zero change regarding wireless between 34_0 and 34_2.

 

[steve7929]

As compared to what version? There has been zero change regarding wireless between 34_0 and 34_2.

I flashed your build directly on my new Asus 68u and so don't have comparative results against other firmwares for it. I had n66u for last 2 weeks with no issues and so was wondering whether I should use Asus stock firmware. Your thoughts?

 

[RMerlin]

I flashed your build directly on my new Asus 68u and so don't have comparative results against other firmwares for it. I had n66u for last 2 weeks with no issues and so was wondering whether I should use Asus stock firmware. Your thoughts?

My code is based on older Asus code at this time, so it's up to you. For the AC68U, there's a good chance that Asus's current FW will work better as Asus fixed various issues in 291 and 306.

 

[canuckle]

Maybe neither. Merlin's RT-AC68U directory currently has a
RT-AC68U_3.0.0.4_374.34_2.zip that appears to be the latest (stable?) release as of this message. In the archive you'll find a change log near the end of the readme file so you can compare releases if you're not sure which one to install.

This brings up another curiosity. What do all the numbers in the version mean? I can't find a post on here or a Wiki about it. The first five numbers seem to be static and the sixth seems to be an incrementing build number. But is there a way to understand what features/fixes from an Asus release are contained in a Merlin release?

Thanks for the reply...I'm just looking for the most stable version of the firmware for basic use. I forward 10 ports to my NAS, and manually assign IP's to my managed switch, NAS, iMac, Apple TV, and Roku. Looking for good stability on both wireless bands, but that's about the extent of it. So, Alpha or Beta?

 

[RMerlin]

So, Alpha or Beta?

Neither - there's a newer non-beta release.