Quickstart
Create a network, install and approve two devices, then verify overlay connectivity.
Choose a site
WideWired provides a mainland China site and a global site. They use different data storage locations, and their accounts, networks and balances are independent. Choose according to your preferred data storage location before registering. This guide covers the global site.
Prerequisites
- Two Linux or Windows devices. They need neither public IPs nor a shared local network. For macOS or mobile devices, follow the app steps in Devices, then return to approval and connectivity checks below.
- Administrator rights on both devices:
sudoon Linux, an elevated PowerShell on Windows. - A browser with access to the console.
Create an account
Open sign up / sign in, register with an email address and password, and complete email verification. Field and verification rules are covered in Signing up and signing in.
Create a network
After sign-in, choose New network from the network picker at the top of the console. On a first visit, follow the create-network prompt. Set:
- Name: a display name you can change later.
- Internal IP range: the private CIDR used by the overlay. Keep it disjoint from every device LAN and your other virtual networks; the default is suitable when you have no existing address plan.
The new network receives a 12-character network ID, for example k7m2p9x4rt6n. The ID is used for device registration, not authentication; a device still needs approval before it can communicate.
Install the client
Open Configuration → Devices in the console and select an installation platform under How it works. The generated command already contains the site domain and current network ID. Copy it directly; do not substitute the angle-bracket examples by hand.
Linux:
curl -fsSL https://<your site's API domain>/wwnet/install/join/<network-id>.sh | sudo sh
Windows (Administrator PowerShell):
# Run in PowerShell as Administrator
iex (irm "https://<your site's API domain>/wwnet/install/join/<network-id>.ps1")
The installer downloads and verifies the client, completes installation, and registers the device with the network ID. Run it once on each device. Platform requirements are covered under Devices.
Approve the devices
Newly registered devices are Pending. Under Configuration → Devices, verify each hostname and platform, then approve both devices. Once Approved, they start establishing connections.
Verify connectivity
Run on both devices:
wwnet
Confirm that status is connected and note each network address. The same table lists one peers row per peer, with its path type and health.
From either device, test the other's network address:
ping <peer network address>
A reply confirms basic network reachability. Test the actual service on its application port as well; its host firewall and access permissions still apply. Use Overview to check the selected network and both devices.
Next steps
- Manage device state and addresses: Devices
- Plan additional networks: Properties
- Inspect paths and link quality: Links
- Understand Global Dedicated Transmission charges: Pricing
Quick troubleshooting
| Symptom | Check and action |
|---|---|
| The install command fails immediately | Confirm administrator rights and curl, then copy the full command again from Configuration → Devices |
status is awaiting approval |
Approve the device in the console; this is the expected post-registration state |
status is not connected |
Follow the status table's action guidance and error code |
| The devices cannot reach each other | Confirm both are approved, use the network address, and check that the overlay CIDR does not overlap either LAN |
For the full decision tree, see Troubleshooting.