Post #2368297
2026-05-07 12:42 UTC
Replies (4)
-
@Zenie@piaille.fr 2026-05-07 13:44
@Kurt@chaos.social Yes. It's a fibre box that does both. The fiber goes all the way to the street unlike the ancient wifi at my old apartment. All equipment is from France and I haven't had problems with other wifi networks no matter where I am in Europe.
-
@Zenie@piaille.fr 2026-05-07 13:45
@Kurt@chaos.social Btw. I'm a very experienced system dev. I know where the fiber is and isn't.
-
@Zenie@piaille.fr 2026-05-07 14:13
@Kurt@chaos.social I don't even know where to start with connecting to wifi, it just fails. I pasted the password just to be sure, and I did the same in nmtui on my Debian box. No problem. So both passwords are the same and correct. It's just graphene negotiation falls over.
-
@Zenie@piaille.fr 2026-05-07 15:26
@Kurt@chaos.social So digging through the logs there are a lot of errors Having to do with wifi supplicant and wifi in general. None of the debug files are present. Wlan0 is all good. It looks mostly normal, then gets worse and worse. The kernel doesn't support multicast. Connection was rejected. But doesn't say why. There are numerous errors could not find RSNE in EIs data. It dies after it sends the cfgvendor-send-supp-string. Association rejection for config 16 It's pretty vague for someone not versed in wpa-supplicant and android debug messages. I'm guessing it might make sense to someone who is more habituated to the log.