What's new

NEW RT-AC68R FIRMWARE OUT 376.1665

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

So what's the correct version of the firmware? Yesterday I downloaded 1665, now every Asus support site has version 1663.
 
Just flashed with firmware 1663 and I dont have access to the internet.


Stay away from 1663
 
Anyone have any idea why they changed the build number ? Did they fix or change anything ?
 
Don't think 1665 is available anymore. Strange thing to upload an inferior version. Maybe they did a mistake yesterday and uploaded the wrong version, 1665 being a test version. I just speculate.
 
Found a bug in this firmware.

If i set 5Ghz to 80mhz, and manually assign a channel 149-153, the wifi log shows 5ghz band is set to 20mhz and channel 39.
Xbox One shows Nat-Type; Moderate.



If i set 5Ghz to 40mhz and manual channel, then wireless log shows correct settings.
Xbox One shows Nat-Type; Open.

I can also confirm this. Also the 5 Ghz signal has dropped way down confirmed from both my wireless adapters. Back to Merlin 43_2 and i am happy again.

I sure hope Merlins new build does not have these issues or i will just forever stay on 43_2 :) In my opinion this new Asus firmware is a giant step backwards for the RT-AC68U
 
I loaded 1665 yesterday and discovered the 5GHz bug. Setting the 5GHz Wireless Mode to "N + AC" caused the 5GHz band to work in 40MHz/450N only. Setting the Wireless Mode to "Auto" instead of "N + AC" fixed the issue and allowed 80MHz/AC877 to AC1300 connections.

I downloaded and flashed 1663 today in hopes that it would fix the bug, but it didn't.

I also discovered a bug in both 1665 and 1663 that I had only encountered with Merlin's firmware previously. When you access the WDS screen from Wireless settings, within about 30 seconds 5GHz signal strength will go down by approximately 10dbm observed at my one AC device (PC with a PCE-AC68 Card). You don't have to change anything in the screen, just access it. The only way to get the signal strength back is to reboot the router.
 
Went back to 43_2 and everything is working correctly. Had to reset and reflash the router a few times to get the internet back.
 
Good Day,
The official first public release - 3.0.0.4.376_1779 - is now or will shortly be available for update via the Firmware Upgrade option under the Administration tab. Most of the US servers now offer the upgrade and the balance of North America and other regions will have the update available by tomorrow. The support site will be updated by Monday.

I will post stable betas in this thread as they become available.

Sincerely,
Gary

What does Asus plan to do about that latest release for the 68U the new version is full of bugs and degraded signal output ?
 
Don't bother updating if you use your cellphone for the usb 3g/4g function. USB tethering does not work with this release. At least not for the Galaxy S4 (T-Mobile USA). The last firmware that does work for me is 3.0.0.4_374_5047. Every firmware released since then, has ceased to work with USB tethering. I have tried running the 3G USB setting in both auto and 3G/4G with no luck. When I turn USB tethering on, the phone shows as connected on the router page, but I do not have internet. After a few minutes the USB tethering function automatically shuts down on the phone side. I flashed back to 3.0.0.4_374_5047 and USB tethering works fine. I pulled the following from the log:

Dec 31 19:07:16 hotplug: add net usb0.
Dec 31 19:07:16 hotplug: Got net usb0, vid 0x4e8, pid 0x6864.
Dec 31 19:07:16 hotplug: set net usb0.
Dec 31 19:08:14 rc_service: wanduck 543:notify_rc restart_wan_if 1
Dec 31 19:08:14 kernel: Attempt to kill tasklet from interrupt
Dec 31 19:08:18 rc_service: wanduck 543:notify_rc restart_wan_if 0
Dec 31 19:08:22 chat[2868]: Failed
Dec 31 19:08:23 chat[2998]: Failed
Dec 31 19:08:23 hotplug: add net usb0.
Dec 31 19:08:23 hotplug: remove net usb0.
Dec 31 19:08:23 hotplug: remove net usb0.
Dec 31 19:08:24 rc_service: wanduck 543:notify_rc restart_wan_if 0
Dec 31 19:08:24 hotplug: add net usb0.
Dec 31 19:08:24 hotplug: Got net usb0, vid 0x4e8, pid 0x6864.
Dec 31 19:08:24 hotplug: set net usb0.
Dec 31 19:08:26 chat[3200]: Failed
Dec 31 19:08:26 hotplug: remove net usb0.
Dec 31 19:08:27 hotplug: add net usb0.
Dec 31 19:08:27 hotplug: Got net usb0, vid 0x4e8, pid 0x6864.
Dec 31 19:08:27 hotplug: set net usb0.
Dec 31 19:08:28 rc_service: wanduck 543:notify_rc restart_wan_if 1
Dec 31 19:08:28 kernel: Attempt to kill tasklet from interrupt
 
Has anyone redownloaded the 63 ? It's been changed from 1665 to 1663
 
Well, I've done some test on 1663 fw.

BASIC CONS are:

1. "wl_reg_mode=d" / "wl0_reg_mode=d" (those are critical variables for mac) won't survive reboot !
2. "wl_country_code" won't survive the the reboot !

There is only one hope - Merlin will fix this in his firmware adition and allow us to take fully advantage from AC68U

3. Regarding power slide bar. One should't much take car about. TxPower variables were always working in association with tx PWR limit an you could enter any numbers you like i those related but always had been limited to power tables hardcoded in software. By the way, in MerlinFW 43_2 you get with Q2 country code 20.00 dBm (100mW) for each band ;-) the same as it comes with official 5656 asus fw.

There are some pros for new firmware however those 2 basic concerns disqualify one for use ...
 
Well, I've done some test on 1663 fw.

BASIC CONS are:

1. "wl_reg_mode=d" / "wl0_reg_mode=d" (those are critical variables for mac) won't survive reboot !
2. "wl_country_code" won't survive the the reboot !

That's because you are using the wrong variables. wl_reg_mode for example is a temporary variable used when the web interface saves user settings, while the real setting names are wl0_reg_mode (for 2.4 GHz) and wl1_reg_mode (for 5 GHz). The same applies to all wireless settings - you must use the actual instanced radio setting for each band (wl0_xxx and wl1_xxx), not the generic, temporary setting.
 
I had already flashed the 1665 before they replaced it with 1663, sadly there is no explanation on the site. Should I flash again? I don't want to continue running 1665 if there is a serious issue with it.
 
I had already flashed the 1665 before they replaced it with 1663, sadly there is no explanation on the site. Should I flash again? I don't want to continue running 1665 if there is a serious issue with it.

I doubt you will ever find the reason for the build # switch. I would download and install 1663 just to be safe you indeed have the latest. Be advised the latest release is buggy.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top