HYPERVISOR_MODE(7)

📦
version 0.2.24 · 2 versions
, in alpine 3.24, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu stonking

🦋 hypervisor_mode(7) — Miscellaneous Information Manual 🦋

🌈 NAME 🌈

okay so bestie, hypervisor_mode is the iconique thing that allows you to run simultaneously many virtual router instances, and to simulate ATM, Ethernet or Frame‐Relay networks. periodt. 💅

✨ SYNOPSIS ✨

dynamips -H [ip_address:]tcp_port

💅 DESCRIPTION 💅

You can connect directly to the TCP control port with telnet, or use dynagen/dynagui that will pass commands transparently. The second method is highly recommended. no cap, it’s just easier.

The command syntax is simple: <module> <function> [arguments...] For example: "vm start R1" starts virtual instance named "R1".

Available since version 0.2.5.

The modules that are currently defined are given below:

  • hypervisor — General hypervisor management
  • vm — General virtual machine (VM) management
  • vm_debug — General virtual machine (VM) debugging
  • c7200 — Virtual instances of Cisco 7200
  • c3745 — Virtual instances of Cisco 3745
  • c3725 — Virtual instances of Cisco 3725
  • c3600 — Virtual instances of Cisco 3600
  • c2691 — Virtual instances of Cisco 2691
  • c2600 — Virtual instances of Cisco 2600
  • c1700 — Virtual instances of Cisco 1700
  • nio — Network Input/Output (NIO) descriptors
  • nio_bridge — NIO bridges (shared media)
  • atmsw — ATM switches
  • atm_bridge — ATM bridges
  • frsw — Frame‐Relay switches
  • ethsw — Ethernet switches
  • object_store — Object store

🫶 Hypervisor management module (hypervisor) 🫶

  • hypervisor version — Display the version of dynamips.
  • hypervisor module_list — Display the module list.
  • hypervisor cmd_list <module> — Display commands recognized by the specified module.
  • hypervisor close — Close the current session.
  • hypervisor stop — Destroy all objects and stop hypervisor.
  • hypervisor reset — Destroy all objects. (used to get an empty configuration)
  • hypervisor working_dir <directory> — Set the directory to use to store files.
  • hypervisor save_config <filename> — Save the configuration of all objects into the specified file.
  • hypervisor parser_test [<a1> [... <a10>]] — Display up to 10 arguments. (since version 0.2.6-RC1)
  • hypervisor tsg_stats — Dump statistics about JIT code sharing to the console. (since version 0.2.8-RC3, unstable)

