Local listening interface -> List the local listening interfaces

[teddyrogers]

Tribler 8.1.0, there is now the new feature under settings, "Local listening interface". Thank you very much for this!

Would it be possible to:

1. List the available network interfaces?

• This would save having to manually search/ locate the interface/s and avoid spelling/ text input field mistakes.

3. Have a means for testing the interface is working?

• You could argue if it does not work there would be no peers and torrent activity.

[qstokkink]

Testing if the interface is working will be part of #8444 (scheduled for 8.2). Coming soon 🚀

I attempted implementing network interface names before. I appreciate having names too. However, a stable cross-platform way to get the network interface names turned out to be too fragile - to the point of me opting to not implement it. I don't see us implementing this.

I think that covers our decisions on both of your suggestions. Stay tuned for the 8.2 release!

[teddyrogers]

@qstokkink I don't think this is even working correctly. I have tried specifying a know network interface and I have torrents sitting with 0 seeds and peers, doing nothing. Strangely some torrents do seem to be active and working. When I remove the network interface string and restart there are no problems, everything is okay again.

Essentially there does not appear to be a method within Tribler to confirm the network interface is being used and, active, or if its "leaking" data across other network interfaces.

Until there is some reliability and assurance I would recommend this feature be disabled in the next release - or have it hidden for testing only.

Would you like me to create a separate issue or reopen?

[teddyrogers]

I have tried specifying a know network interface and I have torrents sitting with 0 seeds and peers, doing nothing.

I should mention Tribler was working okay after defining a known network interface in the evening and then, checking in the morning, Tribler reported the zero seeds and peers (for nearly all torrents in the list). I have associated this issue with using a network interface. I have restarted Tribler and running another test, all has been good for two hours.

[teddyrogers]

@qstokkink Tribler has been running for over 18 hours and no torrents have not stopped with 0 seeds and peers. I can't say for certain what caused this, if it happens again I will report back.

Referring to the image below, Tribler should not be listening on 192.168.101.159 as it is another network interface. Doing a comparison with qBittorrent this never happens. I set-up network monitoring and have not seen any connections being established. Why is Tribler listening on another interface than the one defined in the settings?

[teddyrogers]

I have torrents sitting with 0 seeds and peers, doing nothing.

It has done it again...

[qstokkink]

I think that behavior may be caused by #8483, which is already fixed for the next 8.1.1 pre-release (which is not out yet).