Static Route Commands Generator

Introduction:

A static route is a deliberate forwarding entry in a host, router, or firewall routing table. It tells the device that traffic for a destination prefix should leave through a named gateway, interface, or special route target instead of being learned from a dynamic routing protocol.

Administrators use static routes for small, explicit decisions: a partner network reachable through a firewall, a lab subnet behind a test router, a temporary migration path, a backup default gateway, or a blackhole route for traffic that should be dropped. The same idea appears on Linux servers, Windows hosts, edge firewalls, campus switches, and router operating systems, but each platform names the pieces differently.

Static route command syntax is not portable. Linux uses ip route forms with optional tables and metrics. Windows can use route.exe or PowerShell NetRoute commands. Network devices use configuration syntax such as Cisco-style ip route, Junos static route statements, VyOS configuration paths, RouterOS route entries, or FortiGate router static tables.

Priority values deserve extra care because they are part syntax and part routing policy. Lower values are commonly preferred, but the label changes from metric to administrative distance to preference depending on the target. A repeated destination might be intentional equal-cost routing, a floating backup path, or an accidental duplicate.

A syntactically valid command block is still not a complete change plan. Static routes can redirect broad traffic, especially when the destination is a default route or a large prefix. The destination, next hop reachability, persistence method, and rollback text all need review before anyone pastes commands into a production device.

How to Use This Tool:

Start with the target platform and operation, then treat the generated output as review material rather than a paste-and-forget answer.

1. Choose Platform. The target controls syntax, validation, priority wording, persistence notes, and which route families are allowed.
2. Choose Operation: Add routes, Replace routes, or Delete routes. Use delete mode to prepare rollback output from the same reviewed rows.
3. Paste one route per line in Route rows. The canonical columns are destination,next-hop,interface,priority,name,note. A header row is optional, and a CSV, TXT, ROUTES, or CONF file under 256 KiB can be loaded into the textarea.
4. Use clear destination notation. CIDR prefixes, default, IPv4 hosts, and IPv6 hosts are accepted. Use ::/0 when the intended default route is IPv6, because the word default is treated as IPv4 unless an IPv6 next hop makes the family clear.
5. Open Advanced when the platform needs extra context. Default priority fills blank priority cells, Linux routing table targets a named or numbered Linux table, Junos routing instance targets non-global Junos routing options, Prepend sudo for Linux adjusts host shell output, and Network CLI config wrapper wraps supported device commands in configuration mode.
6. Stop on Fix before pasting. Missing destinations, malformed CIDR, address-family mismatches, missing next-hop or interface values for add/replace output, unsupported names, FortiGate delete rows without numeric route IDs, and priority values outside 0 through 4294967295 block command export.
7. Use Normalize after validation if you want a clean source for the ticket. The textarea is rewritten to canonical columns so add, replace, and delete outputs can be rebuilt consistently.
8. Compare Route Commands, Route Ledger, Paste Safety Review, and Route Priority Map. Copy the commands only after the ledger and safety review match the intended routing change.

Interpreting Results:

Static routes ready means the current rows produced command text for the selected platform and operation. It does not confirm next-hop reachability, authorization, device state, or persistence after reboot. Blocked means at least one row must be corrected before the command output should be used.

Read the result as a change record. The command text is the paste candidate, the ledger is the row-by-row audit, the safety review lists operational concerns, and the priority map shows how explicit and default-derived priority values compare.

The main false-confidence risk is a clean command block aimed at the wrong scope. A host address normalized to a network boundary, a broad default route, or a repeated prefix can all be syntactically valid while still causing an outage if the routing intent is wrong.

Technical Details:

Route lookup normally starts with the most specific matching prefix. A /32 IPv4 host route beats a /24 network route, and both beat 0.0.0.0/0. IPv6 follows the same prefix-length idea across 128-bit addresses. When two candidates have the same destination specificity, platform policy, metric, distance, preference, interface metric, and equal-cost routing behavior decide which path is installed or used.

