Posts RSS Comments RSS 133 Posts and 25 Comments till now

Blog Archives

TekHelp training, day 1

Free food in the dining halls is always nice. The first night of TekHelp training went well. Nick and Luke did a nice overview of the registration process. I think the TekHelps understand our reasoning for all the registration requirements, and the benifits they will provide.


Nick talking in front of the projector screen
Nick and Luke explaining the registration process and proxy settings


Nick talking in front of the projector screen
A bunch of the staff sat in the corner of the room hacking away on various things on our laptops

The staff seems to be surviving the ordeal of training fairly well.


Nick talking in front of the projector screen
Michael (my gunn) and Lawrence snapping photos

All this week we have been working like crazy to get the filters ready. Thanks to the swifty support of telecom we have make excellent progress. The filters are running in Bond Hall, with live management IPs. Mr. Router Man is ready to give us the live IP addresses that the filters will need for production. We are going to make a try at getting them in the networking loop this weekend. Nick and I had a very nice experience testing the filters on Thursday. After they were installed we were able to send data through them on the test network. You get a very odd feeling when you are plugging your laptop directly into ports on a brand new Cisco router. Redundancy seems to work nicely, but we were experiencing up to 3 second delays for the failover to happen. Reading the ifconfig man page specifies that the default timing for CARP notifications is 1 second. The algorithm for detecting a failure of the master interface is 3 times the advbase + advskew settings. So 3 seconds would make sense. I’m pretty sure we can tune the notifications to be quicker.

Last minute hacking

Just managed to get SLUICE actually working. I converted all of it’s weird internal database handling into low-level perl DBI calls. Messy, but it works. So we will have working limitation graphs soon. Also, SLUICE doesn’t limit servers again.

We found out today what the bandwidth will be for the 2004-2005 school year. I guess it’s still supposed to be a surprise, at least until we verify that the link is working at that speed. This little detail we learned today is basically the icing on the cake. After preparing all the server and networks tricks we can to minimize viruses and other “junk traffic” we now find out that we will have a comfortable amount of bandwidth.

This should be a great year for Internet in the residence halls. I can’t wait to sit back and watch all of our tools beat the network traffic into submission.

cvs commits from today

Did quite a lot of real, actual work today. I coded for most of the day again. The backend to the registration process is getting more robust. I have made changes to the DB structure and the various shared classes that operate on them. Should be more efficient, and cause less anomalies.

This finally solves the race condition when the next available IP in a subnet is picked. There is a brief period before the IP is actually recorded as registered, and other students could grab the same IP to register. The new holding table method insures that only one IP is picked and registered at the same time.


1.4 +5 -3 styx/frontend/admin/links.php
- condense something
1.5 +1 -1 styx/frontend/admin/links.php
- fix that one time that I totally <BAD WORD> up quotes in PHP
1.10 +7 -1 shared/restek.css
- CSS for form in sidebar
1.11 +5 -1 shared/restek.css
- OMG style the form more
1.6 +6 -0 styx/frontend/admin/index.php
- add in box for getting an IPs graph
1.13 +2 -1 styx/frontend/admin/graph.php
- fix infinite loop when there is no data in the DB for that time period
1.1 +11 -0 sluice/log.php (new)
- add a php script to ACTUALLY <BAD WORD> MADE THE STUPID DB INSERT.
1.91 +1 -3 shared/sluice/Sluice.pm
- instead of making a simple SQL insert, call a different script, in a different programming language to make the SQL insert.
1.4 +12 -9 styx/frontend/admin/sluice/config.php
- use db clas s
1.2 +0 -11 sluice/log.php (dead)
- move file
1.1 +11 -0 sluice/cronscripts/log.php (new)
- move file
1.29 +5 -5 shared/styx/limitHistory.php
- use seperate config db handle
1.10 +1 -1 styx/frontend/admin/sluice/graph.php
1.39 +3 -2 styx/frontend/admin/sluice/numLimited.php
- fix, by using seperate config db handles
1.9 +2 -2 CVSROOT/cfg_local.pm
1.8 +2 -1 CVSROOT/rcstemplate
- don't show tasktrack stuff
1.68 +75 -0 shared/Ipreg.php
- new holding code
1.28 +2 -31 ipreg/hallserver/frontend/register.php
- OMG redo pick IPs. We are now awesome.
1.69 +2 -9 shared/Ipreg.php
- correct type detection in register();
1.70 +1 -1 shared/Ipreg.php
- )) is not a line ending ); is
1.18 +5 -0 shared/RegException.php
- add dummy getPidnum function
1.19 +1 -1 shared/RegException.php
- exceptions are pidnum 1
1.71 +1 -1 shared/Ipreg.php
- setName(), not checkName()
1.72 +18 -1 shared/Ipreg.php
- use correct type names
1.27 +17 -10 ipreg/cronscripts/makeDhcpConfig.php
- perform holding
- sort by ip
- don't check for blank mac address
1.30 +1 -1 ipreg/hallserver/frontend/register.php
- fix Student registering

Filter setup plan

Here is the basic layout that will run our connection in the fall. Could be good to show at staff training.

Diagram of ResTek network connection

On the left side of the firewalls is one subnet, 10.4.0.0/24. On the right side is another, 10.5.0.0/24. These will be real live IPs when we are in bond hall. The routers serve as a gateway on each end. Each firewall has an IP on each of the 2 subnets here. So firewall A has an interface with the IP 10.4.0.17 and one with 10.5.0.17. These IP’s don’t serve much purpose. Then each firewall is configured with the virtual IP of the gateway for each subnet. The gateway of the 10.4.0.0/24 network is 10.4.0.12, etc. The firewalls decide who will act as the master for the gateway IP using the CARP protocol from OpenBSD. This page has good examples of the power of CARP.

Quick hacking

Felt like doing some quick hacking on my first day back:

  • Added a tooltip to the mac address field in ipadmin that displays the Manufacturer of the NIC card - for nick
  • You can click on a students graph in styx to zoom in on that height of the graph - for nick
  • I made the cookie for remembering bytes or bits persist past a browser session - for luke
  • upgrading servers
  • tweaking tenshi settings to hide more useless messages

New Styx Interface

I started on a new interface to styx, and it’s looking pretty good.

styx screenshot

It has the ability to pick the time ranges to rank students in. It’s also pretty. I added a new column that shows the highest rate they transfered at in one 5 min period. Still needs a little work, but I’m pretty happy with it. Once all the only styx features are in place I’ll make this live.

« Prev - Next »