👑 Virtual Machine module (vm) 👑

  • vm list — List all VM instances. (c7200, c3745, c3725, c3600, c2691, c2600, c1700)
  • vm list_con_ports — List all VM console TCP port. (since version 0.2.6-RC5)
  • vm create <instance_name> <instance_id> <platform> — Create a new router instance. The ID must be unique and is used to name files on disk. (since version 0.2.8-RC1)
  • vm rename <instance_name> <new_name> — Rename a router instance. (since version 0.2.11)
  • vm delete <instance_name> — Delete the specified instance. (since version 0.2.8-RC1)
  • vm start <instance_name> — Start the instance. At least the IOS image must be set. (since version 0.2.8-RC1)
  • vm stop <instance_name> — Stop the instance. The settings are kept. (since version 0.2.8-RC1)
  • vm get_status <instance_name> — Get the status of a VM instance. Return values: 0=inactive, 1=shutting down, 2=running, 3=suspended. (since version 0.2.11)
  • vm set_tsg <instance_name> <group_id> — Set translation sharing group. (since version 0.2.8-RC3-community, unstable)
  • vm set_debug_level <instance_name> <level> — Set the debug level (which is a number) for a VM. By default, no specific debug is enabled (level = 0).
  • vm set_ios <instance_name> <ios_file> — Set the IOS image file to use. There is no default.
  • vm set_config <instance_name> <startup_file> [<private_file>] — Set the config files that are pushed to startup-config and private-config in NVRAM when the instance is started. To keep existing data, use an empty string ('') for the filename. The optional <private_file> is an empty string by default. (supports <private_file> since version 0.2.10)
  • vm extract_config <instance_name> — Get the contents of the config files startup-config and private-config from NVRAM. The data of each file is encoded in a Base64 string, surrounded by single quotes. (returns private-config since version 0.2.10)
  • vm push_config <instance_name> <startup_cfg> [<private_cfg>] — Push configuration to the config files startup-config and private-config in NVRAM. The data is a Base64 encoded string, or '(keep)' to keep existing data. The optional <private_cfg> is '(keep)' by default. (supports <private_cfg> since version 0.2.11)
  • vm set_ram <instance_name> <ram_size> — Set the RAM size, specified in Mbytes.
  • vm set_nvram <instance_name> <nvram_size> — Set the NVRAM size, specified in Kbytes.
  • vm set_ram_mmap <instance_name> <0|1> — Enable/Disable use of a mapped file to simulate router memory. By default, a mapped file is used. This is a bit slower, but requires less memory.
  • vm set_sparse_mem <instance_name> <0|1> — Enable/disable use of sparse memory. (since version 0.2.7-RC1)
  • vm suspend <instance_name> — Suspend execution of the instance.
  • vm resume <instance_name> — Resume execution of the instance.
  • vm set_clock_divisor <instance_name> <clock_div> — Set the clock divisor value. The higher is the value, the faster is the clock in the virtual machine. The default is 4, but it is often required to adjust it.
  • vm set_blk_direct_jump <instance_name> <0|1> — Enable/disable use of block direct jump. (compatibility option, since version 0.2.7-RC2)
  • vm set_idle_pc <instance_name> <pc_value> — Set the idle Pointer Counter (PC). You must determine it through the method explained in the main README file.
  • vm set_idle_pc_online <instace_name> <cpu_id> <pc_value> — Set the idle PC value when the CPU is online. (since version 0.2.6-RC2)
  • vm get_idle_pc_prop <instance_name> <cpu_id> — Get the idle PC proposals. Takes 1000 measurements and records up to 10 idle PC proposals. There is a 10ms wait between each measurement. (since version 0.2.6-RC2)
  • vm show_idle_pc_prop <instance_name> <cpu_id> — Dump the idle PC proposals. (since version 0.2.6-RC2)
  • vm set_idle_max <instance_name> <cpu_id> <idle_max> — Set CPU idle max value. (since version 0.2.6-RC2)
  • vm set_idle_sleep_time <instance_name> <cpu_id> <idle_sleep_time> — Set CPU idle sleep time value. (since version 0.2.6-RC2)
  • vm show_timer_drift <instance_name> <cpu_id> — Show info about potential timer drift. (since version 0.2.6-RC3)
  • vm set_ghost_file <instance_name> <ghost_ram_filename> — Set ghost RAM file. (since version 0.2.6-RC3, needs an extra bogus argument before version 0.2.6-RC4)
  • vm set_ghost_status <instance_name> <ghost_status>" — Set ghost RAM status. (since version 0.2.6-RC3, needs an extra bogus argument before version 0.2.6-RC4)
  • vm set_exec_area <instance_name> <area_size> — Set the exec area size. The exec area is a pool of host memory used to store pages translated by the JIT (they contain the native code corresponding to MIPS code pages).
  • vm set_disk0 <instance_name> <value> — Set size of PCMCIA ATA disk0.
  • vm set_disk1 <instance_name> <value> — Set size of PCMCIA ATA disk1.
  • vm set_conf_reg <instance_name> <value> — Set the config register value. The default is 0x2102.
  • vm set_con_tcp_port <instance_name> <tcp_port> — Set the TCP port to use for console. By default, no TCP port is chosen, meaning that you cannot get access to the console.
  • vm set_aux_tcp_port <instance_name> <tcp_port> — Set the TCP port to use for AUX port. By default, no TCP port is chosen, meaning that you cannot get access to the AUX port.
  • vm cpu_info <instance_name> <cpu_id> — Show info about the CPU identified by "cpu_id". The boot CPU (which is typically the only CPU) has ID 0.
  • vm cpu_usage <instance_name> <cpu_id> — Show cpu usage of dynamips in seconds. (experimental) The instance must exist, "cpu_id" is ignored. (since version 0.2.8-RC5-community)
  • vm send_con_msg <instance_name> <str> [<format>] — (since version 0.2.6-RC3) Send a message on the console. It only writes the bytes that fit in the console buffer.

