> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/home-cloud-white-papers/airguard/rf-jamming.md).

# RF Jamming

Radio Frequency or RF Jamming is one of the easiest methods of defeating a wireless system – the wireless equivalent of cutting the wires on a traditional wired system. The open medium nature of WiFi makes it vulnerable to various attacks, among them, attacks against availability is wifi jamming. WiFi jamming sends a lot of noise in the environment, making it impossible for other nodes to send messages through available channels.

## Types of RF Jamming

AirGuard is capable of detecting four types of RF jamming:

1. Constant Jammer:

   Continually emits a radio signal that interferes with communication.
2. Deceptive Jammer:

   Constantly injects regular packets to the channel without following CSMA/CA procedure.
3. Random Jammer:

   Intermittently emits the jamming signal.
4. Reactive Jammer:

   Jam and simultaneously sense/discern/detect the legitimate transmission.

## Detecting RF Jamming

**AirGuard** adopts unique technologies to detect all types of RF jamming while keeping a very low fail rate on the detection. That is, the system would not easily treat massive transmission of WiFi data as an RF Jamming attack. In contrast, the signal interference sent by a jammer can be efficiently detected in seconds.

![](https://2788256466-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lo1AtG4HHv3uJq1FqqB%2Fuploads%2FMIxG73Y25AgUcKNWzRnz%2Fimage.png?alt=media\&token=795e6bf7-2a75-45c6-afc4-4d591740774c)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.engenius.ai/home-cloud-white-papers/airguard/rf-jamming.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.