I’m still going through the pcap files I gathered. Sometimes they would just time out with an unspecified “error”, other times they connected in a couple seconds and some times it took over 10 seconds to connect.
However, I found a number of models which would connect rather erratically. I was unable to find any model which absolutely refused to connect. I took a mango with 3.025 and a mango with the firmware provided to a local electronics store with a selection of Chromebooks for sale. (If the moderator prefers otherwise, please let me know.) Might as well join this thread as the other one ( here) is getting awfully long. Once I have tested the experimental firmware I will report back. I have given my email address and will see if there is some improvement. This makes using the repeater function quite tedious and mostly impossible fromt he chromebook. What is obvious: often it will arbitrarily struggle to connect - and sometimes not being able to connect at all (after booting up the mango it can get really stuck and the chromebook gives up altogether).Īnything that brings the wireless down can cause this unreliable behavior to emerge also - such as scanning for wifi repeater clients. Once the initial setup has passed and the connection has survived any settings that bring the wifi down (such as renaming the network), my chromebook now connects to the mango relatively reliably. Waiting at least 5 minutes also helped to ensure a successful first connection. I found that it’s easier to reset the mango until the chromebook connects first time than to try and force the wifi connection from the chromebook. I can now connect to the mango since I went back to the official gl.inet firmware but the setup process to get there is super erratic.
INSTALL TCPDUMP ON CHROMEBOOK DRIVERS
I have spent an afternoon diving into this, even tried the official openwrt build with the open source drivers and now have a better overall picture. Also would be helpful to ID the specific version of ChromeOS you’re currently running, and whether or not this is a “managed” ChromeBook (common in EDU/Corporate space, uncommon with consumer owned devices) Might be more helpful if you ID which exact Chromebook you have, Coral refers to the board design, which covers the follow models. People are working on it, both in the community and at GL-iNet
My chipset is intel 7265 and my chromebook is a google coral edition. Having only a chromebook has made this process very complicated and time-consuming for me. I felt the need to create a new post however just to express my discontent at the time wasted trying to get this stupid router to function only to discover the ridiculous efforts users here are going to to make it work and the minimal effort made by gl.inet in return.
0 kommentar(er)
