{{ result.summary.heading }}
{{ result.summary.primary }}
{{ result.summary.line }}
{{ badge.label }}
Pick the CLI syntax family before reviewing the generated commands.
Use Delete when preparing rollback or cleanup commands for the same route rows.
One route per line. Headers are optional; use ::/0 for IPv6 default routes.
{{ params.routes.length.toLocaleString() }} chars
{{ sourceStatus }}
{{ fileError }}
Leave blank to omit priority from commands that do not specify it per row.
Use main, a table number, or a table name already configured on the host.
When set, Junos output targets routing-instances <name> routing-options.
Linux routes often need elevated privileges; Cisco and Junos output is unchanged.
{{ params.linuxSudo ? 'On' : 'Off' }}
Enable when you want a full paste block instead of route lines only.
{{ params.ciscoWrapper ? 'On' : 'Off' }} 
{{ result.commandText }}
{{ header }} Copy
{{ cell }}
No rows for the current input.
Enter valid route rows to draw the route priority map.
Tags: Networking
Export to PDF Fullscreen
Customize
Advanced
:

Static routes are manual forwarding entries. They tell a host, router, or firewall where to send traffic for a destination prefix when dynamic routing does not provide the needed path. A useful static route row needs the destination, a next hop or egress interface, and sometimes a priority value so the route behaves correctly beside primary, backup, and default paths.

The same routing intent is written differently across Linux, Cisco IOS, and Junos. Linux uses ip route commands with metrics and optional routing tables. Cisco IOS uses ip route or ipv6 route lines where the trailing number acts as administrative distance. Junos uses set and delete statements under static route configuration, with preference values and qualified next hops when several next hops share one destination.

Static route rows flowing into platform command syntax, review checks, and a priority map.

Command generation is most useful when a change starts in a ticket, spreadsheet, or router review note. A row such as 10.55.0.0/16,10.44.20.254,,100,,Primary WAN can become a Linux metric command, a Cisco route line with distance, or a Junos static route statement. The row still needs operator review because syntax readiness is not the same as reachability, ownership, maintenance-window approval, or persistence on the target device.

Default routes and duplicate destinations deserve special care. A default route can redirect all unmatched traffic, and repeated destinations often mean equal-cost paths, floating backup routes, or a mistake. Good handoff text keeps the generated commands beside the normalized route ledger and the paste safety review so the person making the change can see both the command and the reason it was produced.

Technical Details:

Static route syntax starts from CIDR notation. IPv4 prefixes use an address and prefix length such as 10.55.0.0/16, while IPv6 prefixes use the same slash-length idea across 128-bit addresses. A host destination without a slash is interpreted as one address: /32 for IPv4 and /128 for IPv6. A default route is the broadest destination, written as 0.0.0.0/0 for IPv4 or ::/0 for IPv6.

Static route priority means different things on different platforms. Linux emits a route metric when a priority is supplied. Cisco IOS emits the number as administrative distance. Junos emits a preference value, and can use qualified next hops when repeated destinations need different next-hop preferences. In all three contexts, lower values are generally preferred when the platform is choosing between otherwise comparable routes.

Rule Core:

Each accepted row is normalized into a platform-specific command plan. The destination and next-hop family must match, add and replace operations need a next hop or interface, and delete operations can produce removal text from the listed destination rows.

Route intent Linux iproute2 Cisco IOS Junos
Add a route ip route add or ip -6 route add, with via, dev, proto static, and optional metric. ip route or ipv6 route, with destination, mask when IPv4, next hop or interface, optional distance, and optional IPv4 route name. set routing-options static route or the selected routing-instance path, with next-hop, preference, or special route type.
Replace a route ip route replace or ip -6 route replace. The same route line is emitted because IOS static route replacement is normally handled by applying the intended line after removing conflicts when needed. A delete line is emitted once per destination before the new set lines.
Delete a route ip route del or ip -6 route del. no ip route or no ipv6 route. delete routing-options static route or the selected routing-instance path.
Drop-style next hop blackhole, unreachable, or prohibit. Null0; entered drop is normalized to Null0. discard, reject, or receive.

The row parser accepts headers, header aliases, comments that begin with #, and positional CSV cells. The canonical column order is destination,next-hop,interface,priority,name,note. Blank priorities can inherit the optional default priority for emitted commands, while the chart uses platform defaults when no explicit value is present.

