← Back to catalogue
Published

router

vr.tr.router · thing-q5318

Enable an AI agent to recognise a physical network router, assess its forwarding and security state, and determine which configuration or maintenance actions are appropriate.

Thing Registry Physical world and living systems PHY.OBJ

Bundle → Layer → Finding → Questions Filled

6 bundles · 11 layers · 20 findings · 31 questions

Router identity and boundaries Establish the intended sense and separate routing capability from adjacent integrated functions.

Registered sense

Resolve the meaning of router and the level at which the kind is represented.

Physical network router sense

Record evidence for the provisional network-device interpretation and any existing canonical model that already owns it.

  1. Does the registry source identify an IP packet-routing device, a woodworking tool or another sense? definition
  2. Does an existing world model already cover this precise sense and therefore require a link rather than another publication? boundary

Routing role and integration

Distinguish the routing role from functions packaged in the same enclosure.

Routing capability versus appliance label

Describe what establishes routing capability and which integrated functions need neighbouring models.

  1. What evidence shows that the device can select next hops and forward packets between IP networks? definition
  2. Which switching, wireless, modem, NAT or firewall functions are integrated, and which remain active when routing is disabled? boundary
Interfaces and network attachment Represent how packets enter and leave through physical links and logical network attachments.

Physical link capabilities

Capture media, port capabilities and observed link operation.

Port and media compatibility

Associate each interface type with connection requirements and operating evidence.

  1. Which connectors, media, transceivers and link standards are supported, and which issuing bodies and specification versions establish compatibility? provenance
  2. What link rate, duplex mode where applicable, error counts and flap history are observed on each active connection? measurement

Logical attachment and MTU

Connect interfaces to addresses, segmentation and encapsulated paths.

Addressing and packet-size boundaries

Record logical attachments and the constraints they impose on reachability.

  1. How are addresses, prefixes, VLAN subinterfaces and tunnel endpoints assigned to physical interfaces and routing contexts? boundary
  2. What interface and effective tunnel MTUs apply in bytes, and what evidence establishes behaviour for oversized packets? measurement
Route selection and forwarding Connect route knowledge to actual packet handling and failure response.

Route origins and selection

Explain how candidate routes arise and become selected paths.

Route authority and preference

Identify route sources, selection policy and the evidence supporting preferred paths.

  1. Which routes originate from connected networks, static configuration or named routing peers, and what establishes their intended authority? provenance
  2. How do prefix matching, route preference, protocol metrics and policy-based routing interact for the traffic being assessed? definition

Forwarding evidence and convergence

Assess installed forwarding state, next-hop resolution and response to path changes.

Installed path and failure response

Tie route decisions to observed packet delivery and bounded disruption.

  1. Do forwarding entries, next-hop neighbour resolution, counters and packet observations agree with the selected route? measurement
  2. How can an authorised path-withdrawal or failover test measure convergence time and packet loss while preserving recovery access? action
Traffic boundaries and router control Represent permitted packet flows and control over the router itself.

Forwarded traffic policy

Locate routing isolation, filtering and translation within packet processing.

Isolation, filtering and translation

Record supported policy mechanisms without assuming all routers provide stateful firewalling or NAT.

  1. Which routing contexts, route leaks and ingress or egress policies determine the permitted source-to-destination paths? boundary
  2. Where supported, how do filtering and address translation interact with route lookup, return paths and existing flow state? definition

Management and control plane

Describe access to configuration and protection of locally processed control traffic.

Administrative and routing-control access

Identify who may administer the router and which networks or peers can reach its control services.

  1. Which management services and routing adjacencies are reachable from each network, and what authentication and traffic restrictions apply? boundary
  2. What authorisation, configuration comparison and alternate access are required before changing management or control-plane policy? action
Capacity, serviceability and recovery Assess sustainable routing performance and the ability to maintain or restore service.

Workload and resource limits

Relate traffic and enabled features to forwarding, table and environmental constraints.

Effective routing capacity

Record capacity evidence under explicit feature and workload conditions.

  1. What throughput in bit/s and packets/s, latency and loss are supported by measurements with the intended packet sizes and enabled features? measurement
  2. Which route, neighbour, queue or optional connection-state limits apply, and what observations reveal exhaustion, CPU overload or thermal throttling? measurement

Installation and service recovery

Connect physical operating requirements and software changes to safe restoration of routing service.

Physical operating requirements

