new firmware on asus site 374.257

[bigcid10]

well,I take that back .there's still something wrong with this driver
It was ok for a day then it started dropping the connection
this morning I came home and it refused to reconnect to my galaxy s4
until I reloaded the profile
kept telling me it couldn't authenticate

 

[jlake]

well,I take that back .there's still something wrong with this driver
It was ok for a day then it started dropping the connection
this morning I came home and it refused to reconnect to my galaxy s4
until I reloaded the profile
kept telling me it couldn't authenticate

That's good that you are reporting it here, but it's unlikely to do you any good unless Merlin owns a galaxy S4. You'll need to contact Asus. And even then, unless Merlin buys a Galaxy S4, it's unlikely to get fixed.

 

[got_milk]

That's good that you are reporting it here, but it's unlikely to do you any good unless Merlin owns a galaxy S4. You'll need to contact Asus. And even then, unless Merlin buys a Galaxy S4, it's unlikely to get fixed.

Merlin doesn't touch the wireless portions of the code (he can't for the most part even if he wanted to - the Broadcom drivers are closed source and distributed as prebuilt blobs). In his own builds he simply replaces the broken driver blobs with working ones from previous firmware releases.

FWIW I'm on Asus .270 and have no problems whatsoever and no plans from moving away from this build as everything is working just as I want it to right now.

 

[bluepoint]

That's good that you are reporting it here, but it's unlikely to do you any good unless Merlin owns a galaxy S4. You'll need to contact Asus. And even then, unless Merlin buys a Galaxy S4, it's unlikely to get fixed.

I do not understand why you're blaming Merlin with your troubles. If any, you should be grateful because he's sharing his customized firmware for free. A childish behavior indeed. Do you expect asus to fix your problem by whining here? If you think your problem will be fix without helping yourself, you are in for more frustrations. Asus can not fix a problem that doesn't exist if you don't tell them. For all you know, your problem might not be even Asus's. Merlin already suggested that you post in another thread specifying all important information about your setup/steps you've taken but you have not done so. I've ask you your wireless driver version and date but you haven't post it. It probably needed to be updated, have you tried that?

 

[bigcid10]

Merlin doesn't touch the wireless portions of the code (he can't for the most part even if he wanted to - the Broadcom drivers are closed source and distributed as prebuilt blobs). In his own builds he simply replaces the broken driver blobs with working ones from previous firmware releases.

FWIW I'm on Asus .270 and have no problems whatsoever and no plans from moving away from this build as everything is working just as I want it to right now.

I'm didn't have any issues with the 270 series firmwares either
even up to merlins's 30-31

 

[jlake]

I'm didn't have any issues with the 270 series firmwares either
even up to merlins's 30-31

My adapters work fine for all the .270 series too (including .276). My adapters have problems with all Asus stock .37x series 5 Ghz (including 354 beta) due to the new driver.

The problem for me is they have not patched the security holes for .270 series. And there's no guarantees that they will continue to support the .270 series if new security vulnerabilites arise in the future.

If you read the changelog, it appears they have devoted their efforts on patching the security vulnerabilities for .37x series and fixing the intel problem.

The "official" workaround that I got from Asus is to use firmware .270 which has security vulnerabilities. That doesn't sound like a well thought out workaround since the 5Ghz problem has been occuring for months for me and many others.

 

[Deleted member 22229]

Just use the Merlin builds the newest bata has all the security fixes but uses the old drivers that have no issues. Merlin has added a ipv6 firewall to the newest bata as well.

 

[jlake]

Merlin doesn't touch the wireless portions of the code (he can't for the most part even if he wanted to - the Broadcom drivers are closed source and distributed as prebuilt blobs). In his own builds he simply replaces the broken driver blobs with working ones from previous firmware releases.

FWIW I'm on Asus .270 and have no problems whatsoever and no plans from moving away from this build as everything is working just as I want it to right now.

You are using Asus firmware .270 that has two un-patched security vulnerabilities. That might be acceptable for you, but it is not acceptable for me and many others.

 

[jlake]

Just use the Merlin builds the newest bata has all the security fixes but uses the old drivers that have no issues. Merlin has added a ipv6 firewall to the newest bata as well.

There's no guarantees that Merlin will continue to support the old driver, especially when he had to hack the current build and it took him 3 days.


Merlin is not responsible for Asus' 5 Ghz problem nor should he be relied on for Asus problems.

Asus needs to immediately patch the security vulnerabilites in .27x

Edit:

The mere fact that the "official" workaround that they gave me on Wednesday was to use firmware .270 without even telling me that it has security vulnerabilities doesn't sit well with me. I already knew it had vulnerabilities, but they didn't even mention it. That is starting to open my eyes a little about Asus.

 

[Deleted member 22229]

There's no guarantees that Merlin will continue to support the old driver, especially when he had to hack the current build and it took him 3 days.


Merlin is not responsible for Asus' 5 Ghz problem nor should he be relied on for Asus problems.

Asus needs to immediately patch the security vulnerabilites in .27x

I concur that Merlin is not responsible for Asus firmware problems but thankfully he does what he does and it helps people. It seems as I read a lot in forums and all the big three routers seem to have a hard time releasing firmware that works right. Do they test this stuff before releasing to the masses I don't think so.

 

[RMerlin]

There's no guarantees that Merlin will continue to support the old driver, especially when he had to hack the current build and it took him 3 days.