Input or check Accepted behavior Review cue
Destination CIDR, default, IPv4 host, or IPv6 host. IPv4 host bits are normalized to the network boundary. Warnings show host-to-prefix conversion and network normalization.
Default route default becomes IPv4 unless an IPv6 next hop makes the family clear. Use ::/0 when the row is meant to be an IPv6 default route.
Next hop and interface Add and replace need a next hop or interface. The next-hop address family must match the destination family. A mixed IPv4 and IPv6 row is blocked before command export.
Priority Whole number from 0 through 4294967295. Out-of-range priorities block export because they would change route ordering or platform acceptance.
Names and table labels Route names, Linux table names, and Junos routing-instance names accept letters, numbers, underscore, period, colon, and hyphen. Unsupported characters are rejected to keep command text paste-safe.
Row volume and text files Up to 250 route rows and selected text, route, or CSV files under 256 KiB. Large route sets should be split into smaller reviewable paste blocks.

The paste safety review is deliberately operational. It checks whether the command target is ready, whether IPv4 and IPv6 rows are mixed, whether priority values should be reviewed, whether destinations repeat, whether default routes are present, and whether delete mode is being used as a rollback plan. Platform-specific review rows also appear for Linux policy-routing tables and Cisco route names.

Result surface What it returns How to use it
Route Commands The generated command block for the selected platform and operation. Copy only after the alert area and review table are clear for the planned change.
Route Ledger One row per parsed route with normalized destination, family, next hop, interface, priority label, name, and generated command. Use it to compare every source row against the command that will be pasted.
Paste Safety Review Checks, statuses, evidence, and recommendations for the current route block. Treat Blocked as a stop, and treat Review as an operator decision before paste.
Route Priority Map A bar chart of route priority values, with explicit and default-derived values separated by color. Use it to spot primary and backup ordering across repeated or related destinations.
JSON Structured platform, operation, validity, errors, warnings, commands, route rows, and review rows. Use it when the route handoff needs a machine-readable archive.

Everyday Use & Decision Guide:

Start by choosing Platform and Operation. Use Linux iproute2 for hosts, appliances, and Linux routers that accept ip route syntax. Use Cisco IOS for ordinary IOS-style static route lines. Use Junos when the change belongs under routing-options static route or a named routing instance.

Paste one route per line in Route rows. A header is optional, so a small handoff can be as simple as destination, next hop, blank interface, priority, blank name, and note. Use the Browse control for a text or CSV source, then use Normalize after the rows validate if you want the textarea rewritten to canonical columns.

  • Set Default priority only when blank rows should emit the same metric, administrative distance, or preference.
  • Set Linux routing table only when the target host already has that policy-routing table defined.
  • Set Junos routing instance when the route belongs under a routing instance instead of global routing options.
  • Turn on Prepend sudo for Linux only when the paste target is a non-root shell that should run privileged commands directly.
  • Turn on Cisco config wrapper when the output should include configure terminal and end.
  • Switch Operation to Delete routes to prepare rollback text from the same normalized rows.

The main stop cue is the warning panel labeled Fix before pasting. A missing destination, malformed CIDR, priority outside the accepted range, unsupported table label, or address-family mismatch blocks command export. Fix those rows before reading the command block as usable text.

A clean command block still needs review. The Paste Safety Review table is the best place to catch default routes, duplicate destinations, mixed address families, Cisco route-name behavior, Linux table assumptions, and whether delete mode really represents the intended rollback. Do not read Static routes ready as proof that the target device will accept, persist, or prefer the route.

For a change ticket, include the Route Commands text plus the Route Ledger and any Paste Safety Review rows with Review status. That gives the reviewer command text, normalized route evidence, and the operator checks in one handoff.

Step-by-Step Guide:

Build the route block from the intended target platform, then use the review surfaces before copying the final commands.

  1. Choose Platform. The summary badge should show Linux iproute2, Cisco IOS, or Junos.
  2. Choose Operation. The summary badge should show Add routes, Replace routes, or Delete routes, and delete mode should also appear in Paste Safety Review as rollback-ready evidence.
  3. Paste rows into Route rows or load a text or CSV source with Browse. If the status line says to review the route row issue, open the warning panel and fix the specific line.
  4. Open Advanced for platform-specific options. Check that Default priority, Linux routing table, Junos routing instance, Prepend sudo for Linux, and Cisco config wrapper match the paste target.
  5. Use Normalize only after the rows are valid. The source status should report route rows and generated command lines after normalization.
  6. Read Route Commands beside Route Ledger. Each ledger row should have the intended destination, family, next hop, priority label, and generated command.
  7. Open Paste Safety Review. Clear Blocked rows, decide every Review row, and compare duplicate destinations or default routes against the planned routing change.
  8. Open Route Priority Map when route ordering matters. Lower values should line up with the intended primary path before the command block is copied.

Interpreting Results:

