Beta 374.501

[mtrains]

Try to disable the firewall, it worked for me.

Tried that. Doesn't work. I found a temporary workaround. If I disable the network card and enable it I can access the router by typing in \\RT-AC68R on the windows explorer window. Then it shows up as a network computer. The router will not automatically show up as a network computer on the windows explorer window.

 

[nyxagamemnon]

Now my Canon Printer cannot connect to the router with .501 lol.


All these resources you have and you can't code software properly.


Makes me laugh.

 

[RMerlin]

Tried that. Doesn't work. I found a temporary workaround. If I disable the network card and enable it I can access the router by typing in \\RT-AC68R on the windows explorer window. Then it shows up as a network computer. The router will not automatically show up as a network computer on the windows explorer window.

There's some firewall funk that Asus added to improve Samba sharing performance, but I also found it interfered with network discovery indeed. I reverted those changes in my firmware to resolve the issue.

 

[Xerxist]

Just for the sake of checking i turned on firewall logging on incoming and outgoing connections last week to see if the firmware 501 is safe.

To my surprise I get accepted connections on port 80 and this is blocked off....

Even if i try shields up it reports as being closed.

But for some reason these get through.

Dec 27 15:10:49 kernel: ACCEPT IN=eth0 OUT= MAC=ea:ee:3b:6d:67:92:11:31:c8:cd:0e:11:73:34 SRC=60.173.10.252 DST=192.168.10.1 LEN=40 TOS=0x00 PREC=0x00 TTL=106 ID=256 PROTO=TCP SPT=6000 DPT=80 SEQ=1811283968 ACK=0 WINDOW=16384 RES=0x00 SYN URGP=0

Not sure what to do.

 

[mtrains]

There's some firewall funk that Asus added to improve Samba sharing performance, but I also found it interfered with network discovery indeed. I reverted those changes in my firmware to resolve the issue.

Yes. I noticed that the network discovery is rock solid with your 36 Beta1 firmware. Then I ran into some web UI instability with that beta. So I decided to switch to 501 Guess I will wait for your official 36 firmware release.

 

[speedingcheetah]

[*] Regarding the new HW acceleration modes: there are now three modes from what I could understand (note that I'm not 100% sure, but pretty close):

1) No CTF (no HW acceleration at all)
2) Level 1 CTF (which is the same as previous FW versions)
3) Level 2 CTF (which is CTF + FA)

FA = Flow Accelerator. It's a Broadcom technology that's supposed to improve network throughput. As usual, there is zero technical details as to how they achieve this, what are the side effects, etc...

Now, the weird part: like other users reported, setting CTF to Level 2 does not seem to work for me either. After it's rebooted it's back on Level 1. I tried querying the wireless driver to see what FA level is supported by the hardware, and it reports... 0. So, either a) not all router models/revisions support it, b) Asus hasn't fully enabled it yet in the driver, or c) the routine that reads the supported FA revision is broken.

If any of you is able to set it to Level 2 and have it stick there after a reboot, please let me know. I'll send you a tool so you can try querying the router for me to see if it returns a different FA revision.

