Thank you for your message.
The problem is cleary as you say, the negotiation.
Sometimes the chromebook connects super fast… other times it just refuses to connect seemingly forever.
The error messages I receive when it fails are the exact same that @czsmith mentioned ‘unrecognised’ error or ‘bad configuration’… The chromebook will often ask me to input the password again because it believes that the configuration is wrong despite it being able to connect later with the exact same config.
So it is pretty clear that the problem is the handshake process because once connected, the router works really great with the chromebook.
However this connection problem is exacerbated by the repeater function which really suffers with this bug. Because of this, I have only been able to connect the Mango as wifi repeater to the chromebook successfully only 3 times during hours of testing.
I understand that you do not have access to a chromebook. However, I believe that you should try to borrow some by asking around. Otherwise, perhaps you could send your Mango to someone who has access to chromebooks to debug it for you - I beleieve that @sfx2000 offered to do this.
Perhaps you could also reach out to your suppliers / mediatek and they will be be able to explain what the specific issue with these chromebooks with intel chips is? Perhaps a bug report on the chromium tracker with @czsmith’s pcaps would be enough to get to the bottom of this problem?
It is probably something really basic like KRACK mitigations etc. It seems a shame for me to throw away the router because it just cannot work with chromebooks.
If this doesn’t seem feasible to you then the only option I see would be for you to compile several firmwares for @czsmith and I to test and we will let you know if there is any improvement. I could easily test a handful of firmwares in less than an hour. It’s quite easy to test the bug with the repeater function so there is no need to spend hours getting a feeling on whether it’s working or not - just try the repeater function and see if it works… if it works try a couple more times. A functioning firmware will be very easy to observe.
But really this is not what I want to do with my time so I really hope that you can find a timely solution to this.