WPS still not disabled on 5Ghz

[CiscoX]

Hi. I just got my new RT-AC87U. Firmware 3.0.0.4.378_3885.
I have noticed couple of bugs.
When I disable the WPS in Wireless. I turn off the WPS on 2.4 and 5Ghz. But when I restart the router. The WPS on 5Ghz are enable. So I have to go to the Wireless and turn it ON and OFF again.

And the second most annoying bug/error is in the system log.
kernel: br0: received packet on vlan1 with own address as source address


UPNP seems not to work very well. With my 68U it shows ports in the port forwarding table. But with my brand new 87u it shows nothing. Even when I start Skype(i use custom port nummer) it will not appear in the port forwarding table.
I didn't had this problem with 66u and 68U.




Sent from my Xperia Z (C6603) or Z1 (C6903)

 

[ankhazam]

Finally someone else with the same bug as me!!!! @RMerlin could you please investigate it.. I am not alone anymore!

@CiscoX ... for the time being you can hide your SSID, it disables WPS permanently.

 

[RMerlin]

Finally someone else with the same bug as me!!!! @RMerlin could you please investigate it.. I am not alone anymore!

I'm not paid to debug Asus's code. Why don't you ask them to fix it?

 

[ankhazam]

Yeah, I understand that and as I wrote you I've been pestering them at the other forum for few months... They still haven't resolved it. I thought it was some simple missing command being not send to Quantenna during initial boot which is on the other hand sent properly when one toggles WPS on and off from the web panel

 

[toor]

Its the same bug on mine, I also have a new bug when I try to toggle the WPS button i cant switch frequencies to the 5Ghz WPS page. How is that for a feature....

 

[ankhazam]

@Rmerlin I simply thought the major advantage of your releases was, beside the added functionality goodies sack, improved security and I find this bug (present in 378.50) qualifies for it.
As a workaround I disabled the SSID broadcast but still it's not a fix

 

[RMerlin]

@Rmerlin I simply thought the major advantage of your releases was, beside the added functionality goodies sack, improved security and I find this bug (present in 378.50) qualifies for it.
As a workaround I disabled the SSID broadcast but still it's not a fix

It's not a priority for me as I cannot reproduce the issue, I have zero documentation on how to configure the Quantenna firmware, and I'm doing this all on my own, on my spare time. I have to chose what to spend my limited time on. So unless I get more help, this will remain fairly low on my list of things to work on. This isn't a 15 mins fix, this will most likely require many hours just to study how the Quantenna firmware works (assuming I can, with the current lack of documentation).

That's why I'm saying Asus is in a much better position to resolve this issue than me.

 

[ankhazam]

Ok, I will pester them more... or just forget it as I don't need ssid broadcast anymore which solves the problem for me.
The rest of people in this thread please report the bug to Asus support eg. in this thread http://goo.gl/E29hel so they will have more feedback that we actually experience this flaw.

 

[toor]

Am i the only one who cant actually switch to the 5ghz on the WPS page to turn it off? I click the button to switch frequencies and it just keeps refreshing the 2.4Ghz.

I'm using merlins 50_ta.

 

[ankhazam]

No, it's common. Asus recently bonded WPS on both radios, you cannot anymore pick 2.4 or 5GHz, only both.
So in order to actually disable the 5GHz one you need to enable it, wait for radios reboot and then disable.

 

[sentinelvdx]

Am i the only one who cant actually switch to the 5ghz on the WPS page to turn it off? I click the button to switch frequencies and it just keeps refreshing the 2.4Ghz.

I'm using merlins 50_ta.

Even with the official ASUS firmware I'm unable to turn off WPS on 5Ghz band. Hope ASUS work on it and fixed it. I doubt RTMerlin have all the information he needs to fix that. ASUS will always keep something for themselves that wont share

 

[CiscoX]

Hi,

Well after couple of days testing my new RT-AC87U, i decide to go back to my old girlfriend RT-AC68U with RMerlin FW 378.50. Rock stable. Thank you RMerlin.

The RT-AC87U, i don't know what to write. But i don't know why ASUS are releasing a product that has not been full tested for 110% with a good firmware. I do understand is difficult to sit there with hundred of other devices, like smartphones, tablets, laptops etc etc to test them on wireless for stability etc etc.

But i don't know why they can't fix the other "small" bugs like:

- Disable WPS
- UPnP in the Port forwarding table list
- Broken NAT loopback?
- VLAN loop: kernel: br0: received packet on vlan1 with own address as source address
- Not record in Traffic Manager - Traffic Monitor

It's probably much more. But this the problems I had for the last two days.
I don't know what to do with this RT-AC87U. Maybe deliver it back to the store.

So, anyway. Thanks again RMerlin for your FW on RT-AC68U

 

[sentinelvdx]

Hi,

Well after couple of days testing my new RT-AC87U, i decide to go back to my old girlfriend RT-AC68U with RMerlin FW 378.50. Rock stable. Thank you RMerlin.

The RT-AC87U, i don't know what to write. But i don't know why ASUS are releasing a product that has not been full tested for 110% with a good firmware. I do understand is difficult to sit there with hundred of other devices, like smartphones, tablets, laptops etc etc to test them on wireless for stability etc etc.

But i don't know why they can't fix the other "small" bugs like:

- Disable WPS
- UPnP in the Port forwarding table list
- Broken NAT loopback?
- VLAN loop: kernel: br0: received packet on vlan1 with own address as source address
- Not record in Traffic Manager - Traffic Monitor

It's probably much more. But this the problems I had for the last two days.
I don't know what to do with this RT-AC87U. Maybe deliver it back to the store.

So, anyway. Thanks again RMerlin for your FW on RT-AC68U

I've reported this to a contact I have (local ASUS Regional Manager) who's going to share me a contact to deliver all of these to the dev. team.
Hope that will help and be more effective than support reps. on asus site

UPDATE (08/03/15): So far I have response about some of the issues reported, but this is not going to be addressed apparently on next firmware. Maybe we will see it on future ones

 

[snbdora]

The bug still exists in the latest firmware. Sigh....