Static routes ready means valid rows produced command text for the selected platform. It does not mean the route is authorized, reachable, persistent, or already present on the target. Blocked means command export is stopped until the listed row issue is fixed.

Route Ledger is the row-by-row audit. Trust the normalized destination shown there, not only the pasted text. A warning that 10.55.7.9/16 was normalized to 10.55.0.0/16 means the command will use the network boundary, and the change owner should confirm that boundary before paste.

Paste Safety Review is the operational judgment check. Default routes with Review should slow the handoff because a default route changes traffic for every unmatched destination. Duplicate destinations with Review can be intentional for equal-cost or backup paths, but the next-hop order and priority values must match the route plan.

Route Priority Map compares priority numbers, not live forwarding state. Lower bars usually mean more preferred routes for the selected platform, but actual installation still depends on the target routing table, interface state, and platform rules. Verify the generated command in a staging or device-specific review path before production paste.

Worked Examples:

Linux primary and backup routes:

The rows 10.55.0.0/16,10.44.20.254,,100,,Primary WAN and 10.55.0.0/16,10.44.20.253,,250,,Backup WAN with Platform set to Linux iproute2 and Operation set to Add routes produce commands such as ip route add 10.55.0.0/16 via 10.44.20.254 proto static metric 100. Route Ledger should show the repeated destination twice, and Route Priority Map should make the lower primary metric easy to compare against the backup metric.

Cisco default route with a route name:

A row such as 0.0.0.0/0,10.44.20.1,,200,WAN_DEFAULT,Default route with Platform set to Cisco IOS produces an IPv4 route line using mask 0.0.0.0, next hop 10.44.20.1, distance 200, and name WAN_DEFAULT. If Cisco config wrapper is on, Route Commands includes configure terminal before the route and end after it. Paste Safety Review should mark default routes for review and report Cisco route names as ready for IPv4 add or replace output.

Junos replacement with different next-hop preferences:

With Platform set to Junos, Operation set to Replace routes, and Junos routing instance set to customer-a, two rows for 10.0.0.0/24 can produce a delete line followed by new static route statements under routing-instances customer-a routing-options static route. If the first next hop has priority 5 and the second has priority 20, the second repeated destination can become a qualified-next-hop line with its own preference. Duplicate destinations should stay in Review until the next-hop plan is confirmed.

Troubleshooting an invalid handoff:

A host destination such as 10.44.20.17 is treated as 10.44.20.17/32 and produces a warning, not a block. A row such as 2001:db8::/64,10.44.20.1,,100,,mixed family is blocked because an IPv4 next hop does not match an IPv6 destination. In that case the summary changes to Blocked, Route Commands shows a fix message, and the warning panel names the line that must be corrected.

FAQ:

Which row format should I paste?

Use one route per line. The canonical CSV order is destination,next-hop,interface,priority,name,note, and the header row is optional. Header aliases such as gateway, metric, distance, preference, iface, and description are also recognized.

Why did default become an IPv4 route?

default is interpreted as IPv4 unless the next hop is clearly IPv6. Use ::/0 when the row is meant to generate an IPv6 default route.

What does priority mean here?

Priority is emitted as Linux metric, Cisco administrative distance, or Junos preference. Lower values are generally preferred, but the final route choice still belongs to the target platform and its current routing table.

Can this push commands to my router?

No. It reads pasted rows or selected text files in the browser and generates text for review. It does not open device sessions, log in to routers, or apply configuration changes.

Why is command export blocked?

The warning panel names the blocking issue. Common causes include a missing destination, malformed CIDR, priority outside 0 through 4294967295, unsupported characters in a table or instance name, or an IPv4 next hop paired with an IPv6 destination.

Does a ready command block prove the route will persist?

No. Linux ip route changes are runtime routes unless the host networking stack persists them separately. Cisco and Junos commands also need normal platform review, commit or save behavior, and change-control checks.

Glossary:

Static route
A manually configured route that sends traffic for a destination prefix to a chosen next hop or interface.
CIDR
Classless Inter-domain Routing notation, such as 10.55.0.0/16, where the slash value gives the prefix length.
Default route
The broadest route, 0.0.0.0/0 for IPv4 or ::/0 for IPv6, used when no more-specific route matches.
Next hop
The gateway address, interface, or special drop target that receives traffic for the destination route.
Metric
The Linux priority-like value emitted with metric when a route row supplies a priority.
Administrative distance
The Cisco route source preference value emitted after a static route when a priority is supplied.
Preference
The Junos static route selection value emitted from the priority column or default priority setting.
Qualified next hop
A Junos next-hop form that allows a repeated destination to carry a next-hop-specific preference.

References: