


Some distros may install it at /usr/local/bin or /bin. The below commands assume drone was installed in /usr/bin. Only the drone agent requires special privileges, not the controller (See Controller-Agent Architecture). I don’t like running Ostinato/Drone as root. You have WinPcap installed (Windows Only).The drone executable is in the same path as ostinato.When I run ostinato, it does not start drone (the server) automatically The fix is simple - just add C:\windows\system32\Npcap\ to your system PATH. If you have npcap installed in native mode, the DLLs are installed into C:\windows\system32\Npcap\ instead of the standard system DLL directory C:\windows\system32\ If you do, check the location of wpcap.dll and packet.dll. Ostinato on Windows does not start because wpcap.dll or packet.dll is not foundįirst make sure you have npcap (or winpcap) installed. Where do I get answers regarding the Ostinato Python API? How do I see debug console logs on Windows platforms? Why isn’t my PCAP file imported correctly? Ostinato shows a “diff” after import

Can I save/restore streams across Ostinato sessions? When I try to view the capture buffer, Wireshark gives me an error “The file could not be opened: Uncompression error: buffer error”. Why does my DUT show incoming traffic rate less than the outgoing rate shown by Ostinato? What is the maximum transmit rate that Ostinato supports? On starting Ostinato/Drone, I get an error “bound address is already in use”. After starting Ostinato, the port group status is disconnected (the port group icon is red) Ostinato on Windows does not start because wpcap.dll or packet.dll is not found
