Applicable Versions
NetSim AcademicNetSim StandardNetSim Pro


Applicable Releases
v12.2
 

  1. User modified parameters will not reflect in newly dropped devices: After dropping nodes on the environment, modification of protocols/ global properties (like Physical Layer parameters, Data Link Layer parameters, and others) in one node will reflect in all other nodes. However, after modification, if any new node is dropped, the modifications will not reflect in the newly dropped nodes.  
    • Solution: After dropping new nodes, open the properties of any previously dropped wireless node and click accept
  2. Device real IP & Destination real IP validation is not perfect in Unicast, Multicast & Broadcast emulation.
  3. The packet size limit in TDMA (Military Radio): High packet sizes will lead to zero throughputs.  Max Packet Size = (Time_Slot_Block_Size*Slot_Duration*Data_Rate) / 8 where SLOT_DURATION is in millisecond and DATA_RATE = 25kbps.
  4. Default gateway can’t be empty: When a user manually provides value in the blank “Default Gateway” parameter in any device, then it cannot be made blank again, which in turn may lead to a simulation crash. Users should not enter any value in the blank “default gateway” field in UI.
  5. Antivirus software may identify NetSimSimulation.exe as malicious and block or remove it from the NetSim install directory. Exceptions will have to be added to avoid this.
  6. Up-link Speed and Downlink Speed are independent parameters and need to be configured individually.
  7. If Zigbee and WLAN is configured together in the same network then the animation for the battery model does not work correctly and may lead to unexpected behavior
  8. DSR is not designed to work with ICMP, VLAN, etc. Hence users cannot set ICMP, VLAN, etc when running simulations involving MANETs connected to wired networks
  9.  Animation over map view requires the user to do  
    • A single click on the map to load the devices
    • The map loads India by default. User will have to move the map to the location where devices were placed
    • Wireless node movement may not be accurate
  10. The very first-time Emulation is run after installation, the user may see the error "NetSim couldn't find either of Windivert32.sys or Windivert64.sys files of Windows Packet Divert(WinDivert) and further throwing the ERROR_CODE(2) - File not found"
  11. In the case of OSPF routing protocol, if 7 or more routers are connected linearly then communication may not happen across the routers
  12. Bridge nodes in MANET do not support ZRP and OLSR protocols.  
  13. Packets received will not get affected when the Path loss model and Distance is changed (COST231-HATAURBAN, COST231-HATASUBURBAN, HATAURBAN, HATASUBURBAN, and TOW_RAY path loss models)
  14. Wireshark is crashing once it is set to Online in wireless devices.
  15. The scenario is crashing when more than 15 ENB’s/gNB’s are used in the network.
  16. In Satellite Network getting Zero throughputs for a scenario with 2 Gateway’s connected through the router. The same issue occurs in case of 2 bridge nodes.
  17. Issues related to Emulation Ping - LTE and VANET
  18. 32 bit and 64-bit setup results are not matching
  19. Zero throughput for Point to point and serial connection scenario in TDMA Radio Network
  20. Re-Installation issues in User Mode
    • In User mode install PRO setup through custom installation. While installing in choose components window uncheck the Netsim checkbox & check only one component & install completely. On the Netsim home page we can observe only one component is present. Now reinstall the Pro setup through express mode completely, we can observe that even we have installed setup in the express mode we are getting only one component which we checked in custom mode.
    • Install any setup of Netsim through express mode or custom mode. Reinstall NetSim and we can observe that the login window is not being displayed after re-installation
  21. Congestion Plot Replot option is not working.
  22. If we uncheck Link plots and run, the Simulation results window is not opening
  23. Workspace multiple NSF file issues experiment getting disappear from GUI.
  24. In cognitive radio networks, the Ethernet interface of CR_base_station is disappearing through open simulation when clicked on the reset button
  25. Connection and dropping devices in 5G networks leads to a wrong IP address for devices
  26. Antivirus issue
    • Norton and K7 Total security are blocking NetSim.exe, NetSim Setup, Uninst.exe
    • Trend Micro detecting simulation.exe,uninstall.exe
    • Avast is blocking Checksum.txt while creating default workspace it won't allow to create a workspace
  27. In any network, zoom then create any scenario and run simulation the scroll bar & Toolbar options are disappearing.

 

Applicable Releases
v12.0v12.1
  1. User modified parameters will not reflect in newly dropped devices: After dropping nodes on the environment, modification of protocols/ global properties (like Physical Layer parameters, Data Link Layer parameters, and others) in one node will reflect in all other nodes. However, after modification, if any new node is dropped, the modifications will not reflect in the newly dropped nodes. 
    • Solution: After dropping new nodes, open the properties of any previously dropped wireless node and click accept.
  2. Device real IP & Destination real IP validation is not perfect in Multicast & Broadcast emulation.
  3. VANET may not work if NetSim is installed silently.
  4. The packet size limit in TDMA (Military Radio): High packet sizes will lead to zero throughputs. 
    • Max Packet Size = (Time_Slot_Block_Size*Slot_Duration*Data_Rate) / 8 where SLOT_DURATION is in millisecond and DATA_RATE = 25kbps.
  5. Default gateway can’t be empty: When a user manually provides value in the blank “Default Gateway” parameter in any device, then it cannot be made blank again, which in turn may lead NetSim to crash. Users should not enter any value in the blank “default gateway” field in UI.
  6. Antivirus software may identify NetSimSimulation.exe as malicious and block or remove it from the NetSim install directory. Exceptions will have to be added to avoid this. 
  7. Up-link Speed and Downlink Speed are independent parameters and need to be configured individually.
  8. MANET Networks give zero throughputs when routing is involved
  9. If Zigbee and WLAN is configured together in the same network then the animation for battery model does not work correctly and may lead to undefined behavior
  10. DSR is not designed to work with ICMP, VLAN etc. Hence users cannot set ICMP, VLAN etc when running simulations involving MANETs connected to wired networks
  11. If applications like FTP, HTTP, COAP, Database are run over a slow & highly error-prone network, where connection keeps getting established and terminated, TCP may crash
  12. Animation over map view requires the user to do 
    • A single click on the map to load the devices
    • The map loads India by default. User will have to move the map to the location where devices were placed
    • Wireless node movement may not be accurate
  13. AODV protocol does not work in case of route error - RERR.
  14. LTE Carrier aggregation - only the first carrier is used in the calculation.
  15. Applications in WSN/IoT in real life run UDP in general. However, for simulation purposes NetSim allows TCP to also be configured. However, if TCP is configured and the network links have high BER then NetSim may crash since the network is very slow and the BER is very high.
  16. The very first-time Emulation is run after installation, the user may see the error "NetSim couldn't find either of Windivert32.sys or Windivert64.sys files of Windows Packet Divert(WinDivert) and further throwing the ERROR_CODE(2) - File not found"
  17. In the case of OSPF routing protocol, if 7 or more routers are connected linearly then communication may not happen across the routers.
  18. Bridge nodes in MANET do not support ZRP and OLSR protocols.