search

pbrah / wpa_supplicant-udmpro

110 stars 24 forks source link

UDM Base Stopped Authenticating #19

Open Stitchn99 opened 2 years ago

Stitchn99 commented 2 years ago

I have been running the WPA supplicant through multiple restarts, losses of power, and even moving to a new location (kept same service) and it has been stable over the past year. Out of no where it has failed. I have not looked at the files or messed with it in a very long time 

# podman start wpa_supplicant-udmpro
6a8f1d1b6388bdd7ac176d88884d8133ed15a5e1edd32d4a84dd73add111e9d6
# podman logs wpa_supplicant-udmpro
Successfully initialized wpa_supplicant
eth4: Associated with 01:80:c2:00:00:03
eth4: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
eth4: CTRL-EVENT-EAP-FAILURE EAP authentication failed
eth4: CTRL-EVENT-EAP-STARTED EAP authentication started
eth4: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13
eth4: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
eth4: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=ATT Services Inc/CN=ATT Services Inc Root CA'
bit2016 commented 2 years ago

Hi,

can you show what steps you have done? I saw a couple of websites but wasn't able to properly setup...

are you using the latest FW for the router?

On Fri, Jan 21, 2022 at 12:36 PM Stitchn99 @.***> wrote:

I have been running the WPA supplicant through multiple restarts, losses of power, and even moving to a new location (kept same service) and it has been stable over the past year. Out of no where it has failed. I have not looked at the files or messed with it in a very long time

podman start wpa_supplicant-udmpro

6a8f1d1b6388bdd7ac176d88884d8133ed15a5e1edd32d4a84dd73add111e9d6

podman logs wpa_supplicant-udmpro

Successfully initialized wpa_supplicant eth4: Associated with 01:80:c2:00:00:03 eth4: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 eth4: CTRL-EVENT-EAP-FAILURE EAP authentication failed eth4: CTRL-EVENT-EAP-STARTED EAP authentication started eth4: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13 eth4: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected eth4: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=ATT Services Inc/CN=ATT Services Inc Root CA'

— Reply to this email directly, view it on GitHub https://github.com/pbrah/wpa_supplicant-udmpro/issues/19, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEBFTZHVQC7YS6VSCI3PZTDUXG7TRANCNFSM5MQPW63A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you are subscribed to this thread.Message ID: @.***>

DavidMonostori commented 2 years ago

Did you check if the certificate is not expired? Mine is only good until 2024 so there is a possibility that you have reached the end of yours.

bit2016 commented 2 years ago

not sure. It was working on the previous USG but when I did the switch for the UDM-PRO it stopped working so I think it's the way I tried to set it up on the UDM-PRO.

Can you tell me the instructions you followed?

I saw a website that had instructions for a docker and a second one without it. I this I messed it up...

On Fri, Jan 21, 2022 at 3:54 PM DavidMonostori @.***> wrote:

Did you check if the certificate is not expired? Mine is only good until 2024 so there is a possibility that you have reached the end of yours.

— Reply to this email directly, view it on GitHub https://github.com/pbrah/wpa_supplicant-udmpro/issues/19#issuecomment-1018976452, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEBFTZFCXHLZJOE2WBOAFL3UXHW33ANCNFSM5MQPW63A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

Stitchn99 commented 2 years ago

Did you check if the certificate is not expired? Mine is only good until 2024 so there is a possibility that you have reached the end of yours.

I am not sure, how would I be able to check the date?

Stitchn99 commented 2 years ago

I was able to get it working using the code blocks from this GitHub. However, how can I ensure it won’t happen again?

raujaku commented 1 year ago

I was able to get it working using the code blocks from this GitHub. However, how can I ensure it won’t happen again?

Can you expand on what you did? I’m now having this same issue.