Allow selection of interface for speedtest tracker to utilize

[teeesss]

I have multiple interfaces on my system and the speedtest tracker is picking an interface I don't want to use.

Allow setting the local interface to use, if there are multiple interfaces to pick from.

[alexjustesen]

On first thought since Speedtest Tracker doesn't really know what interface is being used I'm wondering if this is something that should be done at the Docker container level.

I'll look into it some more.

[gaby]

@alexjustesen By default it can do what its doing now, but there should be an ENV or cli flag that allows specifying an interface.

For example, if this is running with Docker using --net host

[alexjustesen]

If it's at the Docker image level that's not something I would be managing anymore, LSIO will be the only image for this project soon so I'd open a support issue on the repo: https://github.com/linuxserver/docker-speedtest-tracker

[gaby]

@alexjustesen Isnt this project the ones that chooses how to do the speedtest? You can't specify interfaces in Docker

[alexjustesen]

@alexjustesen Isnt this project the ones that chooses how to do the speedtest? You can't specify interfaces in Docker

This project extends the speedtest CLI so wouldn't any networking have to be passed through Docker's network?

[gaby]

@alexjustesen The speedtest-cli has a --interface and -I flags that allow the user to specify which interface to use for the test. With this UI there's no way to specify that.

[alexjustesen]

This will require more research as that network would need to be passed through to the Docker container for it to work.

[gaby]

@alexjustesen Just by running with --net host all interfaces will be available. This is mostly for use cases where the user has multiple interfaces in the host and/or container.

Since I believe right now it just uses whatever is the default route.

[gaby]

@alexjustesen Any update on this?

[alexjustesen]

The short answer: if the issue isn't completed that's a nope.