Skip to content
Yusuke Ogawa edited this page Jun 20, 2025 · 26 revisions

Welcome to the network-sketcher wiki!

image

Read me

  • Since the other day, we have confirmed that if an Excel file name contains square brackets [], the file cannot be clicked and opened, but we are waiting for improvement as we recognize that this is a problem on the Excel side. Currently, when opening an Excel file in Network Sketcher, please open it by specifying the file from the “Menu” screen, or drag and drop it into the Excel window.
  • Read me
  • Demo video
  • Installation
  • Release

User Guide

Language Link
English Link
Japanese Link

Known Bug

Known Bug Workaround
[ns-bug-020] Adding an L1 wire on a device may delete the L2 information on the L1 wire of other wires on that device. Back up the DEVICE file in advance, and restore and resynchronize the portion of the L2 data that was deleted after adding the L1 wire.
[ns-bug-013] Generating an L1 diagram with openpyxl 3.2.0b1 leaves a master file with TMP added to the file name. Use openpyxl 3.1.5 or remove TMP file after Network Sketcher is finished

Resolved

Resolved Bug Workaround Resolved Version
[ns-bug-021] Sync to Master file fails when VLAN name and L2 instance name are only numbers. None 2.5.1f
[ns-bug-017] Generating master data from a rough sketch that contains a line break in the device name fails. Delete the line break. 2.5.1e
[ns-bug-015] In an L1 configuration diagram, changing the placement of a device does not automatically update the vertical and horizontal orientation of wire connections. Delete and recreate the IF connection. 2.5.1e
[ns-bug-014] In an L1 configuration diagram, if horizontal wire connections are present, segments of the L3 all-areas diagram may overlap when drawn. Change the device placement to vertical, or use the “Focus on Connectivity” configuration diagram instead. 2.5.1d
[ns-bug-019] Synchronizing the Per Area configuration chart to the Master file initializes the Attribute sheet. Save the Attribute sheet of the DEVICE file in advance and resynchronize the Attribute sheet from the restored DEVICE file. 2.5.1c
[ns-bug-018] Broadcast domain recognition via Trunk link becomes inaccurate. None 2.5.1b
[ns-bug-016] In an L1 configuration diagram, changing a device’s IF name may cause synchronization with L2/L3 data to fail, resulting in a failure to generate the configuration diagram. Please delete and recreate the IF connection. 2.5.1a
[ns-bug-012] Layer 2 Diagram generation fails. Use version 2.3.1 or earlier 2.3.3(b)
[ns-bug-011] When creating a master file from a rough sketch, devices may not be included in the master file if the horizontal axis distances between devices are close. Increase horizontal axis distance between devices. 2.3.4
[ns-bug-010] When synchronizing L1 per area file to master file(3-1), VPN settings in L3 sheet of master file are deleted. Copy the VPN settings from the backup master file and resynchronize. 2.2.3(b)
[ns-bug-009] Failure to generate a master file for a rough sketch with no wire connections Creating dummy wires. 2.2.3(b)
[ns-bug-008] Master file creation may fail depending on vertical way point placement. None 2.2.1(b)
[ns-bug-007] VPN is not filled in the diagram when "Yes" is selected in the dialog after generating the VPN Diagram. Select "No" in the dialog 2.2.1(a)
[ns-bug-006] A bug that could cause duplicate rows to be output in the IP address table None 2.1.1(c)
[ns-bug-005] DEVICE file generation fails when using python v3.12.x Use Python version 3.11.7 or lower. This bug has been fixed in 2.1.1(b) to the extent that it does not stop with an error. However, since it is caused by a bug in openpyxl, update openpyxl to 3.1.3 or later as soon as possible.
[ns-bug-004] Caused file generation to fail in certain Windows environments None 2.1.1(a)
[ns-bug-003] On Mac OS, file cannot be opened from the dialog after drawing a diagram ignore dialogs 2.1.1
[ns-bug-002] If "Way Points" between Areas are not interconnected, the generation of "Master Data" will fail. Move unconnected "Way Point" between Areas up/down the "Area". 2.3.4
[ns-bug-001] If a "way point" that does not exist above or below the leftmost "Area" exists in the right "Area", the generation of "Master Data" will fail. Move unconnected "Way Point" between "Area" up/down the "Area". 1.12
Clone this wiki locally