Intika-Linux-Network/Network-Watcher

Work in progress

intika opened this issue · 1 comments

intika commented

Issues:

  • Clearing one single line works but for multiples lines 30% are randomly cleaned
  • Block/allow in tomoyo not working test with code... check similar issue on taskman
  • Connections on other namespaces are not monitored !
  • Add raw/af_packet support (this is already the case on tcp-view)
  • Switch to tcp-view and get rid of gtk ?

Improvements:

  • Assign 'delete' to clear function
  • As the button used to clear closed a similar function could be done to clear selected (same as existing but if selected > delete)
  • Implement pop-up on tomoyo functions like task manager
  • Button to save filter
  • Add raw support net.c or datasource.cpp
  • Rename to network watcher
  • Button to start system monitor
  • Integrate nload and nethogs
  • Appimage pr
intika commented

1 - Integrate netlimitter with logs (Net Activity Viewer) just edit net activity viewer to keep disconnected connection instead of removing them from the list...
2 - Proxychains/tsocks launcher (start apps proxified... integrate plasma search ? "alt + space")

  • Proxychains (proxychains-ng does not work with chrome and others. proxychains works with chrome etc.)

  • Tsocks Does not work with chome but firefox ok

  • Injection must be done before process start

  • A solution can be /usr/local/bin before /usr/bin like firejail

  • An other solution could be widely inject proxychains BUT change its code to only inject itself on selected app list (check [proxychains] DLL init std output when starting)

  • Proxychains/Tsocks can be injected with export LD_PRELOAD=/usr/local/lib/libproxychains4.so and export LD_PRELOAD=/usr/lib64/libtsocks.so.1 before starting the app

  • tcp view !!!

  • tray icon from https://github.com/Intika-Linux-SSH/SSH-Tunnel-Manager-Gnome

as blocking allowing is based on pid this can not be done on inactive connection

disconnect connection when tomoyo block is called