when will there be a new update ac87u

[RMerlin]

Beside the delays in release, does this affect your FW development in any way?

It will make it harder for me to release updates to all models simultaneously, so I will have to match Asus and do staggered model releases, in sync with their own release of the necessary components. That means 378.56 might support 2-3 models, 378.57 will support 1-2 different models, etc...

Right now (on September 23rd), the only model guaranteed to be supported by 378.56 is the new model I recently implemented, as the GPL I'm working with is for that specific model. Whether or not 378.56 will also support other models and which models it will be will depend on when each of these model's GPL gets released, and whether or not they are close enough to the GPL code I'm working with at that time. Hence, no ETA.

 

[JohnNerd]

Ok, sorry. As long as there is when and not if I'm very happy.

 

[Authority]

New FCC rules forced Asus to recently close the source code that handles the wireless configuration.

Wow I thought that was just a proposal, it actually went into effect? Damn! Sadly back to stock for now.

 

[RMerlin]

Wow I thought that was just a proposal, it actually went into effect? Damn! Sadly back to stock for now.

The initial FCC changes occurred over a year ago. I even rose awareness about it on the forums back then, after Asus themselves sent me a few documents from the FCC, and warning me that they were going to have to encrypt/close the wireless code in the near future (it just took longer than I expected for them to get around to it). So personally, I've known about this for over a year already...

People are only starting to wake up now due to ADDITIONAL changes that the FCC wants to do on top of the existing new rules, and scary-looking wording that indicates that manufacturers might need to take steps toward preventing any third party firmware. They have already publicly denied this (see the Ars Technica article).

The new rules that are already in place state that:

- Starting with summer 2015 (I forgot the exact month), any new device submission would need to comply with the new rules from last year to be validated
- Starting with summer 2016, any EXISTING device would need to comply with the new rules to be allowed to be marketed

Here's one of the original threads (I can't track down the other one that was in General Wireless):

http://www.snbforums.com/threads/asus-locking-down-routers-to-comply-with-new-fcc-rules.18762/

 

[JGrana]

The initial FCC changes occurred over a year ago. I even rose awareness about it on the forums back then, after Asus themselves sent me a few documents from the FCC, and warning me that they were going to have to encrypt/close the wireless code in the near future (it just took longer than I expected for them to get around to it). So personally, I've known about this for over a year already...

People are only starting to wake up now due to ADDITIONAL changes that the FCC wants to do on top of the existing new rules, and scary-looking wording that indicates that manufacturers might need to take steps toward preventing any third party firmware. They have already publicly denied this (see the Ars Technica article).

Yes indeed, awareness is starting to happen with the general public. Here is an article from Engadget, posted today:

http://www.engadget.com/2015/10/07/fcc-wifi-router-lockdown/#continued

Note that the Electronic Frontier Foundation (non-profit group of very bright technologist) has setup an on-line petition to send to the FCC:

https://dearfcc.org/

If you are a user of DD-WRT, Asuswrt, Tomato, Merlin etc. (actually, open source in general), you should put in your comments and sign.

We need to put pressure on the FCC from protecting us from us!!!

 

[snapilica2003]

Is there anything critical security wise that has changed to the latest stock firmware versus the .55 firmware? I'm asking because my current setup makes it mandatory to use nat scripts and dnsmasq configs. So unless something bad/big/important has been patched by ASUS that's not in Merlin's firmware, I'm sticking with the .55 firmware

What I am scared is that my not so long-ago purchased AC68U might soon be forever unsupported by Merlin. More work means less devices can be kept up to date. That will be a sad day...

 

[RMerlin]

Is there anything critical security wise that has changed to the latest stock firmware versus the .55 firmware? I'm asking because my current setup makes it mandatory to use nat scripts and dnsmasq configs. So unless something bad/big/important has been patched by ASUS that's not in Merlin's firmware, I'm sticking with the .55 firmware

What I am scared is that my not so long-ago purchased AC68U might soon be forever unsupported by Merlin. More work means less devices can be kept up to date. That will be a sad day...

WAN-side, no, at least none documented in their changelog. LAN-side, there are a few vulnerabilities in the internal web server that were fixed. You might just want to make sure that you are not exposing the web interface to the WAN - always use a VPN service instead if you do need remote access.