Tag: JustMigrated

Should anyone ask, traffic prioitization should be done one the edge of your network

I spent some time today experimenting with traffic shaping on ddwrt.  My VOIP calls were still stuttery due to packet congestion.  Although this time I traced the congestion back to my wireless bridge.  Good thing it runs linux and I was able to install the following script.  It simply prioritises packets in and out of my wireless gateway on both the wired and wireless interfaces.  This is nice because people I call will no longer hear a stuttering or voice drop out when there are large file transfers going on.  It simply creates 3 queues  (mobile, laptop, all other) on both interfaces and sets up a simple prio between them.  All classes are guaranteed at least 200kbps (should the wireless connection be really bad and the PHY drop down to 500k. But the beauty of the HTB shaping model is that it will borrow.  So in this case classes (laptop and “all other”) can borrow from “mobile” when they need more “tokens”.  IE the right to transmit a packet.

Did I mention DDWRT was cool?

#eth0 is wired
#eth1 is wireless

#everything heading from wired to wireless
tc qdisc del dev eth1 root
tc qdisc add dev eth1 root handle 2: htb default 30
tc class add dev eth1 parent 2: classid 2:1 htb rate 100mbit
tc class add dev eth1 parent 2:1 classid 2:10 htb rate 100mbit ceil 100mbit prio 1
tc class add dev eth1 parent 2:1 classid 2:20 htb rate 200kbit ceil 100mbit prio 2
tc class add dev eth1 parent 2:1 classid 2:30 htb rate 200kbit ceil 100mbit prio 3
tc qdisc add dev eth1 parent 2:10 handle 10: sfq perturb 10
tc qdisc add dev eth1 parent 2:20 handle 20: sfq perturb 10
tc qdisc add dev eth1 parent 2:30 handle 30: sfq perturb 10
tc filter add dev eth1 parent 2: protocol ip prio 16 u32 match ip dst 10.15.11.8 flowid 2:10 # mobile
tc filter add dev eth1 parent 2: protocol ip prio 16 u32 match ip dst 10.15.11.7 flowid 2:20 # laptop wireless

#everything heading from wireless to wired (we don't one client killing others)
tc qdisc del dev eth0 root
tc qdisc add dev eth0 root handle 3: htb default 30
tc class add dev eth0 parent 3: classid 3:1 htb rate 100mbit
tc class add dev eth0 parent 3:1 classid 3:10 htb rate 100mbit ceil 100mbit prio 1
tc class add dev eth0 parent 3:1 classid 3:20 htb rate 200kbit ceil 100mbit prio 2
tc class add dev eth0 parent 3:1 classid 3:30 htb rate 200kbit ceil 100mbit prio 3
tc qdisc add dev eth0 parent 3:10 handle 10: sfq perturb 10
tc qdisc add dev eth0 parent 3:20 handle 20: sfq perturb 10
tc qdisc add dev eth0 parent 3:30 handle 30: sfq perturb 10
tc filter add dev eth0 parent 3: protocol ip prio 16 u32 match ip src 10.15.11.8 flowid 3:10 # mobile
tc filter add dev eth0 parent 3: protocol ip prio 16 u32 match ip src 10.15.11.7 flowid 3:20 # laptop wireless

# list what we have
tc -s -d qdisc show dev eth0
tc -s -d qdisc show dev eth1

Should anyone ask, I was in Berlin, again.

Returning from Berlin. I have just spent the last 4 days in Berlin. 3 of those with my mother and the last walking around neighbourhoods to find something that I could possibly live in. During that time I have seen 2 great film.

Even though it was the Berlinale, these were ones from my “To be viewed” spool. Most recently I finished watching Luc Besson’s “Angel A”. Wow. I was in Paris last month and this brought back many memories. A large portion of the film takes place on the graceful bridges that span the Seine. The story is about a down and out scamster being put back on his feet by an angel. The fact that this Angel A aka Angela is at least a foot taller than him adds to his depression. The film is shot in black and white with some excellent lighting, particuarly where the main character addresses his deamons (those that that keep beating him up on the street, and to whom he owes much money).

It was Berlinale and I never made it. Although I did make up for the time by meeting Nataša who organises the Croatian equivalent and was here to snag as many films for the next showing in Zagreb. When not talking about films, we exchanged memories of our times on the island of Vis.

Should anyone ask, SQL queries are better than memory queries.

I apologise in advance for the musical snobbery, but its something that’s important to me. The music and less so the snobbery.

I’m listening to a new “micro house” album from an mixer called Nek Sanalet. It’s good stuff. After many years of living away from London I feel that I am finally exiting my musical exile and discovering music that moves me and gets me excited.

Munich’s happy-happy disco excuse for club music has not been good to me and I am now in a “making up for lost time” mode when I use last.fm’s service. The problem with dwelling in the “long tail” of music is one coming across many more artists. Well perhaps not more but certainly one’s not hearing the like of names like Tiefschwartz, Kit Clayton and clubs like Tresor on mainstream radio when driving back from skiing in Austria. So this is why I like services like Last.fm. It’s keeping track of and recommending me names that it thinks I will like. Multiple SQL queries make up for my leaky memory or a reseller’s bad recommendation. Now I actively look forward turning on the application, either as a standalone application or via my Squeezebox. I like it so much I even bought a subscription and for those that know me, this is a big step.

Apart from just playing me cool songs, the application shows me meta data about each song, the artists biography, where they will next be performing/djing etc. It’s the background to the artist that I have found interesting. The average biograpy for each artist reads something like: “Grew up in Bonn, moved to Berlin and now runs record label xyz. Part of the Berlin abc movement. I promise I haven’t put in any play music tagged with "Berlin”, and find this correlation interesting. Ken thinks its a sign and I’m planning a trip there in a couple of weeks to look at some property. Time will tell.