docker speed test

[Cyberwasp]

Back when I first started with my NAS I installed Openspeedtest to see how fast the data connection was. I'd like to try it again. However, the tutorial I used to install it hasn't been updated and the installation has. Is there an updated tutorial anywhere someone may know of. TIA

 

[Deleted member 5784]

I've not used Openspeedtest but I have used iperf3 which does a similar thing, albeit from the CLI rather than a browser.
Docker install guide: How to run a local iPerf3 speed test server on Synology NAS in Docker | LtRoyalShrimp

This guy has lots of syno docker guides and seems to have one for ost: How to Install OpenSpeedTest on Your Synology NAS
He has a slightly weird way of configuring & running docker via the syno's User Defined Scripts dialogue rather than via SSH or the GUI, but it should nevertheless work fine.

 

[Cyberwasp]

I'm familiar with his scripts and tried it. however, it doesn't work. it doesn't even download the image. I have one for Pihole that works fine!

 

[Cyberwasp]

Did a manual install and finally found what had changed to get it to work. Although am not sure if the results are right!! Thank you

 

[Deleted member 5784]

I'm familiar with his scripts and tried it. however, it doesn't work. it doesn't even download the image. I have one for Pihole that works fine!

The

docker run

command in his script pulls the image from the docker registry if it's not on your system.
Edit: have just seen you have managed to download it.

Not sure what results you were expecting? This looks like you are running a test of your LAN (or you could have 1Gb symmetrical Fibre...)?

 

[Cyberwasp]

That's what I was wondering. As I have 1g fiber, but I want the LAN test! I'm gathering that's what it's showing! my isp is usually in that range also.

 

[Rusty]

That's what I was wondering. As I have 1g fiber, but I want the LAN test! I'm gathering that's what it's showing! my isp is usually in that range also.

This is LAN speed.

If you want WAN speed try this compose:

version: '3.3'
services:
    speedtest:
        container_name: speedtesttracker
        image: henrywhitaker3/speedtest-tracker
        ports:
            - 80:80
        volumes:
            - ./speedtesttracker:/config
        environment:
            - TZ=
            - PGID=1000
            - PUID=1000
            - OOKLA_EULA_GDPR=true
            - AUTH=true
        logging:
            driver: "json-file"
            options:
                max-file: "10"
                max-size: "200k"
        restart: unless-stopped

Change the values as needed.

 

[johnnygoodface]

Hi @Rusty
Speedtesttracker is up and running on my box, but as soon as I enable my firewall, it doesn't work. Any chance you know which ports or whatever needs to be open on the WAN side for it continue to work

 

[Rusty]

but as soon as I enable my firewall

You will have to be a bit more specific. What fw did you set up? Sspeedtest-tracker uses Ookla's speedtest cli, so that should mean TCP/UDP 8080

 

[johnnygoodface]

I'm talking about my Synology NAS firewall. I've tested both TCP/UDP 8080 and I still get red Xs as results, rather then the actual Ping, down and up speeds. When I disable my firewall completly, then all is good.

 

[Rusty]

I'm talking about my Synology NAS firewall. I've tested both TCP/UDP 8080 and I still get red Xs as results, rather then the actual Ping, down and up speeds. When I disable my firewall completly, then all is good.

TCP/UDP 5060, add that as well.

 

[johnnygoodface]

@Rusty I've tried both TCP/UDP 5060 and 8080 (at the same time):

and each time I enable my NAS firewall I get this (after the [services.d] done.)

and this

 

[Rusty]

@Rusty I've tried both TCP/UDP 5060 and 8080 (at the same time):

View attachment 11448

and each time I enable my NAS firewall I get this (after the [services.d] done.)
View attachment 11446
and this
View attachment 11447

Hmm. The container is in a network that has internet access? This doesnt look like incoming issue at all, but an outgoing. It looks like your instance is unable to reach other destinations not the otherway around.

Can you try and ping anything from the command line from within the container?