Feature Request: Allow Ignoring Self Connections in TCP Monitor

[ArmchairLegend]

I ran into this while trying to determine why my TCP Monitor rule for Plex Media Server was giving apparent "false positives" when no devices were connecting to it. My knowledge of Plex is extremely limited but the issue was discovered to be that system connecting to itself every so often, i.e. in Netstat there were entries for established connections from 127.0.0.1:xxxxx to 127.0.0.1:yyyyy.

I modified my TCPMonitor.py to exclude any and all entries where the source and destination were both 127.0.0.1 but thought that this might be better as an option available in the config file, either globally or on an entry by entry basis somehow.

[kaayman (emakaay)]

I use the TCP Monitor to monitor different IO depending processes, like:
- sabnzbd
- samba shares
- ftp servers

sometimes these services also use network IO when sabnzbd is not downloading, samba shares are not used. Just small amount of network traffic keeps powernap from going to sleep.

I would really like an option to define a minimal byte threshold, before activity on the network is really treated as traffic (and powernap should not put the computer into a powernap).

Maybe it is possible to add a parameter to the definition of monitored processed that can define this threshold. When threshold is not given, the default method is used. Every change in IO traffic, will stop powernap from sleeping.

I think Plex problem could also be addressed with this.

PS: I could try to code this my self. Have programming skills (only not in python), but would like to contribute if this feature request is honored

[kaayman (emakaay)]

Sorry for the confusion. I'm talking about the IOMonitor instead of the TCP Monitor

[Linus Johansson (termosen)]

@ArmchairLegend

Any chance you could share how you modified the TCPMonitor.py for excluding localhost?
Having the same issue as well, that Plex issues connections on 127.0.0.1.

Br Linus