Network Devices

Native and browser, for routers, switches, and firewalls. See the Network Devices reference, command filtering, and How users connect.

NETCONF

NETCONF authenticates with a key or password (default port 830).

netconf.json

{
  "transaction_id": "txn-netconf-012",
  "protocol": "netconf",
  "username": "dana@corp",
  "target_host": "router1.corp.local",
  "target_port": 830,
  "target_username": "netadmin",
  "private_key": "-----BEGIN OPENSSH PRIVATE KEY-----\n...\n-----END OPENSSH PRIVATE KEY-----",
  "record_session": true,
  "expires_at": 1750000000
}

terminal

broker-bridge-api.sh checkout-create --file netconf.json

RESTCONF

RESTCONF authenticates with a target_password (default port 8443).

restconf.json

{
  "transaction_id": "txn-restconf-014",
  "protocol": "restconf",
  "username": "dana@corp",
  "target_host": "router2.corp.local",
  "target_port": 8443,
  "target_username": "netadmin",
  "target_password": "S3cr3t!",
  "record_session": true,
  "expires_at": 1750000000
}

terminal

broker-bridge-api.sh checkout-create --file restconf.json

Both offer native access (the device’s own tooling at the Bridge port) and a browser session.

Last updated on July 6, 2026

Kubernetes Exec HTTP Proxy