Prefix notation is the common handoff format, but platforms print and configure it differently. IPv4 Cisco-style commands split a destination into network address plus dotted netmask. Linux, PowerShell, Junos, FRR, VyOS, RouterOS, and many modern CLIs accept slash notation. Windows route.exe uses a destination address with a separate mask.

Rule Core:

Command families differ most in replace semantics, route persistence, and how they express route preference. A generated delete block should be checked against the target's exact configuration because some platforms remove by full route tuple while others rely on destination, find expressions, or table IDs.

Validation focuses on command shape before any operational approval. A next-hop IP address must match the destination family. Add and replace operations need a forwarding target. Platform-specific checks block known mismatches, including IPv6 rows for Windows route.exe, unsupported special next-hop words, Junos rows that mix a separate interface with a next-hop value, and FortiGate delete rows without a numeric route ID in the name column.

Route Priority Map plots each route's effective priority. Explicit priorities use the row value. Blank priorities use platform defaults for charting, such as 1 for Cisco-like static routes, 5 for Junos, 256 for Windows route families, 10 for FortiGate, and 0 for Linux and macOS route output. The chart is a review aid, not a forwarding-table simulation.

Persistence differs by target. Linux and macOS route commands usually change runtime state unless another network manager or startup policy saves them. Windows route.exe add output includes persistent syntax. PowerShell NetRoute persistence depends on Windows policy store behavior and should be confirmed after applying. Network device commands still need the platform's normal commit, write, save, or configuration workflow where applicable.

Worked Examples:

Build Linux runtime routes for a partner network

A ticket lists 10.55.0.0/16 via 10.44.20.254 at priority 100 and 172.20.0.0/16 via 10.44.20.253 at priority 150. With Linux iproute2 and Add routes, Route Commands emits ip route add lines with proto static and metrics. Route Ledger should show two IPv4 rows, and Route Priority Map should place the lower metric on the intended primary path.

Prepare a Cisco rollback before the change window

A network operator normalizes the approved rows, changes Platform to Cisco IOS / IOS XE, and sets Operation to Delete routes. Route Commands emits no ip route or no ipv6 route lines, and Paste Safety Review marks rollback fit as ready. The add output and delete output can then travel together in the change record.

Fix a Windows IPv6 route family mismatch

A Windows route.exe target includes 2001:db8:100::/48 with an IPv6 next hop. The result is blocked because the Windows route.exe output path supports IPv4 only here. Switching Platform to Windows PowerShell NetRoute creates a command family that can represent IPv6 prefixes.

Review repeated Junos destinations

Two Junos rows use 192.0.2.0/24 with different next hops and priorities. Paste Safety Review flags the repeated destination, and the generated output can use qualified-next-hop behavior when priorities differ. The reviewer should confirm that the lower preference is the intended active path and that the higher preference is acceptable as backup behavior.

FAQ:

Glossary:

Destination prefix

The network or host route being added, such as 10.55.0.0/16 or ::/0.

Next hop

The gateway address or route type used to forward traffic toward the destination.

Interface route

A route that points traffic out a named interface instead of through a gateway address.

Default route

The catch-all route for destinations that do not match a more specific prefix.

Metric

A Linux or Windows route value used when comparing route candidates in that platform's routing table.

Administrative distance

A Cisco-style trust value where lower values are preferred among route sources.

Preference

A Junos route-selection value where lower values are preferred for static route selection.

References:

• How to add a static route with ip route, Simplified Guide.
• How to remove a static route in Linux, Simplified Guide.
• Configuring Static Routes with ip commands, Red Hat Documentation.
• route command, Microsoft Learn.
• New-NetRoute, Microsoft Learn.
• Describe Administrative Distance, Cisco.
• Static Route Preferences and Qualified Next Hops, Juniper Networks.
• STATIC, FRRouting documentation.
• Static routing, VyOS documentation.
• Routing concepts, Fortinet Document Library.