[
Due to both the Wifi and USB changes, a factory default reset is indeed strongly recommended when flashing this FW. (I even did one myself, which I rarely do).

The HW acc doesn't stick for me either on my AC56U....in fact, when I tried setting level 2, router rebooted...and no wifi...rebooted it manually...and wifi was back, but it did set it back to level 1....so...guess its still a feature they are still working on.

I didn't do a factory reset when I flashed this .501 over the previous stock version....and I really haven't had any issue to report.

 

[mlai]

The 501 still reboots itself if I have a USB3 SSD attached and any levels of NAT HW Acceleration enabled......

 

[RMerlin]

Yes. I noticed that the network discovery is rock solid with your 36 Beta1 firmware. Then I ran into some web UI instability with that beta. So I decided to switch to 501 Guess I will wait for your official 36 firmware release.

I don't see any report of webui issues in my beta thread. I can't really fix issues that aren't reported - that's the whole idea behind releasing a beta FW, so people can report those issues.

 

[Kris404]

Thanks for reporting it. Asus also sent me mine at about the same time it hit retail, so it's probably the same revision.

I don't know if there was any revision update, that's why I'm curious to see if anyone is actually able to enable level 2 support.

CTF Level-2 does not stick for me either after reboot on AC68U. Bought this device from NewEgg in October. Never did a teardown to see what revision it is.

 

[maylyn]

[*] For those wondering about the new info now shown on the Wireless Log page: PSM = Powersaving Mode. You can see that flag get on and off between refresh with mobile devices (I saw it with my Nexus 7). No idea what the two other settings are exactly (SGI = Short GI, and STBC = ...STBC).

A quick google reveals the following

SGI - Short Guard Interval

In the first several “How Stuff Works” posts, I have been talking about technical improvements to 802.11n such as MIMO antennas, Spatial Multiplexing, and Channel Bonding. In this post, I want to talk about another such technical improvement, Short Guard Interval.

The guard interval is the space between symbols (characters) being transmitted. This is often confused with the space between packets, which is the interframe space (IFS). The guard interval is there to eliminate intersymbol interference, which is referred to as ISI. ISI happens when echos or reflections from one symbol interfere with another. Adding time between symbol transmission allows these echos and reflections to settle in before the next symbol is transmitted. In normal 802.11 operation, the guard interval is 800 ns.

STBC - Space-Time Block Coding

A method of transmitting a single data stream across multiple antennas for additional transmission redundancy.

Guess ASUS is spearheading all these in preparation for 2nd Wave 802.11ac and MU-MIMO? hehe

 

[mtrains]

I don't see any report of webui issues in my beta thread. I can't really fix issues that aren't reported - that's the whole idea behind releasing a beta FW, so people can report those issues.

I didn't report it as a problem on the firmware thread because I wasn't sure the root cause of the problem was the firmware. I am new here on these forums. So I wasn't not sure about the protocol for reporting problems on the firmware thread. I will go ahead and report the web UI symptoms I saw on the firmware thread.

 

[whsbuss]

Strange

I've noticed something strange on Beta 501 (downloaded from Asus site). On my MacBook Pro in Safari when I enter the LAN IP of the RT-AC68R it always just logs me in without asking for username/password. Even if I click Logout in the UI it still just logs in. And Safari never asked if I wanted to save the password (which I never do).

 

[RMerlin]

I've noticed something strange on Beta 501 (downloaded from Asus site). On my MacBook Pro in Safari when I enter the LAN IP of the RT-AC68R it always just logs me in without asking for username/password. Even if I click Logout in the UI it still just logs in. And Safari never asked if I wanted to save the password (which I never do).

It has always worked like this. The login credentials are cached by the browser and automatically sent back by it until the time where you completely close your browser.

 

[house]

Best firmware for ac68u ever in my opinion. I get 48mb/s on ac7260 when I copy some large files from synology nas to my clevo.

Wysyłane z mojego LG-D802 za pomocą Tapatalk 2

 

[whsbuss]

It has always worked like this. The login credentials are cached by the browser and automatically sent back by it until the time where you completely close your browser.

Thanks. Not a very secure way to handle things.

 

[intermilan]

Try to disable the firewall, it worked for me.

I disabled the ac68u firewall and it worked here as well.

 

[rtcomputersinc]

Did ASUS change their website? Checking for firmware's is much harder now. Plus it doesn't work well.

On another note if you cant access the webui the phone trick works great.

 

[intermilan]

Did ASUS change their website? Checking for firmware's is much harder now. Plus it doesn't work well.

On another note if you cant access the webui the phone trick works great.

I regret buying this router. Asus sells the router and we get to figure out how to fix bugs in the firmware!

 

[mostou]

I regret buying this router. Asus sells the router and we get to figure out how to fix bugs in the firmware!

I don't regret buying this router. In the process of finding another alternative to my Linksys E3000 with TomatoRAF firmware I am sure the AC68u was the correct choice (long term). Asus is also active in this forum (Asusnet) - I haven't noticed any other router vendor being active in a user forum like this.

Otherwise don't be a first mover. Stick to some of the "older" and stable routers like for instance the Asus RT-N66U if you prefer not to get "your hands dirty".

 

[TimothyM96]

Did ASUS change their website? Checking for firmware's is much harder now. Plus it doesn't work well.

On another note if you cant access the webui the phone trick works great.

I can say they are doing work on it, as well as with the product registration page. Should be almost done now.