Mininet-wifi Installion Hostap Failed

23 views
Skip to first unread message

University Mail

unread,
Jul 10, 2025, 4:32:28 AMJul 10
to mininet-wifi-discuss
Dear Mr. Ramonre,

Could you suggest me how to solve this issue hostap failed when I install mininet-wifi with " sudo util/install.sh -Wlnfv "

/home/aung/mininet-wifi /home/aung/mininet-wifi
/home/aung/mininet-wifi/hostap /home/aung/mininet-wifi /home/aung/mininet-wifi
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/hostapd/defconfig b/hostapd/defconfig
|index 550db697b..41e5200e9 100644
|--- a/hostapd/defconfig
|+++ b/hostapd/defconfig
--------------------------
File to patch: 

Ramon Fontes

unread,
Jul 10, 2025, 5:27:28 AMJul 10
to University Mail, mininet-wifi-discuss
Fixed in https://github.com/intrig-unicamp/mininet-wifi/commit/fd6c7c00e992946597baccab053f48e9a657f187

Em qui., 10 de jul. de 2025 às 05:32, 'University Mail' via
mininet-wifi-discuss <mininet-wi...@googlegroups.com> escreveu:
> --
> 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 visit https://groups.google.com/d/msgid/mininet-wifi-discuss/66089aeb-cdc0-454f-8ff7-d64ef29f552cn%40googlegroups.com.

Wang Rui Xing

unread,
Jul 11, 2025, 9:21:44 AMJul 11
to mininet-wifi-discuss
Dear Mr. Ramon,

Thank you. I solved it. I checked your mentioned link, and I updated my local mininet-wifi repository with"
git pull origin master" and delete "sudo rm -rf ~/mininet-wifi/hostap " after that installed again with "sudo util/install.sh -Wlnfv."

I have another issue, sir. Could you suggest to me how to solve the "DORMANT" status when I check the IP address? The station node WLAN link is connected to the AP and has IPv6 and a default route assigned by me.


mininet-wifi> car1 ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
48: car1-wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 qdisc mq state DORMANT group default qlen 1000
    link/ether 00:00:00:00:00:33 brd ff:ff:ff:ff:ff:ff
    inet6 2001:10::2/64 scope global tentative
       valid_lft forever preferred_lft forever

mininet-wifi> car1 ip -6 route
2001:10::/64 dev car1-wlan0 proto kernel metric 256 pref medium
default via 2001:10::1 dev car1-wlan0 metric 1024 pref medium

mininet-wifi> car1 iw dev car1-wlan0 link
Connected to 02:00:00:00:04:00 (on car1-wlan0)
SSID: ssid1
freq: 2412.0
RX: 71911 bytes (1679 packets)
TX: 395 bytes (6 packets)
signal: -64 dBm
tx bitrate: 1.0 MBit/s
bss flags: short-slot-time
dtim period: 2
beacon int: 100

Ramon Fontes

unread,
Jul 11, 2025, 9:29:06 AMJul 11
to Wang Rui Xing, mininet-wifi-discuss
The 'Dormant' status is related to the network layer. We'll need a
better understanding of your scenario in order to assist you.

Em sex., 11 de jul. de 2025 às 10:21, Wang Rui Xing
<aungsanli...@gmail.com> escreveu:
> To view this discussion visit https://groups.google.com/d/msgid/mininet-wifi-discuss/856bf26d-0b38-41aa-be83-8f172d5339c6n%40googlegroups.com.

University Mail

unread,
Jul 15, 2025, 10:11:40 AMJul 15
to mininet-wifi-discuss
Dear Mr. Ramon,  

Please allow me to explain my scenario. I am testing UDP connectivity using iperf from the station node car1 to the web_server. 
  1. The station is within the range of AP1AP2 and AP3 its wlan0 link shows a 'Dormant' status.
 The virtual connection flow is:
car1 → ap1 → sw1 → r1 → ms_mr → web_server.  
 
The default gateway for the station is r1-eth0, and it has been correctly assigned.
r1-eth0@if38: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 46:ea:0d:b1:55:c0 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 2001:10::1/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::44ea:dff:feb1:55c0/64 scope link
       valid_lft forever preferred_lft forever  

Summarization: 
car1 wlan link is  'Dormant' status. car1 station has a default route and IP in the same network as the gateway. r1-eth0 has assigned IP in the same network as the car1 station. Kindly let me know if there’s anything else you need from my scenario more.

