www.daork.net

I’ve been doing lots of teaching IPv6 lately. At an InternetNZ IPv6 training day in Wellington in ‘07, at NZNOG’08 in Dunedin, and also private training for a few companies and things.

I figure the world is better off if I post up slides and things, as opposed to keeping them secret or proprietary or whatever. If you rip them off, make sure you let me know and give credit and all that noise.

• InternetNZ, talking about transition technologies: 20070809-nward-6to4-teredo.pdf
• NZNOG’08, talking about 6to4, Teredo and my Tui project: 20080124-6to4-teredo-tui.pdf

More to come, when I get em uploaded.

I’ve refined my previous idea slightly:
- IMG tags have src set to “” to start with.
- JavaScript thing runs on page load, and starts a timer, and sets src properties for the 3 images.
- A new IMG tag exists. It’s src is set to deliver results back to me.
- When the first imge loads, a timer is kicked off.
- When either the last image loads or the timer fires, the results IMG src is set to send some data to the server, including: ipv4 loadtime, ipv6 loadtime, ipv6and4 loadtime. Where images don’t load, NaN is sent.
- When the timer fires, the src of the various IMGs is optionally set to “”, to stop the test.

I think that’s about it.
I’ve been running this for a few days on my websites. At least one of them isn’t small and has a wide range of users from non-technical to pretty-technical, and a wide range of OSes and browsers.

The code has been published at:
http://www.braintrust.co.nz/ipv6wwwtest/

Enjoy.

So, I’ve decided to write a network element manager, along the same lines as Dorado RMC.

The idea is that it will be an application that will:
- Do config backups
- Deploy config with templates, config snippets, etc.
- Check that current config meets certain rules
- Use interoperable XML/SOAP stuff for as many interfaces as possible, so it can be swapped out.
- CLI and web GUI to start with - adding maybe a GTK+ or Java GUI later on. I’d also like to do a Cocoa GUI for OS X.

And more things, I’m busy at work so it’s hard to think of all the things I have considered recently, but I’ll edit this post as I come up with more key points.

I use my mail server for several things;
- Standard email hosting
- Receiving mail to go off to scripts for processing (ie. bounces from newsletters)
- Forwarding mail for certain mailboxes/domains off to other servers outside my control
- etc.

Previously, I had dspam set up to process mail in the postfix content_filter mode on the smtpd process. This is OK, but it means that I spam filter email that I forward, and I don’t really want that. I don’t really want to have to opt-out every address that I forward to, either. There was a transport configured to process email in dspam, by calling the dspamc binary, and piping the email to it. It would be sent to the dspam server.
The dspam server would process mail, then deliver it back to Postfix via SMTP on a special unfiltered port for delivery via cyrus using the ‘deliver’ binary that ships with cyrus-imapd.

Now I’ve changed things a bit. The virtual_transport and mailbox_transport in Postfix is set to use LMTP to deliver to my dspam LMTP socket. Dspam is configured to process the mail (it selects user based on the ‘To’ in the envelope), and then deliver it with LMTP to cyrus-imapd. The virtual_transport and mailbox_transport parts run after the alias processing, so mail that goes to remote servers goes un-scanned.
I have to wonder whether there’s a performance boost in here somewhere because of the use of LMTP instead of calling the “deliver” and “dspamc” binaries.

Like I say, it’s possible to accomplish this with optIn/optOut settings, but I like having default optIn for my users who actually receive mail on my server.

On NZRave.com, we run SMF 1.0.x and Mambo 4.5.1. Both are patched a bit to get around some nasty attacks.

I recently installed the new Braintrust database server. It’s got 2GB RAM, 2×1GHz P3 chips, and 2×320GB SATA disks in Linux software RAID1, and of course LVM on top. It’s not huge, but is plenty for our purposes for the moment.

I’m running Centos4 on this new box, and figured I’d use the `centosplus’ repository and get MySQL 5, PHP 5, and PostgreSQL 8. However, it turns out SMF doesn’t like MySQL 5 because of some precedence changes in the SQL parser. Balls.

Back to MySQL 4.x for me. That means I’ve got to drop back to PHP 4, and PostgreSQL 7, as the newer Centos packages all depend on one another somewhat.