Archive for February, 2009

Charter caps and DD-WRT ttraff daemon

February 14, 2009

Charter added 100GB monthly caps to <= 15Mbps service (which is us – we have 5000/512 here.) That doesn’t go really well with our apartment’s recent habits..

January 2009 (Incoming: 208027 MB / Outgoing: 65253 MB)
February 5, 2009 (Incoming: 24011 MB / Outgoing: 4334 MB)
February 6, 2009 (Incoming: 25044 MB / Outgoing: 4525 MB)
February 7, 2009 (Incoming: 17455 MB / Outgoing: 4485 MB)
February 8, 2009 (Incoming: 22946 MB / Outgoing: 4223 MB)

The ttraff daemon on our router actually died a couple more times. Our router itself died a couple times because there were too many concurrent connections (things start breaking at about 2000/4096. I usually want to say at <= 1300.) People have odd torrent configuration settings and I want to try to maximize bandwidth use and internet workability. By setting proper incoming ports and QoSing them to bulk (along with the BitTorrent protocol, if even necessary) then all incoming connections (which are [non?]surprisingly most, at least on small torrents) will be dealt with properly. But what about outgoing? They get shaped by the BT protocol rule. But what about encrypted outgoing?

That’s when I forced outgoing to those ports. Then it should be ok for everyone to have nearly uncapped (50 kB/s) usage — management/fair division of the bandwidth should be done at the router level.

But I can’t believe that they broke the router and the daemon. Well.. I don’t like the fact that the daemon dies to begin with.

Advertisements

ln(1) madness

February 6, 2009

My roommate and I always have a hard time with the arguments for this command.
We generally just use it for symbolic links.

ln(1) - make links between files
ln [OPTION]... [-T] TARGET LINK_NAME
Create a link to TARGET with the name LINK_NAME. Create hard links by default, symbolic links with --symbolic. When creating hard links, each TARGET must exist.

The problem is that we learned it when the manpages had it as SOURCE and DESTINATION or something like that. I swear it did. We always got them mixed up because the “source” could be the existing file and the “destination” could be the new link, or vice versa – “source” being the new link and “destination” being the existing file.

Now that I’m writing a blogpost about how I never memorized which one goes first and how I confuse them all the time, I understand it.. yay.