Here is my topology net link. 
ms_mr ms_mr-eth0:r1-eth2 ms_mr-eth1:r2-eth2 ms_mr-eth2:web-eth0
web web-eth0:ms_mr-eth2
s1 lo:  s1-eth1:ap1-eth2 s1-eth2:ap2-eth2 s1-eth0:r1-eth0
s2 lo:  s2-eth1:ap3-eth2 s2-eth0:r2-eth0
ryu_ctrl
car1 car1-wlan0:wifi
ap1 lo:  ap1-wlan1:wifi ap1-eth2:s1-eth1
ap2 lo:  ap2-wlan1:wifi ap2-eth2:s1-eth2
ap3 lo:  ap3-wlan1:wifi ap3-eth2:s2-eth1

Screenshot 2025-07-12 202642.png

Ramon Fontes

unread,
Jul 16, 2025, 6:48:53 AMJul 16
to University Mail, mininet-wifi-discuss
This is strange. The interface seems to be up and ready, but waiting for lower-layer communication to begin (typically waiting for carrier or association in wireless). Could you use WPA with bgscan?

University Mail

unread,
Jul 17, 2025, 5:01:51 AMJul 17
to mininet-wifi-discuss
Dear Mr. Ramon, 

Thank you so much I got it. Here is my step by step configuration to solve "Dormant" status.  I need to apply the same method to another station within the ranges of AP2 and AP3, just as I did with AP1.

Step 1: Create a WPA config file for car1

wpa_passphrase ssid1 mypassword > /tmp/car1.conf
nano /tmp/car1.conf

network={
        ssid="ssid1"
        psk="mypassword"
        #psk="074d7580516767d9454ba354bb67577644005e9a9f00ee5f96b2d54b533ba942"
        scan_ssid=1
        key_mgmt=WPA-PSK
        bgscan="simple:30:-70:300"
}

Step2: Modify the Mininet-WiFi Python script

ap1 = net.addAccessPoint('ap1', ssid='ssid1', mode='g', channel='1', range='100', position='100,50,0', encrypt='wpa2', passwd='mypassword')
car1.cmd('rm -f /var/run/wpa_supplicant/car1-wlan0')
car1.cmd('wpa_supplicant -B -i car1-wlan0 -c /tmp/car1.conf')


University Mail

unread,
Jul 17, 2025, 5:01:57 AMJul 17
to mininet-wifi-discuss
Dear Mr. Ramon, 

That is second mail. After I have configured the code below, I encountered car1 station a non-seamless connection issue when moving from AP1 to AP3.

I have three access points: AP1, AP2, and AP3. The car1 station must move from AP1 to AP3. WPA with bgscan is currently configured only for AP1. When car1 moves to AP2 and AP3, UDP packets are dropped, and the car1-wlan0 interface does not connect to AP2 or AP3. 

How can I achieve a seamless connection when moving between different APs? 

If I don't use this command in my mininet-wifi python script "car1.cmd('wpa_supplicant -B -i car1-wlan0 -c /tmp/car1.conf')",  the car1 station wlan link will "Dormant" status. 

nano /tmp/car1.conf
network={
        ssid="ssid1"
        psk="mypassword"
        #psk="074d7580516767d9454ba354bb67577644005e9a9f00ee5f96b2d54b533ba942"
        scan_ssid=1
        key_mgmt=WPA-PSK
        bgscan="simple:30:-70:300"
}

    # Access Points

    ap1 = net.addAccessPoint('ap1', ssid='ssid1', mode='g', channel='1', range='100', position='100,50,0',
                                                     encrypt='wpa2', passwd='mypassword')
    ap2 = net.addAccessPoint('ap2', ssid='ssid2', mode='g', channel='6', range='100', position='250,50,0')
    ap3 = net.addAccessPoint('ap3', ssid='ssid3', mode='g', channel='11', range='100', position='400,50,0')

On Wednesday, July 16, 2025 at 5:48:53 PM UTC+7 ramonre...@gmail.com wrote:

Ramon Fontes

unread,
Jul 17, 2025, 6:21:32 AMJul 17
to University Mail, mininet-wifi-discuss
The SSID must be the same if you want to have seamless handover.

Reply all
Reply to author
Forward
0 new messages