Help using this tool #2

[christianberry7]

Hello, I read the last issue created (April 12 2022) and I believe specifying the interface for the OTA may be my issue.

I am running the basic emane80211.py script with two nodes and the EmaneIeee80211abgModel. These seem to default to bandwidth=1000000 / frequency 2347000000. I have ran emane-jammer-simple --power 30 11 2347000000 -v. the default port and group (224.1.2.8/45702) already match up with the defaults of the nodes / emane in the GUI, and verbose is letting me know that it is jamming 2347000000. I have tried various -i but pinging between nodes always results in 0% packet loss. What am I missing?

And side note: this will never affect the visual GUI link between the nodes because that is strictly distance based, correct? or is there a Model that I can switch to that accounts for packet loss %?

[patelkb]

Take a look at the example in the EMANE guide: https://emane.io/ieee80211abg-radio-model It has an example with the emane-jammer-simple and should shows you what to look for. kb Kaushik B. Patel Adjacent Link LLC CEO, Director of Engineering

…

On 12/15/23 14:48, christianberry7 wrote: Hello, I read the last issue created (April 12 2022) and I believe specifying the interface for the OTA may be my issue. I am running the basic emane80211.py script with two nodes and the EmaneIeee80211abgModel. These seem to default to bandwidth=1000000 / frequency 2347000000. I have ran emane-jammer-simple --power 30 11 2347000000 -v. the default port and group (224.1.2.8/45702) already match up with the defaults of the nodes / emane in the GUI, and verbose is letting me know that it is jamming 2347000000. I have tried various -i but pinging between nodes always results in 0% packet loss. What am I missing? And side note: this will never affect the visual GUI link between the nodes because that is strictly distance based, correct? or is there a Model that I can switch to that accounts for packet loss %? — Reply to this email directly, view it on GitHub <#2>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABPLXMZPS34MQCVBQHJTUYLYJSSSBAVCNFSM6AAAAABAW5GOKOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2DIMRZGEYDOOI>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[christianberry7]

Hello, I've followed the example and I can generate part of the final tone (ieee..abg-01 letce2 call works and shows up in spectrum analyzer) but I am still having issues with the emane-jammer-simple.

I have tried running the "emane-jammer-simple-control -v node-4:45715 on 4 2390000000,-20 -a omni" but the subid 65535 doesn't show up in the spectrum analyzer.

additionally I have tried starting emane-jammer-simple-service with:
"emane-jammer-simple-service --config-file ./Documents/emane-guide/examples/ieee80211abg-01/emane-jammer-simple-service.xml --pid-file ./Documents/emane-guide/examples/ieee80211abg-01/persist/jammer-4/var/run/emane-jammer-simple-service.pid --daemonize"

What am I missing for the simple-jammer?

[sgalgano]

Have you verified that you are setting the pathloss or location, depending on physical layer propagationmodel: precomputed or freespace, between the jammer source nem and the destination nem(s) (including the nem id of the emane-sprectrum-monitor instance?

[christianberry7]

The example states that all physical layers are configured to use the precomputed propagation model with the values in pathloss.eel. Where do I go about specifying/referencing this file (pathloss.eel), is this in the call to emane-jammer-simple-control call or does this have to do with simple-service or something else entirely?