Custom OpenWrt engineering for your network products
Xinan develops OpenWrt firmware and embedded network systems: board support, driver integration, network policies, phone-based management, branded interfaces and production handover. We scope work around your devices and real use cases, beyond installing packages.
Choose a scope for your devices and workflows
- Branded routers and gateways
- For device makers and integrators: boot configuration, policies, LuCI pages, business packages and production images with diagnostics and recovery.
- Portable cellular and phone integration
- Assess QMI/MBIM, ModemManager, USB tethering, reconnection and phone management for portable routers and field work; validate the modem and carrier.
- Retail and multi-site networks
- Connect ordering, POS, robots and office networks with scoped VLANs, guest isolation, uplink failover and authorized maintenance; test interfaces and switching.
- Industrial and edge systems
- Integrate Ethernet, serial, USB and scoped field protocols for telemetry, edge AI and energy systems; a general gateway does not replace a real-time safety controller.
Engineering across the system stack
- Board and driver integration
- Review SoC, device tree, boot partitions, flash and ports; assess radio/modem drivers and vendor SDKs, then record supported models.
- System services and interfaces
- Develop around UCI configuration, ubus IPC and procd service lifecycle, defining permissions, errors, logs and configuration migration.
- Network policies and isolation
- Scope netifd, DSA/VLAN, firewall4/nftables, IPv4/IPv6 and DNS by release; evaluate SQM, multi-WAN and authorized WireGuard connections per use case.
- LuCI and mobile management UX
- Build branded themes, plugins, setup and diagnostic pages with touch access, role permissions and local management; native apps are a separate scoped integration.
- Traceable builds and production
- Pin source, toolchain, feeds and configuration; track patches and dependencies, supplying required source, build notes, checksums and flashing instructions under applicable licenses.
- Updates, security and recovery
- Plan image verification, release authorization, backups, failed-upgrade handling and maintenance. A/B and power-loss recovery require partition and boot support plus interruption tests.
Mobile OpenWrt: define the device before the experience
Mobile may mean portable 4G/5G router firmware, a phone connecting to or managing an OpenWrt gateway, or a feasibility study for specific phone hardware. The first two do not replace the phone OS. Native installation requires model-specific boot, kernel, driver and recovery validation; Android and iPhone compatibility is not assumed.
Confirm board, SoC, flash layout, boot chain, radio/modem drivers and permissions before testing throughput, latency, stability, upgrades and recovery. No universal phone flashing or performance promise.
From the lab to practical use cases
AI-generated engineering and usage concepts, not delivered customer projects.
Device makers: productized firmware
From serial debugging to production configuration: validate boot, ports, radio, upgrades and recovery with a supported-model list and release traceability.
Field teams: portable connectivity
A portable cellular gateway handles connectivity and policy; the phone manages settings and status. Validate signal, power, data plans and continuity; no unconditional uptime promise.
Retail sites: separate business and guest traffic
Define access for ordering, POS and robots, isolate guest networks and plan recovery with existing business systems. Validate outcomes on site.
From requirements to validated firmware
Requirements and hardware review
Agree use cases, models, permissions, interfaces, targets and maintenance term; record feasibility and risks.
Bring-up and prototype
Validate boot, console, networking and key drivers with one representative workflow.
Feature and management integration
Integrate policies, UI, packages and business interfaces with permissions and failure handling.
Load and recovery acceptance
Record version, environment, load and results; test disconnection, restart, interrupted upgrades and recovery. Performance comes from agreed tests.
Handover, production and maintenance
Deliver images, build configuration, license material and operating/recovery guides; agree vulnerability maintenance, support and change control.
Handover and acceptance
- Hardware support matrix and feature scope
- Images, checksums, build configuration and dependencies
- Source, patches and notices required by applicable licenses
- Interface documentation, operating and recovery guides
- Test records, known limitations and production checks
Compatibility and acceptance limits
Confirm board, SoC, flash layout, boot chain, radio/modem drivers and permissions before testing throughput, latency, stability, upgrades and recovery. No universal phone flashing or performance promise.
Technical references
- Official: ubus interfaces
- Official: firewall configuration
- Official: smartphone USB tethering
- Official: cellular networking
- Official: firmware upgrades and backups
Independent development service, not endorsed by the OpenWrt project. Images are AI-generated concepts. Features depend on the selected release, device and contract. Confirm radio, modem and carrier requirements separately, together with open-source, driver and trademark rights.
Discuss firmware requirements
Share the board model, use case, interfaces, connectivity, expected volume and maintenance period. We assess compatibility and risks before quoting milestones.
Discuss firmware requirements