Announcement

Collapse
No announcement yet.

Mux: No notification about change in WiFi state when using W command

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mux: No notification about change in WiFi state when using W command

    Hi,
    this is a follow up/possible explanation for a previous thread.

    I'm creating several sockets to listen on the Mux interface:

    Code:
    0a5555TCP
    1h
    2a5556TCP
    Then I use W to wait for incoming connections and set the host to sleep until I get an RX interrupt on the UART:

    Code:
    W0r1r2r
    The device will stay in this state for several hours.

    Now what I've noticed is the following: When I change the WiFi network in the Web Interface (or for that matter, xPico decides to reconnect on it's own), I don't get any message on the mux.

    The sockets are now invalid, but they are still open:

    HTML Code:
    2017-05-03 14:50:24,650 - INFO # status Diagnostics IP Sockets>show
    2017-05-03 14:50:24,650 - INFO # 
    2017-05-03 14:50:24,681 - INFO # Diagnostics IP Sockets Status:
    2017-05-03 14:50:24,682 - INFO # 
    2017-05-03 14:50:24,745 - INFO # IP Socket 1 : UDP, 0, 0, ap0: 67, - , Listen
    2017-05-03 14:50:24,745 - INFO # 
    2017-05-03 14:50:24,825 - INFO # IP Socket 2 : UDP, 0, 0, ap0: 53, - , Listen
    2017-05-03 14:50:24,825 - INFO # 
    2017-05-03 14:50:24,888 - INFO # IP Socket 3 : TCP, 0, 0, ap0: 80, - , Listen
    2017-05-03 14:50:24,904 - INFO # 
    2017-05-03 14:50:24,968 - INFO # IP Socket 4 : TCP, 0, 0, ap0: 5555, - , Listen
    2017-05-03 14:50:24,968 - INFO # 
    2017-05-03 14:50:25,032 - INFO # IP Socket 5 : TCP, 0, 0, ap0: 5556, - , Listen
    2017-05-03 14:50:25,047 - INFO # 
    2017-05-03 14:50:25,111 - INFO # IP Socket 6 : TCP, 0, 0, ap0: 5557, - , Listen
    2017-05-03 14:50:25,112 - INFO # 
    2017-05-03 14:50:25,190 - INFO # IP Socket 7 : UDP, 0, 0,wlan0: 68, - , Listen
    2017-05-03 14:50:25,191 - INFO # 
    2017-05-03 14:50:25,254 - INFO # IP Socket 8 : TCP, 0, 0,wlan0: 5555, - , Listen
    2017-05-03 14:50:25,254 - INFO # 
    2017-05-03 14:50:25,334 - INFO # IP Socket 9 : TCP, 0, 0,wlan0: 5556, - , Listen
    2017-05-03 14:50:25,334 - INFO # 
    2017-05-03 14:50:25,397 - INFO # IP Socket 10: TCP, 0, 0,wlan0: 5557, - , Listen
    2017-05-03 14:50:25,398 - INFO # 
    2017-05-03 14:50:25,477 - INFO # IP Socket 11: TCP, 0, 0,wlan0: 80, 10.42.0.1:55888, Syn Received
    2017-05-03 14:50:25,477 - INFO # 
    2017-05-03 14:50:25,556 - INFO # IP Socket 12: UDP, 0, 0,wlan0:30718, - , Listen
    But I can't connect to them as they are still bound to the old IP.

    There doesn't seem to be any way to get notified about such network change to re-create those sockets.

    This issue persists with the latest firmware 1.5.0.0A25
Working...
X