-
Notifications
You must be signed in to change notification settings - Fork 68
Feature - Port Ranges #24
Comments
I implemented this a few versions ago, but I apparently forgot to put it in the docs. You should be able to put in |
Hmm, using |
Actually, not a timeout Uptime Kuma reports a |
I just tested this out with my setup and one of the ports in the block. It works for me. What does the PostUp section of your |
Sorry for the delay All ports open in Oracle Cloud (i think) VPS wg0.conf
Now all ports are broken, whereas if I don't have port ranges but every thing else it's just fine |
Terms
Summary
The ability to enter ports such as
3000-4000/tcp
since its much better than3000/tcp,3001/tcp,etc
. This would also need to be followed up with support for specifying one IP for this range.Motivation
Why are we doing this?
To make it a lot faster to do lots of ports.
What use cases does it support?
Game server panels, or other applications which require a large range of ports
What is the expected outcome?
Entering ranges of ports
Potential conflicts / foreseeable issues
None that I can think of
Additional Context
I've had to do it manually for only 100 ports with both protocols (so 200 entrys) and it took a while, would be much nicer to just deal with 2 entries (one per protocol)
The text was updated successfully, but these errors were encountered: