On Sep 1, 2017, at 1:20 PM, Matthew Pulis <mpulis@gmail.com> wrote:
I installed the server certificate on the client and we proceeded one step further. Now it is even more complicated because there are no errors yet the connection to WiFi is still failing.
The connection isn't failing. It's not *finishing*.
... (4) Sent Access-Challenge Id 194 from 192.168.100.201:1812 to 192.168.100.116:34201 length 0 (4) EAP-Message = 0x016b003d158000000033140303000101160303002846f2bdbd4e3a5070b7581cc10130c36dfec89071bcc2e5e14a65ffe690ae1ba4cbce11f94d6dc8be (4) Message-Authenticator = 0x00000000000000000000000000000000 (4) State = 0x11d6614f15bd743baa2bd1cfb9605e94 (4) Finished request Waking up in 4.9 seconds. (0) Cleaning up request packet ID 190 with timestamp +37 (1) Cleaning up request packet ID 191 with timestamp +37 (2) Cleaning up request packet ID 192 with timestamp +37 (3) Cleaning up request packet ID 193 with timestamp +37 (4) Cleaning up request packet ID 194 with timestamp +37 Ready to process requests
If you leave the server there for a while, it will then print out a message that you should read. Again, follow the guide I posted. It has a series of steps you can take to configure the system. Alan DeKok.