Identify the requirements specific to installing and servicing the applicable router class.

  1. What dimensions, mounting clearances, input power and temperature limits apply, with units and manufacturer evidence? measurement
  2. Which electrical, EMC and, if applicable, radio requirements and certification marks apply in the installation jurisdiction, and what maintenance or interlocks are documented? provenance

Software change and restoration

Establish whether configuration or firmware changes can be completed and recovered without losing essential access.

  1. What evidence establishes firmware support status, update authenticity and compatibility with the installed hardware and configuration? provenance
  2. What backup, console or out-of-band access, rollback method and post-change routing checks are required before an authorised update or reset? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.

Reported evidence

Findings from the breadth pass, kept separate from the structural claims.

Check these first

Recalled without web access and unsourced; every item is a lead to verify.

  1. Which of these check these first hold for the sense of router this model covers, and on what evidence? provenance

Kinds and varieties

Recalled without web access and unsourced; every item is a lead to verify.

  1. Which of these kinds and varieties hold for the sense of router this model covers, and on what evidence? provenance

Identifiers and schemes

Recalled without web access and unsourced; every item is a lead to verify.

  1. Which of these identifiers and schemes hold for the sense of router this model covers, and on what evidence? provenance

Standards and regulation

Recalled without web access and unsourced; every item is a lead to verify.

  1. Which of these standards and regulation hold for the sense of router this model covers, and on what evidence? provenance

Real-world use

Recalled without web access and unsourced; every item is a lead to verify.

  1. Which of these real-world use hold for the sense of router this model covers, and on what evidence? provenance

Typical measurements

Recalled without web access and unsourced; every item is a lead to verify.

  1. Which of these typical measurements hold for the sense of router this model covers, and on what evidence? provenance

Failure modes and hazards

Recalled without web access and unsourced; every item is a lead to verify.

  1. Which of these failure modes and hazards hold for the sense of router this model covers, and on what evidence? provenance

Regional variation

Recalled without web access and unsourced; every item is a lead to verify.

  1. Which of these regional variation hold for the sense of router this model covers, and on what evidence? provenance

Neighbouring kinds and how to tell them apart

Recalled without web access and unsourced; every item is a lead to verify.

  1. Which of these neighbouring kinds and how to tell them apart hold for the sense of router this model covers, and on what evidence? provenance

Classifiers Filled

Family
Thing Registry
Category
Physical world and living systems
Entry kind
thing
Plane
PHY
Domain
PHY.OBJ
Other names and narrower kinds
MikroTik RouterBOARD, wireless router, TP-Link Archer VR1600v, TP-LINK Archer AX50, Netgear WNR3500L v1, Netgear WNR3500L v2, IAD WLAN 4421, tp-link AX3000 Dual Band Gigabit Wi-Fi 6 Router, Netgear WNR3500L, Broadcom's based router, Banana Pi BPI-R1, Google Wifi

What it is Filled

A router, in the computer-networking sense used here, is a device that forwards packets between IP networks by selecting an outgoing interface or next hop using destination addresses and routing information.

In scope

  • Packet forwarding between IP networks and selection of next hops
  • Physical and logical interfaces, addressing and network attachment
  • Route acquisition, selection, installation and withdrawal
  • Management access, traffic policy and separation of routing contexts
  • Capacity, power, software lifecycle and recovery of router operation

Out of scope

  • Woodworking routers and their cutting operations
  • Standalone virtual routing software and application request routers
  • Network-wide topology, addressing governance and service architecture
  • Switching, wireless access, modem and firewall functions except where their integration affects routing
  • Vendor product catalogues, individual device inventories and service contracts as independent models

Why it exists Filled

Enable an AI agent to recognise a physical network router, assess its forwarding and security state, and determine which configuration or maintenance actions are appropriate.

Distinguishing features Filled

  • Determine whether the device selects next hops between IP networks, rather than only bridging frames within a link-layer network.
  • Check for routing and forwarding tables; a default route can support routing without a dynamic routing protocol.
  • Do not identify a router solely by Wi-Fi, Ethernet sockets, NAT or a WAN label; establish its actual routing capability and operating mode.
  • Treat a multilayer switch performing IP routing as overlapping this functional kind, with its switching role represented separately.
  • Confirm that the registered sense concerns packet forwarding rather than a rotating cutting tool.

What robots and AI may and may not do Filled

Must not

  • Access or reconfigure a router on a network it does not administer.
  • Redirect, intercept or inspect traffic passing through a router without lawful authority.
  • Disable logging, filtering or security updates to hide activity.
  • Announce routes that hijack or blackhole other networks' address space.

