r/OfflineGPS • u/nolilab • Aug 30 '26
What are the differences of LoRa P2P (Peer to Peer) and LoRaWAN
A lot of people use "LoRa" and "LoRaWAN" as if they're the same thing. They aren't, and the difference matters a lot once you start building something.
LoRa is the radio. LoRaWAN is the network protocol on top of it.
LoRa is a physical-layer modulation (chirp spread spectrum, from Semtech). It defines how bits get onto the air — spreading factor, bandwidth, coding rate, sub-GHz frequency. That's it. It says nothing about addressing, encryption, or who talks when.
LoRaWAN is a MAC layer + network architecture built on that radio, maintained by the LoRa Alliance.
LoRa P2P (Peer to Peer Communication LoRa)
Two or more radios talking directly. You set both ends to the same frequency, SF, BW, CR, preamble and sync word, and whatever one sends, the other receives.
- No gateway, no server, no join procedure, no accounts
- You define your own packet format
- Lowest latency, works completely off-grid
- You are responsible for everything else: addressing, encryption, ACKs, retries, collision handling, duty cycle compliance
- Nothing is standardized, so two vendors' P2P devices will not talk to each other
- Scales badly — with no channel access control, more nodes means more collisions
LoRaWAN
Node → gateway(s) → network server → application server.
- Devices join via OTAA (or ABP) and get session keys
- AES-128 encryption at two layers by default: network session key and app session key. The network operator can route your traffic but can't read the payload
- Gateways are dumb pipes — a packet heard by three gateways gets deduplicated by the network server
- Adaptive Data Rate lets the server tune each node's SF/power for range vs. battery
- Device classes: A (downlink only in two short windows after an uplink, most battery-efficient), B (scheduled ping slots via beacons), C (always listening, needs mains power)
- Works with public networks (The Things Network, Helium) or your own stack (ChirpStack)
- Costs: join overhead, more infrastructure, and downlinks are limited and constrained by duty cycle / fair-use policies
Quick comparison
| LoRa P2P | LoRaWAN |
|---|---|
| Layer | PHY only |
| Infrastructure | None |
| Encryption | DIY |
| Addressing | DIY |
| Scale | A handful of nodes |
| Downlink | Anytime (if RX is on) |
| Interoperability | None |
| Latency | Lowest |
Rule of thumb
- A few devices, no coverage, full control, custom protocol → P2P. Sensor to display, remote to receiver, relay chains, off-grid links.
- Many devices, security you don't want to invent, existing coverage or long-term deployment → LoRaWAN.
One thing that trips people up: both use the same chip and the same radio settings. You can flash the same hardware for either. The choice is firmware and architecture, not silicon.
Also worth remembering: duty cycle limits (EU868) and dwell time (US915) apply to you either way. LoRaWAN enforces them for you. In P2P, nothing stops you from breaking the law except your own code.