(since version 0.2.14) The optional argument <format> indicates the string format. On success it will report "X byte(s) written".

String formats:

  • plain - plain string (default, old behavior)
  • base64 - base64 encoded string
  • vm send_aux_msg <instance_name> <str> [<format>] — (since version 0.2.6-RC3) Send a message on the AUX port. It only writes the bytes that fit in the aux buffer.

(since version 0.2.14) The optional argument <format> indicates the string format. On success it will report "X byte(s) written".

String formats:

  • plain - plain string (default, old behavior)
  • base64 - base64 encoded string
  • vm slot_bindings <instance_name> — Show slot bindings. (since version 0.2.8-RC1)
  • vm slot_nio_bindings instance_name slot_id — shows you the NIO bindings for the slot you asked about, bestie. (since version 0.2.8-RC1)
  • vm slot_add_binding instance_name slot_id port_id dev_type — adds a slot binding. (since version 0.2.8-RC1)
  • vm slot_remove_binding instance_name slot_id port_id — takes that slot binding back out. (since version 0.2.8-RC1)
  • vm slot_add_nio_binding instance_name slot_id port_id nio_name — adds a NIO binding for a slot/port. (since version 0.2.8-RC1)
  • vm slot_remove_nio_binding instance_name slot_id port_id — removes a NIO binding for a slot/port. (since version 0.2.8-RC1)
  • vm slot_enable_nio instance_name slot_id port_id — turns NIO on for the slot/port you point at. (since version 0.2.8-RC1)
  • vm slot_disable_nio instance_name slot_id port_id — turns NIO off for the slot/port you point at. (since version 0.2.8-RC1)
  • vm slot_oir_start instance_name slot_id subslot_id — OIR to start a slot/subslot. (since version 0.2.8-RC3-community)
  • vm slot_oir_stop <isntance_name> slot_id subslot_id — OIR to stop a slot/subslot. (since version 0.2.8-RC3-community)
💀 okay so heads up: that second one literally says <isntance_name> in the original. That is not me typing too fast, that is the manpage's actual spelling. Leaving it exactly as-is because the facts are sacred and the typo is, unfortunately, canon. 🫶

🔍 Virtual Machine debugging module (vm_debug) 🔍

Available since version 0.2.6-RC1. This one is your little x-ray machine for the VM internals, iykyk.

  • vm_debug show_cpu_regs instance_name cpu_id — dumps the CPU registers straight to the console.
  • vm_debug show_cpu_mmu instance_name cpu_id — dumps the CPU MMU info to the console. (since version 0.2.7-RC1)
  • vm_debug set_cpu_reg instance_name cpu_id reg_id value — sets the value of a CPU register.
  • vm_debug add_cpu_breakpoint instance_name cpu_id address — adds a breakpoint. 🛑
  • vm_debug remove_cpu_breakpoint instance_name cpu_id address — removes a breakpoint.
  • vm_debug pmem_w32 instance_name cpu_id address value — writes a 32-bit memory word to physical memory.
  • vm_debug pmem_r32 instance_name cpu_id address — reads a 32-bit memory word from physical memory.
  • vm_debug pmem_w16 instance_name cpu_id address value — writes a 16-bit memory word to physical memory.
  • vm_debug pmem_r16 instance_name cpu_id address — reads a 16-bit memory word from physical memory.
  • vm_debug pmem_cfind instance_name cpu_id bytes [first [last]] — finds a sequence of bytes in the physical memory interval [first,last]. The byte sequence is composed of hexadecimal characters and must have a length multiple of 2 — so abc will get you clowned, it's gotta be pairs, fr fr. The interval defaults to the complete memory space. Only the memory of cacheable devices (ram, rom, disks, ...) is searched. (since version 0.2.12)

