Unable to ping when running ieee80211p.py

[Marcilio Lemos]

Hi folks,

I tried to execute the pingall command when running examples/ieee80211p.py. I had installed all dependencies according to https://mininet-wifi.github.io/80211p/. Attached are the logs.

I'd appreciate any hint  from you. 

Thank you!

*** Ping: testing ping reachability

sta1 -> *** sta1 : ('ping -c1  10.0.0.2',)

PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.

From 10.0.0.1 icmp_seq=1 Destination Host Unreachable

--- 10.0.0.2 ping statistics ---

1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

X *** sta1 : ('ping -c1  10.0.0.3',)

PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data.

From 10.0.0.1 icmp_seq=1 Destination Host Unreachable

--- 10.0.0.3 ping statistics ---

1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

X 

sta2 -> *** sta2 : ('ping -c1  10.0.0.1',)

PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.

From 10.0.0.2 icmp_seq=1 Destination Host Unreachable

--- 10.0.0.1 ping statistics ---

1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

X *** sta2 : ('ping -c1  10.0.0.3',)

PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data.

From 10.0.0.2 icmp_seq=1 Destination Host Unreachable

--- 10.0.0.3 ping statistics ---

1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

X 

sta3 -> *** sta3 : ('ping -c1  10.0.0.1',)

PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.

From 10.0.0.3 icmp_seq=1 Destination Host Unreachable

--- 10.0.0.1 ping statistics ---

1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

X *** sta3 : ('ping -c1  10.0.0.2',)

PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.

From 10.0.0.3 icmp_seq=1 Destination Host Unreachable

--- 10.0.0.2 ping statistics ---

1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

X 

*** Results: 100% dropped (0/6 received)

[Ramon Fontes]

Hello Marcilio,

Can you confirm that your system has OCB working correctly? By the way, If I were you I wouldn't use the pingall command in scenarios where nodes have multiple interfaces.

[Marcilio Lemos]

Hi Ramon.

Thank you for your email. I got the following output by running ''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

Such an output is the same from https://mininet-wifi.github.io/80211p/

However, when running  "iw reg get" I get bellow output

global
country 00: DFS-UNSET
        (2402 - 2472 @ 40), (N/A, 20), (N/A)
        (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
        (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
        (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
        (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
        (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
        (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
        (57240 - 63720 @ 2160), (N/A, 0), (N/A)

On Tue, May 11, 2021 at 2:00 PM Ramon Fontes <ramonre...@gmail.com> wrote:

Hello Marcilio,

Can you confirm that your system has OCB working correctly? By the way, If I were you I wouldn't use the pingall command in scenarios where nodes have multiple interfaces.

--

Marcilio Olinto de Oliveira Lemos

MSc in Computer Science - Federal University of Paraíba 

BSc in Computer Science - Federal University of Paraíba

[Ramon Fontes]

It seems that 5.9GHz is not being activated by the regulatory domain. You have to solve it if you want to work with 802.11p.

[Marcilio Lemos]

Thank you Ramon.

Yeah, my linux is not using /lib/crda/regulatory.bin  when I run iw reg set DE.

Did you provide any VM supporting ieee802.11p for download?

Thanks

On Tue, May 11, 2021 at 2:42 PM Ramon Fontes <ramonre...@gmail.com> wrote:

It seems that 5.9GHz is not being activated by the regulatory domain. You have to solve it if you want to work with 802.11p.

[andres...@unicauca.edu.co]

See Master's Thesis - Charmae Franchesca Ugnaya Mendoza - IMPLEMENTATION AND EXPERIMENTAL EVALUATION OF COOPERATIVE AWARENESS BASIC SERVICE FOR V2X COMMUNICATIONS 

Appendix 5, 6, 8, 9, and 10.

[SARRA KHABER]

Hi,

How did you solve this problem please?

I have the same output, the frequency isnt showing with iw reg get (even the DE domain)

[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

[Prodromos Nasis]

Hello everyone!

I'm facing the same issue when running "ieee80211p.py" example. I'm following the instructions you provided about reloading the kernel modules and yet I don't see the frequencies when running the "iw reg get" command. I even tried to set the country in DE because I saw that in the db.txt file the required frequencies for that country exist, but still nothing. I also tried restarting the network-manager, but again nothing. I have tried the installation process on the ready-made lubuntu vm, but I have also performed a custom installation on a virtual machine running Ubuntu 20.04. In both cases I have exactly the same issue. Has anyone solved this problem? Can you help me? I would be grateful to you as it would help me to move forward with my BSc Τhesis. Thank you very much in advance for your time!

[Ramon Fontes]

Enabling 5.9GHz may not be (and usually is not) a trivial task. What I suggest is to use a recent kernel (+5.5) and Ubuntu as OS.