-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
inform new client ip4 address during SYSTEM_EVENT_AP_STAIPASSIGNED (IDFGH-563) #2949
Comments
Sorry, I can't catch you. Isn't IP address in the event information? |
Yes in current implementation it just sends empty event, the modified code is proposed method
…-----Original Message-----
From: TimXia <notifications@github.com>
To: espressif/esp-idf <esp-idf@noreply.github.com>
Cc: swk <swk@swkemb.com>, Author <author@noreply.github.com>
Sent: Tue, 15 Jan 2019 16:50
Subject: Re: [espressif/esp-idf] [TW#28414] inform new client ip4 address during SYSTEM_EVENT_AP_STAIPASSIGNED (#2949)
Sorry, I can't catch you. Isn't IP address in the event information?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#2949 (comment)
|
@123swk123 OK, we will add it. Thanks for your suggestion. |
@123swk123 Thanks, it's a good idea. We can add it in v4.0 |
Should have searched here before, I basically came up with the same changes. I'll be patching my v3.1 branch for this change. Its kind of scary we initialize the event with random values and pass over the event to the user without an explanation on what is expected to be populated, talk about potential debugging headaches... A quick search through the code base shows at least 5 spots in +1 to @123swk123's code, here is a follow up with the event zero'd out.
I'd also like to add there is no documentation for the event. |
in the soft AP mode, when a new client connects SYSTEM_EVENT_AP_STAIPASSIGNED is raised and it would be good if it also has additional information about which IP address it has assigned to its new client in the event information.
some thing like below.
The text was updated successfully, but these errors were encountered: