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. LTE network (LTE-A, D2D, FEMTOCELL) simulations crash if we run the scenario without UEs (v11.0)
  3. Device real IP & Destination real IP validation is not perfect in Multicast & Broadcast emulation.
  4. VANET may not work if NetSim is installed silently.
  5. If the link name is left empty, then the simulation will crash. In v11 this option is not present.
  6. Users cannot enable radio range when the network is created in map view. In v11 for CR network radio range is not working
  7. Packet size limit in TDMA (Military Radio):High packet sizes will lead to zero throughput. Max Packet Size = (Time_Slot_Block_Size*Slot_Duration*Data_Rate) / 8 where SLOT_DURATION is in millisecond and DATA_RATE = 25kbps.
  8. Default gateway can’t be empty: When user manually provides a 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 blank “default gateway” field in UI.
  9. Antivirus software's may identify NetSimSimulation.exe as malicious and block or remove it from NetSim install directory. Exceptions will have to be added to avoid this. 
  10. Through open network the position of the Adhoc link Icon is changing.
  11. Up-link Speed and Down-link Speed are independent parameters and need to be configured individually.
  12. MANET Networks give zero throughputs when routing is involved
  13. If Zigbee and WLAN is configured together in the same network then animation for battery model does not work correctly and may lead to undefined behaviour
  14. TDMA/DTDMA cannot be interfaced with WLAN. The first network created through the GUI must be TDMA/DTDMA
  15. 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
  16. Radio Range will not work in Map view
  17. 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
  18. 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
  19. AODV protocol does not work in case of route error - RERR.
  20. In WSN network modifying the network layer protocol leads to simulation crash (v11.1)
  21. LTE Carrier aggregation - only the first carrier is used in the calculation.
  22. WSN network scenario's with Application types Peer to Peer/ HTTP/ Database crash if simulated for more than 100 seconds.
  23. In WSN / IOT the transmitter power of the sensor in Interface(Zigbee) is shown as dBm instead of mW
  24. 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.
  25. The very first time Emulation is run after installation, 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"