I observe the same issue, it seems link_up only work once.
My test is very simple that just print something in link_up/down callback.
The second time turn off AP than turn on AP, I don'e see link_up get called.
Yeah it works sometimes, rest of the time it doesn't. Very much
To resolve this problem, I start a thread which scans available networks
and as soon as it finds one same as configured in dct, it will try to
As soon as connection is done, it goes into link_up handler.
Shatruddha Singh Kushwaha
On Fri, Feb 6, 2015 at 9:55 AM, sam.lin <
Another strange thing I noticed today
Before that, a prelog to what I'm doing :
I'm sending a "Hi" on ip address 188.8.131.52 at port 80.
At first startup it all works fine, when I disconnected and reconnected, I'm obtaining a new IP address through DHCP.
Now in my observation I see that after reconnecting and obtaining new IP address, the message that I'm sending is still being sent using the previous IP address.
I checked in my router log to see all the transactions happening through my router. There I see my my device has an IP address 192.168.1.141 and my old IP address before reconnect was 192.168.1.133.
In the messages sent after reconnect, I still see packets being sent using 192.168.1.133.
So clearly new IP address obtained is not replacing the old one in the stack. I'm unable to find out where this is set.
Can anybody help?
Could you please provide sniffer trace for this test?
Discussion is being locked. If you have follow-up, please start a new discussion.