Challenges and Discrepancies

Challenges:

• Unstability of the TK GUI:
  • Decision on the GUI between Django and TK, settled upon tk for a simple local interface, but the unstability of the tk gui caused a number of problems
• Graph Plotting:
  • Plotting a proper network graph which is readable from the data obtained was quite an effort, used different libraries to arrive at one.
• Performance and Timing:
  • The performance and timing of the total application was a big challenge with different data gathering and output generation

Known Bugs:

• Memory Hogging

  • Sometimes memory hogging occurs when lower RAM is present in the system as the data stored in the memory from the pcap file is huge
  • Should be Fixed by moving data into a database than the memory itself

• Race Condition

  • Due to mainloop of the TK gui, other threads could undergo a race condition
  • Should be fixed by moving to a better structured TK implementation or Web GUI

• Tk GUI Unstability:

  • Same reason as above

• Code:

  • clumsy and unstructured code flow

• Clumsy Graph:

  • This occurs when there are no traffic routes for the selected protocol. Graph has huge nodes displayed

• Unlimited Progress bar problem

  • GUI does not update and progress bar keeps going infinite.

• PyVis assert error with names having more than one .

  • Absolute path file name with 2 .s in the name would cause an error

• Current Fix in rare occasions:

  • If any of the above issue occurs the progress bar keeps running and no output is generated, a restart of the app would be required.

• I expect a high quality code and PcapXray still needs a bunch of code refactor work! But the Solution works!, working to improvise. Having security fun!