Run Sniffnet on startup

[Aikatsui]

Is there an existing issue for this?

• I have searched the existing issues.

Describe the solution you'd like

• Run Sniffnet on startup and keep it minimized to the system tray. (Related to [request] system tray support #217)
  Currently, Sniffnet does not start automatically on Ubuntu 24.04.1 LTS for non-root users. I have to launch the application manually and select the traffic source each time. Please add a toggle for this option under General → Settings so users can easily enable or disable it.
• Use previous analysis configuration on startup.
  Sniffnet should remember the user’s last configuration and automatically resume analysis on startup by default. If needed, users can stop the analysis, change the traffic source.

[GyulyVGC]

Hey @Aikatsui I think what you're asking for can be already done pretty easily, except the system trail part.

Sniffnet already saves configurations and reload them at startup, and it supports the -a command line option to automatically start the analysis from a given network adapter.

Then if you want to run it at startup, you can just create a service file to run it as a daemon.

[Aikatsui]

This issue isn't entirely a duplicate of #217

@GyulyVGC Then if you want to run it at startup, you can just create a service file to run it as a daemon.
@Aikatsui Please add a toggle for this option under General → Settings so users can easily enable or disable it.

I know, but I expected to see this setting in the graphical user interface. See the example below.

This is not uncommon for modern Linux applications nowadays.

Sniffnet already saves configurations and reload them at startup

It doesn't. Sniffnet v1.5.0

bug.mp4

[GyulyVGC]

Thanks for the more detailed explanation.
So, two points:

1. I don't like the idea of providing an option to run the app on startup without first supporting system tray
2. The configurations being saved are stuff like custom filters, notifications, favourites, themes, blacklist, DB, etc. Captured data isn't saved across sessions and this is on purpose, since each new session is supposed to restart the data analysis from scratch.

[Aikatsui]

I don't like the idea of providing an option to run the app on startup without first supporting system tray.

It's OK. You can keep this issue open to track the feature request. After adding system tray support, you can implement this option.

@GyulyVGC The configurations being saved are stuff like custom filters, notifications, favourites, themes, blacklist, DB, etc. Captured data isn't saved across sessions and this is on purpose, since each new session is supposed to restart the data analysis from scratch.
@Aikatsui Use previous analysis configuration on startup.
Sniffnet should remember the user’s last configuration and automatically resume analysis on startup by default. If needed, users can stop the analysis, change the traffic source.

I tried to clarify in the details and video above that I don't want to have to select a network adapter and click 'Start' every time I launch the application or open terminal and run a command. In the video, you can see that I currently have to manually pick a traffic source and click 'Start. This is an annoying workflow for a personal computer or laptop. While power users might work around this by creating a scheduled task with command-line arguments, it shows that the software isn't easy to set up. Even consumer tools like GlassWire and enterprise software like Ntopng automatically start analyzing traffic without requiring user intervention.

https://www.glasswire.com
https://www.ntop.org/products/traffic-analysis/ntopng
https://hub.docker.com/r/ntop/ntopng
https://github.com/ntop/ntopng

@GyulyVGC Captured data isn't saved across sessions and this is on purpose, since each new session is supposed to restart the data analysis from scratch.

You've misunderstood. This isn't related to this issue, but it would be a great addition for #1041 (Navigate historic data) and nice-to-have feature for analyzing past captured data within custom time and date ranges. It seems you may not be interested in Sniffnet retaining data for a long period. So, if implemented, you could offer an option for users to define their own data retention period (e.g., past 24 hours, 7 days, 1 month, 3 months, or 6 months). Many people will like it.

Sample: As shown in the screenshots below, GlassWire allows users to analyze data within custom time and date ranges. As far as I remember, the application retains all captured data from the time of installation.

[GyulyVGC]

Thanks for the additional feedback @Aikatsui

Now I see what you mean.
Sniffnet remembers the adapter that was sniffed last time, but it doesn't automatically start capturing on it.
Since currently it's not possible to run the app on startup, I see little sense to immediately start capturing from the adapter because the user has to click on the app icon, so an interaction is required anyway.

I've reopened this issue to track the request to start the app on startup, and in such case the app can immediately start capturing from the saved network adapter.

Let's keep the historical-data stuff as part of #1041