I have an iperf in servermode on each hw server and on virtual pfsense installations. Have found network issues and bottlenecks. Thanks for finding the docker version.
A tip on using it as a stack that I just discovered. You can pass command line arguments to the stack, example below. Just tested and works perfectly. Thanks for the video, I've been looking for something similar as well! version: '3.3' services: iperf3-server: image: networkstatic/iperf3:latest container_name: iperf3-server restart: always ports: - 5201:5201 command: -s
I don't understand why you need it on more ports. It only recognizes one port. To get it to work on multiple ports, you'd have to install multiple instances of the container. If you want to use it on a port other than 5201, then you would change the port line to be something like: - '5555:5201' Just don't change the ":5201" because that's the port that the container is listening on.
Thank you @@DBTechYT My understanding is that once a client uses the default port 5201, the other clients have to wait until that port is released. The plan is to create a server multiple client PCs can use.
That is correct about the port. This container only listens on 1 port. Internally that port is 5201, but you can change that port to something else with the instructions I provided in my previous comment. If you want/need to deploy multiple instances of this, then you could do that and just change the port number incrementally on each instance. For example: First container - '5555:5201' Second container - '5556:5201' Third Container - '5557:5201' Fourth Container - '5558:5201' You would also need to change the container name of each instance as well. So, like: container_name: iperf3-server1 container_name: iperf3-server2 container_name: iperf3-server3 container_name: iperf3-server4
I have an iperf in servermode on each hw server and on virtual pfsense installations. Have found network issues and bottlenecks. Thanks for finding the docker version.
A tip on using it as a stack that I just discovered. You can pass command line arguments to the stack, example below. Just tested and works perfectly. Thanks for the video, I've been looking for something similar as well!
version: '3.3'
services:
iperf3-server:
image: networkstatic/iperf3:latest
container_name: iperf3-server
restart: always
ports:
- 5201:5201
command: -s
This is brilliant!! Thank you! I'll update the blog post with this :)
Very handy! I'm also looking for a general cpu/IO docker app. To compare my various hosts.
Thanks!! You might check out this video? ua-cam.com/video/exZ179uNQW8/v-deo.html
Hallo This installation is compatible with Raspberry Pi Portainer also?
You should activate Jumbo Frames (MTU 9000) for 10GB speed
How can I edit the docker instance to allow more ports to be used besides the 5201 port?
I don't understand why you need it on more ports. It only recognizes one port. To get it to work on multiple ports, you'd have to install multiple instances of the container.
If you want to use it on a port other than 5201, then you would change the port line to be something like:
- '5555:5201'
Just don't change the ":5201" because that's the port that the container is listening on.
Thank you @@DBTechYT
My understanding is that once a client uses the default port 5201, the other clients have to wait until that port is released.
The plan is to create a server multiple client PCs can use.
That is correct about the port. This container only listens on 1 port. Internally that port is 5201, but you can change that port to something else with the instructions I provided in my previous comment.
If you want/need to deploy multiple instances of this, then you could do that and just change the port number incrementally on each instance. For example:
First container
- '5555:5201'
Second container
- '5556:5201'
Third Container
- '5557:5201'
Fourth Container
- '5558:5201'
You would also need to change the container name of each instance as well. So, like:
container_name: iperf3-server1
container_name: iperf3-server2
container_name: iperf3-server3
container_name: iperf3-server4
Change of compose needed for logging to work.
version: '3.3'
services:
iperf3:
restart: unless-stopped
container_name: iperf3-server
ports:
- '5201:5201'
image: networkstatic/iperf3
stdin_open: true # docker run -i
tty: true # docker run -t
command: -s
Thanks! I've updated the stack
well thanks to this comment I was able to build ctop using docker compose in portainer. thanks Ron
@@eldmaster how did you do that? I would love to have this in portainer
nm i got it