🌐 Virtual Cisco 7200 instances module (c7200) 🌐

  • c7200 list — lists literally every existing Cisco 7200 instance you've got kicking around.
  • c7200 set_npe instance_name npe_name — sets the NPE model. For example: npe-100, npe-400, ... The default is "npe-400".
  • c7200 set_midplane instance_name midplane_name — sets the midplane model, and it can be either "std" or "vxr". The default is "vxr".
  • c7200 get_mac_addr instance_name — gets the base MAC address of the router. By default, the address is automatically generated with this pattern : ca<instance_id>.<process_pid>.0000 (Cisco format). (since version 0.2.11)
  • c7200 set_mac_addr instance_name mac_addr — sets the base MAC address of the router. The MAC address patern (spelled exactly how the original spells it, no notes 💅) can be the Cisco format (e.g. ca01.1234.0000) or the standard format (e.g. ca:01:12:34:00:00).
  • c7200 set_system_id instance_name system_id — sets the system id. (since version 0.2.8-RC3-community)
  • c7200 set_temp_sensor instance_name sensor_id temperature — sets temperature for a DS1620 sensor. This can be used to simulate environmental problems like overheat. 🔥 (since version 0.2.8-RC3-community)
  • c7200 set_power_supply instance_name power_supply_id <0|1> — sets power supply status. This can be used to simulate environmental problems like power loss. 💀 (since version 0.2.8-RC3-community)
  • c7200 show_hardware instance_name — displays virtual hardware info about the instance.

🌐 Virtual Cisco 3745 instances module (c3745) 🌐

  • c3745 list — lists all existing Cisco 3745 instances.
  • c3745 set_iomem instance_name size — sets the I/O mem size.
  • c3745 get_mac_addr instance_name — gets the base MAC address of the router. By default, the address is automatically generated with this pattern : c4<instance_id>.<process_pid>.0000 (Cisco format). (since version 0.2.11)
  • c3745 set_mac_addr instance_name mac_addr — sets the base MAC address of the router. The MAC address patern can be the Cisco format (e.g. c401.1234.0000) or the standard format (e.g. c4:01:12:34:00:00).
  • c3745 set_system_id instance_name system_id — sets the system id. (since version 0.2.8-RC3-community)
  • c3745 show_hardware instance_name — displays virtual hardware info about the instance.

🌐 Virtual Cisco 3725 instances module (c3725) 🌐

  • c3725 list — lists all existing Cisco 3725 instances.
  • c3725 set_iomem instance_name size — sets the I/O mem size.
  • c3725 get_mac_addr instance_name — gets the base MAC address of the router. By default, the address is automatically generated with this pattern : c2<instance_id>.<process_pid>.0000 (Cisco format). (since version 0.2.11)
  • c3725 set_mac_addr instance_name mac_addr — sets the base MAC address of the router. The MAC address patern can be the Cisco format (e.g. c201.1234.0000) or the standard format (e.g. c2:01:12:34:00:00).
  • c3725 set_system_id instance_name system_id — sets the system id. (since version 0.2.8-RC3-community)
  • c3725 show_hardware instance_name — displays virtual hardware info about the instance.

🌐 Virtual Cisco 3600 instances module (c3600) 🌐

  • c3600 list — lists all existing Cisco 3600 instances.
  • c3600 set_chassis instance_name chassis_name — sets the chassis model. Possible values: 3620, 3640, 3660. The default is "3640".
  • c3600 set_iomem instance_name size — sets the I/O mem size.
  • c3600 get_mac_addr instance_name — gets the base MAC address of the router. By default, the address is automatically generated with this pattern : cc<instance_id>.<process_pid>.0000 (Cisco format). (since version 0.2.11)
  • c3600 set_mac_addr instance_name mac_addr — sets the base MAC address of the router. The MAC address patern can be the Cisco format (e.g. cc01.1234.0000) or the standard format (e.g. cc:01:12:34:00:00).
  • c3600 set_system_id instance_name system_id — sets the system id. (since version 0.2.8-RC3-community)
  • c3600 show_hardware instance_name — displays virtual hardware info about the instance.