Only with a human decision

  • Changes to core routing or border routes that can cut off many users.
  • Restarting or replacing a router that carries emergency or critical services.

May

  • Read routing tables, interface state and logs on routers it is authorized to manage.
  • Apply approved configuration changes and keep a record of each one.
  • Report faults, unusual traffic and outdated firmware to the network operator.

Moral aspects Filled

  • Routers decide whether people can reach services, including emergency ones.
  • Control of a router allows surveillance of everyone behind it.

Who is affected

  • Network users
  • Network operators
  • Services reached through the network

Owners Filled

Steward

The network operator or the household that owns the device.

Master systems

  • Regional internet registry routing records

Links to other meta-models Filled

parent

  • Q1546066 - registry parent class

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Vercy registry: vr.tr.router
  • Wikidata: Q5318 (https://www.wikidata.org/wiki/Q5318)

Direct properties required Filled

  • Routing role and deployment context: Access gateway, branch, edge, core, industrial, other or unresolved; roles may overlap
  • Supported network-layer families: IPv4, IPv6, both or other explicitly identified support
  • Interface inventory and roles: Physical ports and logical interfaces linked to media, network attachments and assigned roles
  • Interface link rate: bit/s per interface, distinguishing supported, configured and negotiated rates
  • Forwarding performance: bit/s and packets/s, with packet size, enabled features, traffic mix and test conditions
  • Route acquisition methods: Connected, static and explicitly named dynamic routing protocols; supported and enabled recorded separately
  • Routing and forwarding agreement: Consistent, pending convergence, discrepant or unknown
  • Path MTU constraints: Bytes, with interface, tunnel and protocol context
  • Routing context isolation: Interfaces and routes assigned to routing instances, with explicit route-leak relationships
  • Management exposure: Enabled management services, reachable source networks and authentication controls
  • Power requirements: Input voltage in V, maximum or measured draw in W, and supply or PoE requirements where applicable
  • Software and recovery readiness: Installed release, support status, configuration backup status and verified recovery method

Recognition required Filled

  • Separate network interfaces labelled WAN and LAN suggest a router, although these labels are not universal.
  • A chassis identification label describing the equipment as a router provides stronger evidence than antennas or enclosure shape.
  • Ethernet sockets and link indicators also occur on switches and access points, so appearance alone cannot confirm routing capability.

Capabilities and actions required Filled

  • Trace an intended destination through route selection, forwarding installation and egress reachability.
  • Compare configured, negotiated and observed interface behaviour to localise connectivity faults.
  • Assess whether traffic load and enabled services fit measured forwarding and state-table limits.
  • Evaluate and, when authorised, change routes, interfaces or traffic policies with reachability checks and rollback.
  • Inspect management exposure and routing-context boundaries for unintended access or route leakage.
  • Plan firmware updates, failover tests or hardware replacement around service dependencies and recovery access.

Hazards and failure modes required Filled

  • A misconfigured route can cut off whole networks or send traffic to the wrong place.
  • Default passwords and unpatched firmware let attackers take control of the device.

Standards and interfaces required Filled

  • RFC 1812, issued by the Internet Engineering Task Force, specifies requirements for routers that forward IPv4 packets.
  • RFC 8200, issued by the Internet Engineering Task Force, specifies the IPv6 protocol used by routers that forward IPv6 packets.

Context of use required Filled

  • Routers connect separate IP networks in homes, workplaces, data centres and telecommunications infrastructure.
  • They direct traffic towards its destination and may also provide access controls, address translation and network monitoring.

Sources Filled

  1. Wikidata item Q5318: router - identity and sense of the item
  2. Wikipedia: Router (computing) - general description of the item

Open questions

  • Does vr.tr.router denote a network router or a woodworking router, and which original registry source resolves that ambiguity?
  • Does an existing world-model publication already own the confirmed concept, requiring this registry entry to link to it?
  • How should the canonical model relate physical routers, virtual routers and multilayer switches without duplicating shared routing semantics?
  • Which deployment classes need distinct capacity, resilience and maintenance questions, and which authoritative sources establish their meaningful ranges?
  • Which protocol specifications, installation standards and jurisdiction-dependent certifications should be researched for the confirmed scope?

Machine files

Provenance

thing registry research (pass 2) · unreviewed

Built from: models/things/publications/thing-q5318/spec.json