OneNet Gateways
The heart of OneNet: bridging NMEA 2000 buses onto IP, joining multiple 2000 networks across a vessel, and moving PGNs bidirectionally between the bus and the Ethernet backbone — designed against the module we helped author.
OneNet is NMEA's Ethernet standard — NMEA 2000 data over IPv6, at the bandwidth radar, video, and dense sensor streams demand. We design the gateways, firmware, and certified devices that put a vessel on it.
OneNet is NMEA's Ethernet-based marine standard — built on IPv6 and IEEE 802.3. It carries NMEA 2000 PGNs over IP, links multiple NMEA 2000 networks together, and opens the bandwidth for data the 250 kbit/s NMEA 2000 bus was never meant to carry: radar, camera video, and dense sensor streams.
Big Cove's founder serves on the NMEA OneNet standards committee and co-authored the OneNet Gateway module. When you build a OneNet gateway or a certified OneNet device with us, you're working with someone who helped write the specification — not someone reading it for the first time. It's the natural next layer on our NMEA 2000 and 0183 development work.
The heart of OneNet: bridging NMEA 2000 buses onto IP, joining multiple 2000 networks across a vessel, and moving PGNs bidirectionally between the bus and the Ethernet backbone — designed against the module we helped author.
Transporting NMEA 2000 PGNs over IPv6 — multicast distribution, addressing, and the high-bandwidth payloads (radar, video, sonar) that outgrow the CAN bus, delivered cleanly over Ethernet.
OneNet is the first NMEA standard with a real security model. We implement its TLS and X.509 certificate handling — device identity, authentication, and encrypted transport — the part NMEA 2000 never had.
Designing OneNet devices and gateways for certification from the first schematic — hardware, firmware, and the conformance behavior the standard requires — so the product passes, not just works on the bench.
| Attribute | NMEA 2000 | NMEA OneNet |
|---|---|---|
| Physical layer | CAN bus | Ethernet (IPv6 / IEEE 802.3) |
| Speed | 250 kbit/s | 100 Mbit/s–1 Gbit/s+ |
| Data format | Binary PGNs | NMEA 2000 PGNs over IP |
| Security | None | TLS + X.509 certificates |
| Best for | Instruments & sensors | Radar, video, displays, dense streams, linking networks |
| Status | Current mainstream standard | Emerging high-bandwidth standard |
OneNet doesn't replace NMEA 2000 — it carries it. The gateway between the two is exactly the piece we build.
Bridging marine networks is what we do. The Nemo Gateway already fuses NMEA 2000 and 0183 with automatic sensor failover; OneNet is the same discipline at Ethernet scale — and one we helped specify. From a single certified device to a full OneNet backbone, we build the bridge.
OneNet is NMEA's Ethernet-based marine standard, built on IPv6 and IEEE 802.3. It carries NMEA 2000 PGNs over IP at high bandwidth — enough for radar, video, and dense sensor streams the 250 kbit/s NMEA 2000 bus can't handle — and adds a real security layer. It complements NMEA 2000 rather than replacing it.
NMEA 2000 is a 250 kbit/s CAN bus for instruments and sensors. OneNet runs the same data over Gigabit-class Ethernet and IPv6, so it can carry high-bandwidth payloads and link multiple NMEA 2000 networks together. OneNet also adds TLS and certificate-based security — something NMEA 2000 has never had.
A OneNet gateway bridges NMEA 2000 buses onto the OneNet Ethernet network — moving PGNs between the CAN bus and IP, and joining separate NMEA 2000 segments across a vessel into one network. It's the core piece of a OneNet system, and the module our founder co-authored.
Yes. We design OneNet devices and gateways for certification from the start — hardware, firmware, the IPv6 and security stack, and the conformance behavior the standard requires — and guide the product through the process.
Yes — security is built into the standard. OneNet uses TLS and X.509 certificates for device identity, authentication, and encrypted transport. We implement that security model as part of any OneNet device or gateway we build.
Tell me about the network, the data, and where it needs to go. I helped write the gateway spec; I'll tell you how I'd build it.
Set a course info@bigcove.io