Deployment profile
Fixed wireless access with less protocol overhead
On a radio link, every byte of framing costs capacity and every session protocol adds state to maintain. Netvyn lets you run DHCP-based access with the subscriber identified by the network, so the air interface carries traffic rather than session keepalives.
Typically deployed by
- Fixed wireless access networks
- Rural and hard-to-reach coverage
- Point-to-multipoint sectors
- Mixed wireless and fibre footprints
01 What matters here
Built for how this network actually behaves
The four decisions that make the difference on this kind of network.
IPoE where PPP costs too much
DHCP-based access removes per-session protocol overhead from the radio path.
Identity from the network
The access point or switch identifies the circuit, so identity does not depend on subscriber-side configuration.
Sector-level fairness
Subscriber limits nest under an aggregate representing a sector or backhaul link.
Public IPv4 stretched
Carrier NAT lets a small address holding cover a growing subscriber base.
02 Deployment shape
How it is put together
Sizing is a conversation about your server, your access model and the services you enable. Your licence is sized on concurrent sessions or on throughput, perpetual or subscription, and every service is included either way.
| Access model | IPoE with MAC or circuit identity; PPPoE also available |
|---|---|
| Bandwidth | Per-subscriber shaping under sector or backhaul aggregates |
| Addressing | Private addressing with carrier NAT, or public where available |
| Identity | Access-node circuit information, or client MAC |
| Growth | Add sectors without redesigning the gateway |
Other solutions
Size a gateway for your network
Bring your subscriber counts, access model and address plan. We size against your hardware, not a product tier.