| Command | Syntax Example | What It Crafts | | :--- | :--- | :--- | | subnet create | craft subnet create --cidr 192.168.10.0/28 --name "IoT-zone" | Creates a new /28 subnet with 14 usable addresses. | | subnet split | subnet split 172.16.0.0/24 into 2 /25 | Divides a /24 into two /25 subnets, reconfiguring gateways automatically. | | subnet merge | subnet merge 10.1.0.0/25 + 10.1.0.128/25 | Merges two adjacent /25s back into a /24. | | route craft | route craft --src subnet A --dst subnet B --via 10.0.0.1 | Creates a custom static route with QoS markings. | | telemetry ping | telemetry ping --subnet 192.168.5.0/26 --count 1000 | Sends crafted ICMP probes from every host in the subnet. | | rollback diff | rollback diff --revision 12..13 | Shows exact changes between two crafting sessions. |
In large-scale IP and MPLS networks, subnetting creates logical divisions that improve performance and security. However, when a subnet becomes unreachable due to routing failures, misconfigured ACLs, or control plane issues, standard NMS tools often fail. The addresses this gap by providing a direct, protocol-agnostic interface to a specific subnet’s elements—often at Layer 1 or Layer 2. subnetwork craft terminal
The KIL is the SCT’s direct bridge to the operating system’s network stack. Commands issued here bypass standard socket abstractions, allowing raw access to ip table rules, nftables chains, and ebtables filters. In a typical terminal, you might type ip route add . In an SCT, you craft rule precedence with sub-millisecond precision. | Command | Syntax Example | What It
One of the most coveted skills in modern networking is . Using a Subnetwork Craft Terminal, the process looks like this: | | route craft | route craft --src
Symptom: VM in VNI 5001 cannot reach gateway. VTEPs show no errors. SCT action: Deploy an SCT in the overlay subnet (VNI 5001) and send a crafted GARP from a test MAC. Check if the underlay (IP/ UDP) delivers the encapsulated frame. If not, your multicast group or head-end replication list is broken.
Now, the terminal on your subnetwork can see and pull every item from your main storage, but the entire setup only consumes one channel on your main network (for the Interface). Pro-Tip: The Crafting Dilemma One common hurdle is that a subnetwork terminal can see , but it won't see crafting patterns