Timeline for Using a pi as a wireless access point with bridge - incorrect password
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 14, 2021 at 3:50 | answer | added | DeathByPiano | timeline score: 0 | |
| Mar 2, 2020 at 13:43 | answer | added | Ingo | timeline score: 1 | |
| Feb 28, 2020 at 14:19 | comment | added | Chris Schmitz | also @JaromandaX I added an update to the post after doing some more troubleshooting, still stuck, but I've def narrowed the issue down to something to do with the bridge or how it's hooked up. | |
| Feb 28, 2020 at 14:18 | history | edited | Chris Schmitz | CC BY-SA 4.0 |
adds more detail from continued troubleshooting, corrects command name
|
| Feb 28, 2020 at 14:04 | comment | added | Chris Schmitz | @JaromandaX I mistyped, it's the hash I pulled out of the wpa_passphrase command that I tried as the wpa_psk value in the hostapd.conf file. Also yeah, I was originally using the passphrase and that stopped working when I added the bridge which is when I tried the psk :/ I'm going to try re-generating the psk this morning, but I'm positive I copy/pasted it correctly. | |
| Feb 28, 2020 at 5:32 | comment | added | Jaromanda X | generated by the wpa_supplicant command - you mean by the wpa_passphrase command? try using a wpa_passphrase instead of a wpa_psk - if that works, then you've botched the wpa_psk somehow - edit: oh, you did use a passphrase originally after the bridge? | |
| Feb 28, 2020 at 4:30 | review | First posts | |||
| Feb 28, 2020 at 8:47 | |||||
| Feb 28, 2020 at 4:30 | history | asked | Chris Schmitz | CC BY-SA 4.0 |