You can see that there’s a pace where to enable legacy 802.11b rates. I don’t have a Flint myself but you could try to search in wireless page on Luci, or downgrade your firmware to 4.2.3 if you can’t find this config.
Also, you could try the IGPM snooping config like the OP did.
I don’t understand your suggestion to downgrade my firmware to 4.2.3 to debug this problem. Surely this is an issue for the GLinet engineering team. If the current firmware revision is wrong it shoud be fixed. I should always be on the latest revision. I have already made a request for the firmware to be investigted. I reiterate that again here as I believe I have revealed a real problem with it with my extensive investigations. I apprciate all your help but this is starting to get to me
I don’t think that it is an firmware issue itself. The main issue is that your investigation isn’t really helpful since it’s not well documented.
To understand the problem we would need much more details. Like the exact WiFi chip within the device which is not able to connect and the capabilities.
If we would do some serious troubleshooting there would be plenty of rows in a table with checkmarks for each combination.
Right now I would assume that the problem is with your device only or with your settings at all. Since I am using a Flint by myself I can say that everything works as it should.
exactly, so it is incumbent apon the developers of this product to do this work, as you would not expect end users’ to do such investigations, as they are the customer not the merchant, and even so, they do not possess the skill set nor the expertise to diagnose the problem. Again I say there is an issue which I have flagged. Your engineering team should take it seriously and investigate such things as the said adapter chip set amongst other things. This kind of service enhances the reputation of the organization and the product
Oh! Sorry man. With all your help I really thought you were an employee for some reason. Please accept my apologies. I will find and write to the team. It’s in their interest to investigate. Thanks for all your help. I really appreciate your suggestions.
If people confuse me with the employees, it proves that I’m doing my “job” quite well
I already marked one of the team members, he will see it as soon as the week starts.
Would you mind providing me with the model number of the TPLink T4UH Wi-Fi dongle anyway? You said it’s an “old” computer - about “how old” do we talk here? Windows XP? Windows 7? Something entirely different?
Hey thanks for your understanding, man. I felt bad. Yes you are doing your “job” very well. Very convincing . Reason I got a bit crazy is I’m an electrical engineering with software experience. So I know some stuff. Anyways …
Windows XP does not support encryption standards higher than WPA2 TKIP (and even this not out of the box, only after installing KB893357) - could you please try to lower the encryption standard to WPA TKIP instead of WPA2/WPA3?
tried WPA2-PSK earlier which did not work. Just now tried the other low option WPA/WPA2-PSK. hat did not work either. There are no other low security options
I am not very familiar with Windows XP. Not anymore. Good old times, ha.
Can you compare the WiFi-settings of the Netcom Wireless router modem NB604N with the ones on the Flint? Pretty sure that the issue is the operating system because Windows XP is missing many modern WiFi stuff.
While frequency and stuff is handled by the dongle, encryption and other things are handled by the OS. So our goal must be to rebuild the same settings like on the NB604N.
It can because we don’t know the settings of the Wi-Fi on the public spot or your phone. Public Wi-Fi is mostly without encryption. Phone is often trying to have the lowest standards, so everyone can connect.
The main problem is that there are so many Wi-Fi standards outside that you can’t test against all devices. That’s why we have to do it step-by-step. In my normal job (which is IT) I would just tell “Windows XP isn’t supported anymore”
Another problem is that a Wi-Fi access point is capable of “deciding” which SSID should be shown to which device. So it is even possible that the Flint just decided not to be shown to your Windows XP devices - reason not yet known. There are so many adjustments that you could spend days on them.
Do you use the GL.iNet GUI for changing things, or do you use luci as well?
You tried to reset the Flint as well, I guess?
Sorry for the inconvenience. If you don’t have the devices within reach, it is very difficult to carry out troubleshooting in this way. I’ll still try my best so that we can understand (and solve) the problem together
Hey admon. When you mentioned win xp as potential culprit, it got me thinking. I got this brainiac idea. Installed the adapter on my windows 10 comptrer and I’m getting the same result as the xp computers. Win 10 can’t see the flint either with the adapter’s driver. I think we can close the case. I think the issue is with the TPlink driver. OK, Im officially over it. I’ll take it up with TPLink from here. Thanks for your help and patience with me. You did a good “job”
Yeah I guess that’s the other possibility that the dongle could actually be faulty. I’ll take it up with TPLink service department. Again thansk for your help. You did an amazing “job”
Hey thanks for the suggestion shivadow. But could not find what you referred to. Please explain it again. On my Flint, my wireless settings have no advanced tab. In Luci, Network section has no wireless tab either. Can you send a pic perhaps? cheers