Hi. I'm jon.404, a Unix/Linux/Database/Openstack/Kubernetes Administrator, AWS/GCP/Azure Engineer, mathematics enthusiast, and amateur philosopher. This is where I rant about that which upsets me, laugh about that which amuses me, and jabber about that which holds my interest most: *nix.
From zero to Ventrilo in 5 minutes...
Long story short:
Me. Rackspace cloud. Start timer.
Spin up Ubuntu 13.04 cloud server (512 MB size is perfect for this), start downloading Ventrilo Server for Linux. Edit Cloud DNS in the Rackspace mycloud portal to add A/CNAME/PTR after the assigned ip's show up...
A few moments later, login to server. Change root password. scp Ventrilo installer to server. Install the Rackspace cloud monitoring agent.
Create vent user. Untar ventrilo installer to vent user home. cd /home/vent/ventsrv. Edit ventrilo_srv.ini to add passwords (as required) and change codec settings (again, as required).
./ventrilo_srv > /dev/null &
netstat -nltp | grep 3784
Yup, it's running...but we're not done and it's only been 3 1/2 minutes!
ufw is stupid. It's a prime example of linux projects getting excessively bloated over time. I mean...well, nevermind...I've only got about another minute, right? Sigh.
iptables -A INPUT -p tcp -m tcp --dport 22 -j ACCEPT #(more on this later)
iptables -A INPUT -p tcp -m tcp --dport 3784 -j ACCEPT
iptables -A INPUT -p udp -m udp --dport 3784 -j ACCEPT
iptables -P INPUT DROP #(yeah, yeah, yeah. Learn how to use your
# firewall properly and you won't lock yourself out...sheesh)
iptables -P FORWARD DROP
Setup rate limiting rules for ssh.
Call friends and tell them the hostname, port, and password for the new vent server.
Well, ok, that last step might not happen within the 5 minute timeframe =)
Ok, I suppose adding a ventrilo initscript wouldn't be a bad idea, either, so yeah, more than 5 minutes =P
Me. Rackspace cloud. Start timer.
Spin up Ubuntu 13.04 cloud server (512 MB size is perfect for this), start downloading Ventrilo Server for Linux. Edit Cloud DNS in the Rackspace mycloud portal to add A/CNAME/PTR after the assigned ip's show up...
A few moments later, login to server. Change root password. scp Ventrilo installer to server. Install the Rackspace cloud monitoring agent.
Create vent user. Untar ventrilo installer to vent user home. cd /home/vent/ventsrv. Edit ventrilo_srv.ini to add passwords (as required) and change codec settings (again, as required).
./ventrilo_srv > /dev/null &
netstat -nltp | grep 3784
Yup, it's running...but we're not done and it's only been 3 1/2 minutes!
ufw is stupid. It's a prime example of linux projects getting excessively bloated over time. I mean...well, nevermind...I've only got about another minute, right? Sigh.
iptables -A INPUT -p tcp -m tcp --dport 22 -j ACCEPT #(more on this later)
iptables -A INPUT -p tcp -m tcp --dport 3784 -j ACCEPT
iptables -A INPUT -p udp -m udp --dport 3784 -j ACCEPT
iptables -P INPUT DROP #(yeah, yeah, yeah. Learn how to use your
# firewall properly and you won't lock yourself out...sheesh)
iptables -P FORWARD DROP
Setup rate limiting rules for ssh.
Call friends and tell them the hostname, port, and password for the new vent server.
Well, ok, that last step might not happen within the 5 minute timeframe =)
Ok, I suppose adding a ventrilo initscript wouldn't be a bad idea, either, so yeah, more than 5 minutes =P
Total Comments 1
Comments
-
The Rackspace cloud currently charges $0.12/GB for *outbound* traffic, so you have to calculate what maximum bitrate you're willing to live with based on that. (I have a seedbox for OpenBSD installer torrents and kali linux torrents, so I sorta needed to go down this road because the 20GB/day of upload bandwidth was a bit startling at first =)
Here's the math:
$monthly_bandwidth_budget / 0.12 = GB_target
GB_target / 248 = GB_per_day (eight people talking constantly for 31 days straight)
GB_per_day / (24 * 60 * 60) = GB_per_sec (probably a very small number)
GB_per_sec * 1024 * 1024 * 1024 = target_bytes_per_sec
Find a codec that comes in just below your target_bytes_per_sec (if this is a big number, i.e. you have $200 a month budget for bandwidth, pick whatever you want =P ).
Done.
Going by this math, if you picked the highest Speex codec (note: there is a GSM that uses more bandwidth, but meh), that would be ( 5520 bytes/sec / (1024^3) ) * 60 * 60 * 24 * 248, or roughly $13.25 a month in bandwidth charges.Posted 06-05-2013 at 09:43 PM by rocket357 
Updated 06-05-2013 at 11:20 PM by rocket357
