💡 Feature Description
I would love to have an option where we can add all the IPs on our servers we own, and then via user management, or certain app managements be able to add the IPs to them.
Adding to this as I almost forgot: specifying ports for rtorrent would be great also. I actually have a couple ports for each user, but even if it just had to be a range where we could tell rtorrent to limit port range would be awesome. (Im sure i do my server wrong, as I firewall everything and only have a handful of necessary ports open. maybe i need to move to cloudflare and some sort of new tech shits ;p)
📈 Motivation and Context
Say I have 20 IPs. (forget how many i actually have :P)
I use 1 IP for my domain for my dash board.
I use one domain specifically for SSH (all those bots scrub torrents for IPs to try and hack)
I have 1 IP that i assign to each user, and have to put in the .rtorrent.rc, and the autodl for irc (so they have matching IPs)
Then a few that I can rotate out as needed or just for keeping it fresh.
This is a great feature to separate the users so they arent hitting the trackers with the same IP.
Theres more accountability per IP if something happens so its nice to know who an IP belongs to if they are causing issues.
🛠️ Suggested Implementation (if known)
I would think there would be one section just to add all the IPs to the system (manually updating the networking is kinda tedious if you have a bunch)
Then in each user, perhaps have a pulldown for that user. that way all the apps that you may want to use that ip (such as vpn, rtorrent, autodl, etc) configs will automatically assign that IP.
🖼️ Visuals or References (optional)
🔗 Related Issues or Discussions
🧩 Additional Notes
💡 Feature Description
I would love to have an option where we can add all the IPs on our servers we own, and then via user management, or certain app managements be able to add the IPs to them.
Adding to this as I almost forgot: specifying ports for rtorrent would be great also. I actually have a couple ports for each user, but even if it just had to be a range where we could tell rtorrent to limit port range would be awesome. (Im sure i do my server wrong, as I firewall everything and only have a handful of necessary ports open. maybe i need to move to cloudflare and some sort of new tech shits ;p)
📈 Motivation and Context
Say I have 20 IPs. (forget how many i actually have :P)
I use 1 IP for my domain for my dash board.
I use one domain specifically for SSH (all those bots scrub torrents for IPs to try and hack)
I have 1 IP that i assign to each user, and have to put in the .rtorrent.rc, and the autodl for irc (so they have matching IPs)
Then a few that I can rotate out as needed or just for keeping it fresh.
This is a great feature to separate the users so they arent hitting the trackers with the same IP.
Theres more accountability per IP if something happens so its nice to know who an IP belongs to if they are causing issues.
🛠️ Suggested Implementation (if known)
I would think there would be one section just to add all the IPs to the system (manually updating the networking is kinda tedious if you have a bunch)
Then in each user, perhaps have a pulldown for that user. that way all the apps that you may want to use that ip (such as vpn, rtorrent, autodl, etc) configs will automatically assign that IP.
🖼️ Visuals or References (optional)
🔗 Related Issues or Discussions
🧩 Additional Notes