🌐 Virtual Cisco 2691 instances module (c2691) 🌐

  • c2691 list — lists all existing Cisco 2691 instances.
  • c2691 set_iomem instance_name size — sets the I/O mem size.
  • c2691 get_mac_addr instance_name — gets the base MAC address of the router. By default, the address is automatically generated with this pattern : c0<instance_id>.<process_pid>.0000 (Cisco format). (since version 0.2.11)
  • c2691 set_mac_addr instance_name mac_addr — sets the base MAC address of the router. The MAC address patern can be the Cisco format (e.g. c001.1234.0000) or the standard format (e.g. c0:01:12:34:00:00).
  • c2691 set_system_id instance_name system_id — sets the system id. (since version 0.2.11) ⚠️ notice this one says 0.2.11, not the 0.2.8-RC3-community that all its little siblings say — that's not a typo on my end, that's what the page says.
  • c2691 show_hardware instance_name — displays virtual hardware info about the instance.

🌐 Virtual Cisco 2600 instances module (c2600) 🌐

Available since version 0.2.7-RC1.

  • c2600 list — lists all existing Cisco 2600 instances.
  • c2600 set_chassis instance_name chassis_name — sets the chassis model. Possible values: 2610, 2611, 2620, 2621, 2610XM, 2611XM, 2620XM, 2621XM, 2650XM, 2651XM. The default is "2610".
  • c2600 set_iomem instance_name size — sets the I/O mem size.
  • c2600 get_mac_addr instance_name — gets the base MAC address of the router. By default, the address is automatically generated with this pattern : c8<instance_id>.<process_pid>.0000 (Cisco format). (since version 0.2.11)
  • c2600 set_mac_addr instance_name mac_addr — sets the base MAC address of the router. The MAC address patern can be the Cisco format (e.g. c801.1234.0000) or the standard format (e.g. c8:01:12:34:00:00).
  • c2600 set_system_id instance_name system_id — sets the system id. (since version 0.2.8-RC3-community)
  • c2600 show_hardware instance_name — displays virtual hardware info about the instance.

🌐 Virtual Cisco 1700 instances module (c1700) 🌐

Available since version 0.2.8-RC1.

  • c1700 list — lists all existing Cisco 1700 instances.
  • c1700 set_chassis instance_name chassis_name — sets the chassis model. Possible values: 1710, 1720, 1721, 1750, 1751, 1760. The default is "1720".
  • c1700 set_iomem instance_name size — sets the I/O mem size.
  • c1700 get_mac_addr <instance_name> — grab the router's base MAC address. out of the box it's auto-generated using this pattern : d0<instance_id>.<process_pid>.0000 (Cisco format). (since version 0.2.11)
  • c1700 set_mac_addr <instance_name> <mac_addr> — set the router's base MAC. the pattern can be either Cisco format (like d001.1234.0000) or standard format (like d0:01:12:34:00:00). either one, she's flexible 💅
  • c1700 set_system_id <instance_name> <system_id> — set the system id. (since version 0.2.8-RC3-community)
  • c1700 show_hardware <instance_name> — show off the virtual hardware info for that instance ✨

🌸 Network Input/Output (NIO) module ("nio") 🌸

  • nio list — list every NIO in the building. all of them. the whole roster.
  • nio create_udp <nio_name> <local_port> <remote_host> <remote_port> — make a UDP NIO with exactly these params.
  • nio create_udp_auto <nio_name> <local_addr> <local_port_start> <local_port_end> — make an auto UDP NIO. (since version 0.2.8-RC3-community)
  • nio connect_udp_auto <nio_name> <remote_host> <remote_port> — hook a UDP Auto NIO up to a remote host/port. (since version 0.2.8-RC3-community)
  • nio create_unix <nio_name> <local_file> <remote_file> — make a UNIX NIO with exactly these params.
  • nio create_vde <nio_name> <control_file> <local_file> — make a VDE NIO with exactly these params. VDE = "Virtual Distributed Ethernet", and bestie it plays nice with the UML (User-Mode-Linux) switch. 🦋
  • nio create_tap <nio_name> <tap_device> — make a TAP NIO. TAP devices are Linux-and-FreeBSD only, and yes they need root access. root only, no cap.
  • nio create_gen_eth <nio_name> <eth_device> — make a generic ethernet NIO using PCAP (0.9.4 and greater). needs root access. only available if it was compiled with GEN_ETH.
  • nio create_linux_eth <nio_name> <eth_device> — make a Linux ethernet NIO. needs root access and Linux platforms only. only available if it was compiled with LINUX_ETH.
  • nio create_null <nio_name> — make a Null NIO.
  • nio create_fifo <nio_name> — make a Null NIO. (yes, that's literally what the page says for this one — the manpage is passing the vibe of create_null, we don't ask questions 🙈)
  • nio crossconnect_fifo <nio_name> <nio_name> — cross-connect two FIFO NIOs. it's giving matchmaker energy 🫶
  • nio rename <nio_name> <new_name> — rename a NIO. (since version 0.2.11)
  • nio delete <nio_name> — delete the NIO you named. heads up tho: you can only delete it once it's not in use by any other object anymore.
  • nio set_debug <nio_name> <debug> — toggle debugging on/off for that NIO. with debugging on, every packet received and emitted gets printed on screen. it's mainly for debugging interface drivers.
  • nio bind_filter <nio_name> <direction> <filter_name> — bind a packet filter. direction is 0 for receiving, 1 for sending, 2 for both. filter freq_drop drops packets. filter capture captures packets, and it's only available if compiled with GEN_ETH.
  • nio unbind_filter <nio_name> <direction> — take that packet filter off.
  • nio setup_filter <nio_name> <direction> [<a3> [...<a10>]] — set up a packet filter for a given NIO. the arguments get passed straight on to the setup function of the filter.
    • filter freq_drop takes 1 argument <frequency> . it'll drop everything with a -1 frequency, drop every Nth packet with a positive frequency, or drop nothing at all.
    • filter capture takes 2 arguments <link_type_name> <output_file> . it captures packets into the target output file. the link type name is a case-insensitive DLT_ name taken from the pcap library constants with the DLT_ part chopped off.
  • nio get_stats <nio_name> — get the stats for a NIO. (since version 0.2.8-RC3-community)
  • nio reset_stats <nio_name> — reset the stats for a NIO. (since version 0.2.8-RC3-community)
  • nio set_bandwidth <nio_name> <bandwidth> — set the bandwidth constraint. (since version 0.2.8-RC3-community)

🎀 NIO bridge module ("nio_bridge") 🎀

  • nio_bridge list — list all the NIO bridges.
  • nio_bridge create <bridge_name> — make a NIO bridge. a NIO bridge acts like shared media — think of it as a kind of hub.
  • nio_bridge rename <bridge_name> <new_name> — rename a NIO bridge. (since version 0.2.11)
  • nio_bridge delete <bridge_name> — delete a NIO bridge.
  • nio_bridge add_nio <bridge_name> <nio_name> — add a NIO as a new port on a NIO bridge. the NIO has to have been created through the "nio" module, periodt.
  • nio_bridge remove_nio <bridge_name> <nio_name> — remove that NIO from being a member of the NIO bridge.

💜 Virtual Ethernet switch module ("ethsw") 💜

  • ethsw list — list all the Ethernet switches.
  • ethsw create <switch_name> — create a brand new Ethernet switch.
  • ethsw rename <switch_name> <new_name> — rename an Ethernet switch. (since version 0.2.11)
  • ethsw delete <switch_name> — delete the Ethernet switch you named.
  • ethsw add_nio <switch_name> <nio_name> — add a NIO as a new port on an Ethernet switch. again, the NIO must have been created through the "nio" module.
  • ethsw remove_nio <switch_name> <nio_name> — remove that NIO from being a member of the Ethernet switch.
  • ethsw set_access_port <switch_name> <nio_name> <vlan_id> — set that port as an ACCESS port in VLAN <vlan_id>.
  • ethsw set_dot1q_port <switch_name> <nio_name> <native_vlan> — set that port as an 802.1Q trunk port, with native VLAN <native_vlan>.
  • ethsw set_qinq_port <switch_name> <nio_name> <outer_vlan> — set that port as a trunk (QinQ) port. (since version 0.2.3-RC3-community)
  • ethsw clear_mac_addr_table <switch_name> — wipe the MAC address table clean 🧹
  • ethsw show_mac_addr_table <switch_name> — show the MAC address table (output format: Ethernet address, VLAN, NIO)

🔥 Virtual ATM switch module ("atmsw") 🔥

  • atmsw list — list all the ATM switches.
  • atmsw create <switch_name> — create a new ATM switch.
  • atmsw rename <switch_name> <new_name> — rename an ATM switch. (since version 0.2.11)
  • atmsw delete <switch_name> — delete the ATM switch you named.
  • atmsw create_vpc <switch_name> <input_nio> <input_vpi> <output_nio> <output_vpi> — create a new Virtual Path connection (unidirectional).
  • atmsw delete_vpc <switch_name> <input_nio> <input_vpi> <output_nio> <output_vpi> — delete a Virtual Path connection (unidirectional).
  • atmsw create_vcc <switch_name> <input_nio> <input_vpi> <input_vci> <output_nio> <output_vpi> <output_vci> — create a new Virtual Channel connection (unidirectional).
  • atmsw delete_vcc <switch_name> <input_nio> <input_vpi> <input_vci> <output_nio> <output_vpi> <output_vci> — delete a Virtual Channel connection (unidirectional).

🌈 Virtual ATM bridge module ("atm_bridge") 🌈

Available since version 0.2.8-RC2.

  • atm_bridge list — list all the ATM bridges.
  • atm_bridge create <bridge_name> — create a new ATM bridge.
  • atm_bridge rename <bridge_name> <new_name> — rename an ATM bridge. (since version 0.2.11)
  • atm_bridge delete <bridge_name> — delete an ATM bridge.
  • atm_bridge configure <bridge_name> <eth_nio> <atm_nio> <vpi> <vci> — configure an ATM bridge.
  • atm_bridge unconfigure <bridge_name> — unconfigure an ATM bridge.

🦋 Virtual Frame-Relay switch module ("frsw") 🦋

  • frsw list — list all the Frame-Relay switches.
  • frsw create <switch_name> — create a new Frame-Relay switch.
  • frsw rename <switch_name> <new_name> — rename a Frame-Relay switch. (since version 0.2.11)
  • frsw delete <switch_name> — delete the Frame-Relay switch you named.
  • frsw create_vc <switch_name> <input_nio> <input_dlci> <output_nio> <output_dlci> — create a new Virtual Circuit connection (unidirectional).
real talk: in the source page the frsw delete description and the frsw create_vc synopsis literally crash into each other in one blob — typo behavior, iconic honestly 😭 — but both commands and both descriptions are exactly what's listed above, so you're not missing anything.
  • frsw delete_vc <switch_name> <input_nio> <input_dlci> <output_nio> <output_dlci> — delete a Virtual Circuit connection (unidirectional).

🍓 Object store module ("object_store") 🍓

Available since version 0.2.8-RC2.

  • object_store write <object_name> <data> — write an object. the data comes in base64 encoding.
  • object_store read <object_name> — read an object and hand the data back in base64 encoding.
  • object_store rename <object_name> <new_name> — rename an object. (since version 0.2.11)
  • object_store delete <object_name> — delete an object from the store.
  • object_store delete_all — delete all objects from the store
  • object_store list — the object list.

🐛 REPORTING BUGS 🐛

found something cursed? please send your bug reports to https://github.com/GNS3/dynamips/issues 💀

👑 SEE ALSO ✨

dynamips(1), nvram_export(1), dynagen(1), dynagui(1) http://www.gns3.net/dynamips/ http://forum.gns3.net/ https://github.com/GNS3/dynamips

🕰️ OLD WEBSITES 🕰️

http://www.ipflow.utc.fr/index.php/ http://www.ipflow.utc.fr/blog/ http://hacki.at/7200emu/index.php

💖 AUTHOR 💖

dynamips is being maintained by Flávio J. Saraiva <flaviojs2005@gmail.com>. This manual page was initially written by Erik Wenzel <erik@debian.org> for the Debian GNU/Linux system.

okay bestie that's the whole page 🫶 shoutout to the HYPERVISOR_MODE(7) manual, source dated Mar 27, 2014 — she's vintage, she's maintained, she ate. go configure something iconic 💅✨

📦 where this page comes from