throttled for Mac0.5.2

I have used versions prior to the 0.5 release and had a dismal outcome. I installed the program not long after I bought my first mac and was flummoxed as to why my LAN speeds were pitifully slow. Some 12 months or more later I had an epiphany - could it be that Throttled was stymieing my LAN speeds and not just WAN as was intended? Removing this program made me a very happy LAN person. I am not sure if this program helped me shoot myself in the foot or it is just plain evil. The former is more likely, but I am still perplexed.

This is a great product, an absolute must for those who want to run a Mac OS X server on a limited internet pipe. But if you don't like spending a day or more troubleshooting the program to try and get it to work this isn't for you...this wouldn't have been a problem if the support actually existed. There is NO support, I emailed them during business hours and got no reply. When I paid for the pro version of throttled I didn't even get my serial # until I did a whois on their domain and called them...if you rely on support then you may find it worth your time to avoid this product and all products this company makes as there is NO SUPPORT! But other then that this product is great, just takes some time getting used to how it works. TIP: If you have something like a FTP server which consumes a huge amount of ports like I did and which results in the throttled port being in use you will not be able to use the gui. Instead you will have to download the command prompt version, create the ipfw rules yourself and then start the throttled process yourself. It's not that hard if you don't mind reading the documentation and startup script for info on how to do both... But again there is no support and since they seem to promise support this is a big no no to me...is anyone there?!

Besides the related problem with audio/video chatting with iChat (not 100% sure as I didn't test it again after uninstalling Throttled) , I could not start the OS X built-in firewall.

Since OSX does not allow QoS via kernel i.e. mark packages and priorise & queue them, this is the way to go. Of course, it is mostly a matter of settings... Lately, I switched to a self compiled linux gateway with fully qos and it's unbeaten so far, i.e. skyping while upload is totally full is possible.

I would love it if this program worked better, it would be great for P2P. However I have found it makes it impossible to make voice chats in iChat. I have been trying repeatedly with another mac user on broadband. Everything else was setup correctly, (UPnP, port forwarding etc) but it always failed saying insufficient bandwidth. As soon as I removed throttled it worked fine. Will

Does anyone know if there is an application that can prioritise bandwidth to specified apps, in an order of importance. Acquisition seems to slow down my surfin' experience quite a bit. What I mean is e.g. me giving Acquisition 80% of bandwidth above other internet apps like Entourage or ICQ, but prioritise Netscape with 90% above Aquisition and the rest if I'm downloading a page. So I should be able to move the internet apps up and down in a list and assign a % of bandwidth to each app, which it will use when no other app above is using bandwidth. Am I making any sence ? Big question is, is it possible ? If so it might proove a challenge to all ya programmers out there! Who's up for it ? Björn ;-) PS: if you need me to explain by more graphic means, mail me at bxlbjorn@yahoo.co.uk

throttled does *not* work when apple's firewall is active. however, there is a way to make it work with BrickHouse (which - like the apple firewall GUI - also uses ipfw, the firewall built into Mac OS X). one has to edit /etc/firewall.conf and add all the ipfw rules that normally are in the throttled-startup file right at the beginning of it. one has to rename the rule numbers, so that throttled's rules come before ipfw's rules. as an example, here's how my /etc/firewall.conf looks like: # Firewall Boot Script # Generated by BrickHouse ################################################# # BEGIN throttled ipfw rules, added by boli ################################################# # prioritize http/https add 500 divert 17778 tcp from any to any 80 out xmit en0 add 501 divert 17778 tcp from any to any 443 out xmit en0 # prioritize ssh and telnet add 502 divert 17778 tcp from any to any 22 out xmit en0 add 503 divert 17778 tcp from any to any 23 out xmit en0 # prioritize imap and smtp add 504 divert 17778 tcp from any to any 143 out xmit en0 add 505 divert 17778 tcp from any to any 25 out xmit en0 # prioritize ftp directory listings add 506 divert 17778 tcp from any to any 21 out xmit en0 # prioritize aim or iChat add 507 divert 17778 tcp from any to any 5190 out xmit en0 # prioritize msn # add 508 divert 17778 tcp from any to any 1863 out xmit en0 # prioritize pop3 add 509 divert 17778 tcp from any to any 110 out xmit en0 # prioritize irc and sirc add 510 divert 17778 tcp from any to any 6667 out xmit en0 add 511 divert 17778 tcp from any to any 6668 out xmit en0 add 512 divert 17778 tcp from any to any 9999 out xmit en0 # prioritize hotline and carracho "listing" ports (client end) add 513 divert 17778 tcp from any to any 5500 out xmit en0 add 514 divert 17778 tcp from any to any 6700 out xmit en0 # prioritize hotline and carracho "listing" ports (server end) # add 515 divert 17778 tcp from any 5500 to any out xmit en0 # add 516 divert 17778 tcp from any 6700 to any out xmit en0 # bind to throttle low priority services. add 517 divert 17777 tcp from any to any out xmit en0 ################################################# # END throttled ipfw rules, added by boli ################################################# ################################################# # Allow Loopback ################################################# add 1000 allow ip from any to any via lo0 ################################################# # Allow packets from existing connections ################################################# add 1002 allow tcp from any to any established add 1003 allow all from any to any frag ################################################# # Allow Essential ICMP Traffic ################################################# add 1004 allow icmp from any to any icmptype 3,4,11,12 ################################################# ## Rules for the en0 interface ################################################# ... more of the original firewall.conf follows, but that should be already there and of course depends on the settings you've made in BrickHouse. i also commented out (added # in front of it) the above rules in the throttled-startup file, so these rules won't be added twice. thanks for all this information go to the very responsive developer! i just thought i'd share it here. :D

Very nice. I was looking for a tool to do exactly this. It let's you control the upstream bandwidth. Not for those afraid of the command line however. But, once you dive in you'll see how powerful this tool can really be. Great if you are interested in setting up QoS on your OSX box.

I THINK I found a way to cap downloads in throttled (if you're interested) that actually works! In the throttled-startup configuration, instead of using allow to process your packets, designate a skipto # instead for all approved packets to be 'throttled' and approved through 1 inbound local port. For example: # Localhost $IPFW add 100 allow ip from any to any via lo0 $IPFW add 101 deny ip from 127.0.0.0/8 to any $IPFW add 101 deny ip from any to 127.0.0.0/8 # Internet $IPFW add 2000 skipto 65000 tcp from any to any via any # Otherwise, no access $IPFW add 64000 deny ip from any to any # Divert $IPFW add 65000 divert 17777 ip from any to any via any (add another rule here to allow all passing traffic if you need to, you don't have to in Mac OS X) I THINK this is sound, it's definately having an effect on my downloads when I apply it to everything to emulate a slower connection, and CNET Bandwidth tester confirms my settings. Can anyone confirm that this style works?

This is far far better than Carafix. Is is much more powerful, and in fact is no less than a replacement for the missing 'Dummynet' functionality of most BSD kernels. Just stick this in and add some divert rules to ipfw (as you would with dummynet) and you have a decent as QoS system as you are going to find for OS X at the mo. Does the job very well once you understand how to configure. Search on OS X hints or mail the (very responsive) developer for more info.