@Mark14 wrote: First of all, the problem is not "SOLVED". If it was solved, you would have given a solution and we could use our networks the same as we did before this happened (approx 6 weeks ago). Please change the status back to "OPEN" and please progress with Technical Support to have the problem fixed.  While I sympathise with a number of the points you've made in your reply, isn't it the person who started the thread who chooses a reply as being a 'solution', after which the thread is then marked 'solved'? In other words, perhaps it wasn't a mod who marked the thread solved?   I'm not sure on this point, as I'm new to these forums. However, on the one thread I've started, I'm seeing that I have the option to mark any reply in that thread as an accepted solution, which is why I think it works the way I've outlined above. ... View more

@david64 wrote: The term WPA2/WPA3 ought to mean that the Sagemcom understands WPA2 and WPA3, whichever one a wifi device wants to use. I understand this. However, the mere fact that the modem is offering WPA3 seems to be the thing that bamboozles my phone. When it is only WPA or WPA2 that are offered (as on my old router) then my phone correctly connects using WPA2. I appreciate that the fault probably lies more with my phone than with the modem but buying a new phone within the trial period is not something I really want to do.   I'll see if I have the time to try setting up another router as an access point in the next couple of days. Otherwise I think I may have to return the Sagemcom. Would have been good if they offered WPA/WPA2 as an option. Seems to be quite limited in what you can configure on this modem, probably by design but ultimately gives people less room to deal with device connection issues. ... View more

Thanks for the reply @david64.   Here's what I've established regarding my phone (Mi A1) and the Sagemcom modem :   (I experimented using guest networks, as the interface gave me the greatest control over the settings on these.)   1. Activated a guest network on 2.4 Ghz with the only available security setting of WPA2/WPA3, and with a unique name. My phone could see it but couldn't connect. Changed the security setting to no security. My phone could connect and then did as well on the Ookla speedtest as my laptop does.   2. Activated a guest network on 5 GHz with the only available security setting of WPA2/WPA3, and with a unique name. My phone could see it but couldn't connect. Changed the security setting to no security. My phone could connect and then did as well on the Ookla speedtest as my laptop does.   So, in summary, my phone works on both 2.4 Ghz and 5 GHz but the WPA2/WPA3 security setting bamboozles it.   On my old router (Archer C1600), my phone can also connect on both frequencies and that router has a security setting of WPA/WPA2. My phone connects fine and when connected it shows that it's using WPA2.   So the only available setting of WPA2/WPA3 on the Sagemcom seems to be a problem (btw, this shows up on my phone when seeing the network as a padlock with a + superscript).   I've found a person in another thread describing the same issue between the Mi A1 phone and the Sagemcom modem here : https://community.tpg.com.au/t5/Modems-and-Devices/Sagemcom-5866T-5G-modem-WiFi-settings/m-p/125628/highlight/true#M17461   Now I can appreciate that the issue lies more with my phone than the router, i.e. seems to be a bug with my phone concerning WPA3. But if the modem allowed more than one security setting, i.e. if it allowed WPA/WPA2 as an option along with WPA2/WPA3 then I could sidestep the issue with my phone. However it doesn't and not being able to connect my phone to the modem is a show-stopper for me. I understand that I could set up another router as an access point and bridge that router to the sagemcom modem but that's a bit of a hassle for me, and also uncharted territory (fairly confident that I could work out how to do it but haven't done it before). So looks like I might have to return the Sagemcom modem and go back to my old NBN plan (which is an option as I'm in the 7 day changeover period). ... View more