The deal is:-
The I've got an e-smith management module, but I'm stuck deciding between too flexible or easy to use

I've think this is the easiest layout though
Choose the closest inbound links speed (in kps) [56, 128, 256,512,1000,1500, 2000]
Note: DNS and ICMP will only ever be given a maximum of 5% of the total inbound bandwidth. This should help stop the majority of ping-flood style DoS attacks.
Bandwidth Allocation (in %)
HTTP and HTTPS [10,20,30,40,50,60,70,80] [Hard Limit, Soft Limit]
Mail (POP & SMTP) [10,20,30,40,50,60,70,80] [Hard Limit, Soft Limit]
FTP File Transfers [10,20,30,40,50,60,70,80] [Hard Limit, Soft Limit]
SSH Administration [10,20,30,40,50,60,70,80] [Hard Limit, Soft Limit]
Game Servers [10,20,30,40,50,60,70,80] [Hard Limit, Soft Limit]
NAT Communications [10,20,30,40,50,60,70,80] [Hard Limit, Soft Limit]
(masqueraded connections above port 1024)
The page then calculates the Hard and Soft Bandwidth limits to give you an idea of how much traffic each should do. I've got a friend working on a horizontal compound bar graph showing these limits.
The main problems are:-
Other networks (eg 192.168.1.*)
Other inbound traffic speeds
Time
Flexibility further down the track such as other protocols or server daemons
Other e-smith official and contrib ipmasq RPMs toes
Time
Coding for good perl
Time
Regards,
Craig Foster