Vanet simulation with containernet/mininet-wifi

[SARRA KHABER]

Hello,

I am simulating a vehicular network using containernet and mininet-wifi (vehicles' class is DockerSta of containernet), I want to use the Wave protocol (ieee 802.11p) to connect vehicles so I am using ITSlink and adding it to each vehicle,

Now when I ping a vehicle from another vehicle to see the ping delay, it's not working,

Do I have to change anything in the ITSlink class code?

Thanks in advance.

[Ramon Fontes]

Please follow the instructions available at https://mininet-wifi.github.io/80211p/. If you happen to be following them, please provide details that might help me to help you. 

[SARRA KHABER]

I have followed the instructions and installed everything, but i still can't ping

I went to perform a ping in a simpler topology "vanet-sumo.py" of mininet-wifi, 

mininet-wifi> car1 ping 192.168.1.1 -c5
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.036 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.054 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.053 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.053 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.050 ms

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4093ms
rtt min/avg/max/mdev = 0.036/0.049/0.054/0.006 ms

mininet-wifi> car1 ping 192.168.1.2 -c5
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
From 192.168.1.1 icmp_seq=1 Destination Host Unreachable
From 192.168.1.1 icmp_seq=2 Destination Host Unreachable
From 192.168.1.1 icmp_seq=3 Destination Host Unreachable
From 192.168.1.1 icmp_seq=4 Destination Host Unreachable
From 192.168.1.1 icmp_seq=5 Destination Host Unreachable

--- 192.168.1.2 ping statistics ---
5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 4124ms
pipe 4

I also want to confirm this : will the latency of the ping increase when the distance between the vehicles increases?

Thank you

[Ramon Fontes]

> I have followed the instructions and installed everything, but i still can't ping

Technically speaking this doesn't help. Can you confirm that 5.9GHz is working? Did you perform wifi scanning? What else??

> I also want to confirm this : will the latency of the ping increase when the distance between the vehicles increases?

Yes.

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/e7fb162f-e498-4535-ae25-19ae53954a00n%40googlegroups.com.

[SARRA KHABER]

Hello,

here is the output of the commands :

sudo /sbin/regdbdump /lib/crda/regulatory.bin | grep -i ocb
country 00: invalid
    (5850.000 - 5925.000 @ 20.000), (20.00), NO-CCK, OCB-ONLY

iw reg get
global
country DE: DFS-ETSI
    (2400 - 2483 @ 40), (N/A, 20), (N/A)
    (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
    (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
    (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
    (5725 - 5875 @ 80), (N/A, 13), (N/A)
    (5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
    (57000 - 66000 @ 2160), (N/A, 40), (N/A)

Thank you

[SARRA KHABER]

Hello,

Could you please answer me?

There is not much documentation in the internet about this, and time is not in my favor,

Does configuring ieee 802.11p has anything to do with my actual hardware? (network card) or is it just a software thing (enabling it through commands)

Plus, I am running the setup on a ubuntu VM (Linux version 5.13.0-44-generic (buildd lcy02-amd64-107) (gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34)) and not on my host machine.

Thanks in advance

[Ramon Fontes]

Unfortunately, If you don't answer all the questions I won't be able to help you. 

Sent from my android

To view this discussion on the web visit https://groups.google.com/d/msgid/mininet-wifi-discuss/73046c86-72bc-4e0d-bca1-bba78c84d6f2n%40googlegroups.com.

[SARRA KHABER]

I have run certain commands to verify is 5.9GHz is working and here is the output

sudo /sbin/regdbdump /lib/crda/regulatory.bin | grep -i ocb
country 00: invalid
    (5850.000 - 5925.000 @ 20.000), (20.00), NO-CCK, OCB-ONLY

iw reg get
global
country DE: DFS-ETSI
    (2400 - 2483 @ 40), (N/A, 20), (N/A)
    (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
    (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
    (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
    (5725 - 5875 @ 80), (N/A, 13), (N/A)
    (5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
    (57000 - 66000 @ 2160), (N/A, 40), (N/A)

Thank you

[Ramon Fontes]

What about wifi scanning?? Did you run the code in debug level? 

Sent from my android

To view this discussion on the web visit https://groups.google.com/d/msgid/mininet-wifi-discuss/231ea76d-ac4f-4a35-9896-ddfeecdcb484n%40googlegroups.com.

[SARRA KHABER]

Hello,

yes I am running the code in debug level but it's not showing anything

and this is for the wifi scanning 

mininet-wifi> car1 iw dev car1-wlan1 scan 
command failed: Operation not supported (-95)
mininet-wifi> car1 iwlist car1-wlan1 channel
car1-wlan1  32 channels in total; available frequencies :
          Channel 01 : 2.412 GHz
          Channel 02 : 2.417 GHz
          Channel 03 : 2.422 GHz
          Channel 04 : 2.427 GHz
          Channel 05 : 2.432 GHz
          Channel 06 : 2.437 GHz
          Channel 07 : 2.442 GHz
          Channel 08 : 2.447 GHz
          Channel 09 : 2.452 GHz
          Channel 10 : 2.457 GHz
          Channel 11 : 2.462 GHz
          Channel 12 : 2.467 GHz
          Channel 13 : 2.472 GHz
          Channel 14 : 2.484 GHz
          Channel 36 : 5.18 GHz
          Channel 40 : 5.2 GHz
          Channel 44 : 5.22 GHz
          Channel 48 : 5.24 GHz
          Channel 52 : 5.26 GHz
          Channel 56 : 5.28 GHz
          Channel 60 : 5.3 GHz
          Channel 64 : 5.32 GHz
          Channel 100 : 5.5 GHz
          Channel 104 : 5.52 GHz
          Channel 108 : 5.54 GHz
          Channel 112 : 5.56 GHz
          Channel 116 : 5.58 GHz
          Channel 120 : 5.6 GHz
          Channel 124 : 5.62 GHz
          Channel 128 : 5.64 GHz
          Channel 132 : 5.66 GHz
          Channel 136 : 5.68 GHz

[Ramon Fontes]

I see no channel 181 as a frequency supported by your system.

Sent from my android

To view this discussion on the web visit https://groups.google.com/d/msgid/mininet-wifi-discuss/d5b2af42-6b89-497e-bdfa-f819526af644n%40googlegroups.com.

[SARRA KHABER]

I have followed the instructions to enable the 802.11p but in vain

Does that have something to do with my network card / network driver...etc? or would I have to add a module to the VM kernel?

[Ramon Fontes]

This seems to be an issue with the regulatory domain and/or network manager.

Sent from my android

To view this discussion on the web visit https://groups.google.com/d/msgid/mininet-wifi-discuss/4a07e8ab-3483-422d-b8cb-4ec1f9d0ef71n%40googlegroups.com.

[M. Arif Hakimi]

You may try this step to implement the new regulatory domain related to 802.11p after you have confirmed the OCB exist in the 

sudo /sbin/regdbdump /lib/crda/regulatory.bin | grep -i ocb
country 00: invalid
    (5850.000 - 5925.000 @ 20.000), (20.00), NO-CCK, OCB-ONLY

The steps:

After updating the regulatory database, you'll need to reload the cfg80211 kernel module for the changes to take effect:

sudo modprobe -r cfg80211
sudo modprobe cfg80211

Verify the changes:
Once the regulatory database is updated and cfg80211 is reloaded, you should verify that the changes have been applied. You can use the iw command to list the regulatory settings:
iw reg get

Setting the correct country (if necessary):
If you need to set the regulatory domain to a specific country, you can use the iw command:
sudo iw reg set <COUNTRY_CODE>

If and only if you got this error (refer below steps):

sudo modprobe -r cfg80211

modprobe: FATAL: Module cfg80211 is in use.

Identify the dependent modules:
Use the lsmod command to see which modules are using cfg80211:

lsmod | grep cfg80211
The output will show the modules that are dependent on cfg80211. These modules need to be unloaded before you can unload cfg80211.

Unload the dependent modules:
Based on the output from the previous step, unload each of the dependent modules. For example, if mac80211 is using cfg80211, you would do:

sudo modprobe -r mac80211

Repeat this for any other modules that are listed as dependent on cfg80211.

Retry unloading cfg80211:
Once all dependent modules are unloaded, try unloading cfg80211 again:

sudo modprobe -r cfg80211

Reload cfg80211:
Once successfully unloaded, you can reload cfg80211:
sudo modprobe cfg80211

Reload the dependent modules (if necessary):
If you unloaded other modules in step 2, you might need to reload them:
sudo modprobe mac80211

Then run the previous step again.

Regards,

Muhammad Arif Hakimi Zamrai