Truth be told, I haven't taken any decision yet. Releasing a new firmware still based on the old driver isn't difficult, that 3 days of work only had to be done the first time when I split the code into two branches.

Some people get better performance with the new driver, while others still need the old driver. And if possible I'd rather avoid releasing two different FW for each driver version, as each new release already requires me to compile and bundle 8 different firmwares.

So for now I'm in a wait-and-see situation as more feedback gets posted.

 

[jerry6]

the new FW seems to have fixed the 5 ghz band problems , stable connection , much better transfer rate , at least 4-6 MBPS faster with intel 5300 and 6300 clients with latest FW . With the old FW was lucky to get 1 MBPS transfer rate . Using 20/40 mhz .
Hope others are getting good results as well

 

[bluepoint]

Just use the Merlin builds the newest bata has all the security fixes but uses the old drivers that have no issues. Merlin has added a ipv6 firewall to the newest bata as well.

If I'm not mistaken the reported security vulnerabilities were both fix in .276, the reason the 27X branch released new versions. It has not been noted in the release notes but I think it's the main reason Asus released .271/.276.

 

[jlake]

If I'm not mistaken the reported security vulnerabilities were both fix in .276, the reason the 27X branch released new versions. It has not been noted in the release notes but I think it's the main reason Asus released .271/.276.

Once again, you seem to be speaking on behalf of Asus. What evidence do you have that supports your belief that "it's the main reason Asus released .271/.276"?

 

[got_milk]

You are using Asus firmware .270 that has two un-patched security vulnerabilities. That might be acceptable for you, but it is not acceptable for me and many others.

The two vulnerabilities I think you're referencing are the ones that is related to AiCloud (don't remember the specifics offhand) and the Broadcom ACSD buffer overflow. I don't use AiCloud so it is disabled on my router, rendering that vulnerability moot to me, and as far as I can tell the Broadcom ACSD vulnerability requires LAN access as port 5916 is not WAN-accessible by default. (I could be wrong on this point so if someone knows better, please correct me.)

No piece of software is ever 100% secure - there are always vulnerabilities that can be found and exploited, it's just a matter of whether we know they exist or not. You have to balance the level of security you're willing to have and usability. I won't bother upgrading to fix vulnerabilities that don't affect me and potentially break my perfectly functioning configuration.

 

[RMerlin]

Anyone still having issues with 374_257, please try switching to TKIP and reconfiguring the wireless connection on your device/phone. I'm curious to see if your issue would be similar to this issue happening with the Samsung S4 and different router models (not just Asus):

http://forums.androidcentral.com/t-...alaxy-s4-slow-wifi-issues-when-using-aes.html

Even if it works I do not recommend you keep it that way, as TKIP is less secure than AES. I'd just like to gather some additional feedback.

 

[jlake]

The two vulnerabilities I think you're referencing are the ones that is related to AiCloud (don't remember the specifics offhand) and the Broadcom ACSD buffer overflow. I don't use AiCloud so it is disabled on my router, rendering that vulnerability moot to me, and as far as I can tell the Broadcom ACSD vulnerability requires LAN access as port 5916 is not WAN-accessible by default. (I could be wrong on this point so if someone knows better, please correct me.)

No piece of software is ever 100% secure - there are always vulnerabilities that can be found and exploited, it's just a matter of whether we know they exist or not. You have to balance the level of security you're willing to have and usability. I won't bother upgrading to fix vulnerabilities that don't affect me and potentially break my perfectly functioning configuration.

Yes. Perfectly understandable why you aren't concerned about Aicloud patch. I do use Aicloud.

 

[RogerSC]

I didn't ask you to explain why it was working fine when going back to 270.
I know why it worked fine when you went back to .270. It worked fine for the same reason my adapters work fine when I go back to .270. Because there is an incompatibility issue.

My questions were rhetorical.

http://en.wikipedia.org/wiki/Rhetorical_question

But thanks for explaining anyway.

I sent another email to Jeremy. I need to dump this router if they don't fix it soon. Thanks for all your help.

After sending my issues to Jeremy in regards to my Ralink-based wireless network adapters, I got a note back from Asus development today that they realize that they fixed the Intel-related problems and are hearing that there are other wireless network adapters that need more work. So they are still working on those problems that were not fixed by this latest firmware.

Don't despair, help is coming, I hope *smile*. No date, of course, but they are aware of these problems and are working on them.

 

[RMerlin]

After sending my issues to Jeremy in regards to my Ralink-based wireless network adapters, I got a note back from Asus development today that they realize that they fixed the Intel-related problems and are hearing that there are other wireless network adapters that need more work. So they are still working on those problems that were not fixed by this latest firmware.

Don't despair, help is coming, I hope *smile*. No date, of course, but they are aware of these problems and are working on them.

I also heard back from Asus tonight that they were going to look into the issues experienced with some Broadcom-based adapters such as the Linksys AE2500.

 

[njfoses]

Just purchased this router today. First thing i did was upgrade to the latest firmware and cleared nvram for the heck of it. My Vaio laptop with an Intel-6235 would only connect if i changed the 5 ghz setting to 20 mhz. If the setting was at 20/40 or 40 mhz it would not connect at all on 5 ghz. It would connect to 2.4 ghz with no issue. The highest link speed i could achieve was 144 mbps on 5 ghz. I then installed Merlin 372.31 cleared nvram and now i can connect with the setting at 20/40 and the link speed i expected of 300 mbps. At least for me the new firmware is not the answer.