Further negotiations with Caida have been carried out to allow the running of the traces with maximum packets per trace at a higher rate, 300 pps.

The Internet simulator was modified and is running. Some effort has been put into finding out how to make small runs quicker by using more cores.

The files for the Caida nodes have been prepared including the different files necessary for analysing with a maximum number of probes or the reduced limit. Two nodes with the former will be used and twentythree with the latter.

This week I've re-writing the code so I can start to optimise it. Mainly converting the use of a mix of 1D and 2D arrays to just using 1D arrays. It took a while to fix all the bugs this caused. I've also started writing my report.

Spent the week working on graphs for the AMP web interface. Added
colouring based on loss to the smokeping graphs and made sure that the
y-axis is always long enough to accommodate the smokey peaks rather than
following the median line.

Started to work on an event graph type that can be added to any of the
existing time series graphs. It currently draws hardcoded events as
vertical bars on the graph with mouse highlighting and tooltips describing
the event. Spoke to Shane about the event API and started to implement the
code to fetch events dynamically based on the graph.

What happened this week:

• Spent a large chunk of the week working with Shane and Brendon to clean up some of our Wand projects (BSOD, AMP) to show off to potential students at open day. Ran into some pretty funky bugs in BSOD that Shane spent time fixing.

• Met with a student who wants to do some work experience in the Computer Science department in July. Potentially going to spend some days with Wand, so if you have any fun projects for them to work on to get them excited about Computer Science flick me a message.

• Met with our Dell pre-sales guy to work out what Dell solutions we can use to build some new hardware for AMP / ISP capture boxes. Going over what was discussed and getting some invoices generated next week to see how much they cost.

• Finally, Friday was our annual Open Day. We manned the stall in S-block most of the day trying to generate interest by showing off Wand projects. Talked to many potential (and current) students.

Spent much of my week working on getting BSOD ready to be wheeled out at Open Day once again. During this process, I managed to find and fix a couple of bugs in the server that were now causing nasty crashes. I also tracked down a bug in the client where the UI elements aren't redrawn properly if the window is resized. Normally this hasn't been a big problem, but newer versions of Gnome like to try and silently resize full-screen apps and this meant that our UI was disappearing off the bottom of the screen. As an interim fix, I've disabled resizing in BSOD client but we really should be trying to handle resize events properly.

Received a bug report for libtrace about the compression detection occasionally giving a false positive for uncompressed ERF traces. This is because the ERF header has no identifying 'magic' at the start, so every now and again the first few bytes (where the timestamp is stored) end up matching the bytes we use to identify a gzip header. I've strengthened the gzip check to use an extra byte so the chance of this happening now is 1 in 16 million. I've also added a special URI format called rawerf: so users can force libtrace to treat traces as uncompressed ERF.

Started working on trying to get amp-web to plot graphs of interface byte counts. I've managed to draw a line on the graph, but much of the graph styling is still using the smokeping style. I'm now looking at rewriting the javascript for the graph styling to be a bit more generic and configurable, rather than having one (mostly copied) javascript file for each of our metrics.

Friday was mostly consumed with looking after our displays at Open Day. BSOD continued to impress quite a few people and we were reasonably busy most of the day, so it seemed a worthwhile exercise.

AMP's new throughput test is now reporting Web10G variables. Added options to disable TCP nagle, change TCP MSS and control socket buffer sizes. Briefly started testing seems to be reporting similar results to iperf, hoping to try this out on the 10Gig network next week to make sure it can keep up.

Troubleshooted a bit more and solved firewall and time synching problems between the compute and controller node. Started working on the interim report for this project.

Worked on my in class presentation for this project this week as well as starting my Interim report.

I started testing the path learning, which took a bit of effort, changing the test network to be a non full mesh, and adding scripts to bring switches down and back up again when I need to. So most of the week was spent debugging this.

I also did my in-class presentation, which went fine..

A modified analysis was created for the Internet Simulator. This used existing available factor levels in a modified pattern. This was done to confirm the function of the simulator. It was noticed that the simulator generates some error messages in its native state and it would be useful to find out if these are important or what can be done them. The simulation is still running, and I note that with the smaller number of simulations that only one core on Wraith is being used.

The set up procedure with Caida is progressing and we should be probing soon.