handover scenario containernet - wifi

[Sarah K]

Hello, 

I am trying to make a handover scenario in a mininet wifi network with DockerSta stations.

i had no trouble running handover using mininet-wifi with my topology (i used bgscan).

But when my stations are now dockerSta, it doesnt work.

Actually, the associated AP is correct at first, but when i try to change the position of a station to a different AP, it shows me "Not-associated"

mininet-wifi> sta2 iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

sta2-wlan0  IEEE 802.11  ESSID:"vanet-ssid"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:00:00:11:00:01  
          Bit Rate:1 Mb/s   Tx-Power=1 dBm  
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=25/70  Signal level=-85 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

mininet-wifi> py sta2.setPosition('60,60,0')
mininet-wifi> sta2 iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

sta2-wlan0  IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm  
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
         
mininet-wifi> sta2 iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

sta2-wlan0  IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm  
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

I'll leave my file below

Thank you in advance

[Ramon Fontes]

It would be great if you provide more information about the issue. Do you have any useful information from bgscan on the client side? Or any conclusion other than connected/not connected?

Sent from my android

--
You received this message because you are subscribed to the Google Groups "mininet-wifi-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mininet-wifi-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mininet-wifi-discuss/26bc2f5f-8d3a-4a6e-9ee8-561da99b6f6bn%40googlegroups.com.

[Sarah K]

i performed a scan on its interface

mininet-wifi> sta2 iw dev sta2-wlan0 scan
BSS 00:00:00:11:00:01(on sta2-wlan0) -- associated
        last seen: 24091.127s [boottime]
        TSF: 1659122054105970 usec (19202d, 19:14:14)
        freq: 2412
        beacon interval: 100 TUs
        capability: ESS ShortSlotTime (0x0401)
        signal: -85.00 dBm
        last seen: 0 ms ago
        Information elements from Probe Response frame:
        SSID: vanet-ssid
        Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
        DS Parameter set: channel 1
        ERP: Barker_Preamble_Mode
        Extended supported rates: 24.0 36.0 48.0 54.0
        Supported operating classes:
                 * current operating class: 81
        Extended capabilities:
                 * Extended Channel Switching
                 * Multiple BSSID
                 * SSID List
                 * Operating Mode Notification

mininet-wifi> py sta2.setPosition('60,60,0')

mininet-wifi> sta2 iw dev sta2-wlan0 scan
BSS 00:00:00:11:00:01(on sta2-wlan0)
        last seen: 24091.127s [boottime]
        TSF: 1659122054105970 usec (19202d, 19:14:14)
        freq: 2412
        beacon interval: 100 TUs
        capability: ESS ShortSlotTime (0x0401)
        signal: -85.00 dBm
        last seen: 24012 ms ago
        Information elements from Probe Response frame:
        SSID: vanet-ssid
        Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
        DS Parameter set: channel 1
        ERP: Barker_Preamble_Mode
        Extended supported rates: 24.0 36.0 48.0 54.0
        Supported operating classes:
                 * current operating class: 81
        Extended capabilities:
                 * Extended Channel Switching
                 * Multiple BSSID
                 * SSID List
                 * Operating Mode Notification
BSS 00:00:00:11:00:02(on sta2-wlan0)
        last seen: 24121.999s [boottime]
        TSF: 1659122084978122 usec (19202d, 19:14:44)
        freq: 2437
        beacon interval: 100 TUs
        capability: ESS ShortSlotTime (0x0401)
        signal: -84.00 dBm
        last seen: 0 ms ago
        Information elements from Probe Response frame:
        SSID: vanet-ssid
        Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
        DS Parameter set: channel 6
        ERP: Barker_Preamble_Mode
        Extended supported rates: 24.0 36.0 48.0 54.0
        Supported operating classes:
                 * current operating class: 81
        Extended capabilities:
                 * Extended Channel Switching
                 * Multiple BSSID
                 * SSID List
                 * Operating Mode Notification

[Ramon Fontes]

I see no info about bgscan.. :(

Sent from my android

To view this discussion on the web visit https://groups.google.com/d/msgid/mininet-wifi-discuss/af84fa6e-7943-481c-9add-4a9a0bba2d51n%40googlegroups.com.

[Sarah K]

I have changed the AP args in my previous file as follow :

kwargs = {'ssid': 'vanet-ssid','mode':'g','passwd': '123456789a', 'encrypt': 'wpa2'}

now the stations aren't associated from the beginning, but there is a new file inside the container of each station :

root sta2:/# cat sta2-wlan0_0.staconf
ctrl_interface=/var/run/wpa_supplicant
network={
   ssid="vanet-ssid"
   psk="123456789a"
   proto=WPA2
   pairwise=CCMP
   key_mgmt=WPA-PSK
   bgscan="simple:5:-60:10"
}

I did not find this file when executing my previous code

If this info does not help you understanding the problem, can you specify some troubleshooting commands?