db.osoal.org.nz

Subscribe to this feed

Naughty

Tuesday, 10th September 2013

Google have suspended my Adsense account for 'Copyright Infringement'.

I was pretty surprised about that initially considering I've written all the code here in perl, bashed away at the HTML, javascript and CSS by hand, done all the images in gimp and I'm sure no one would want to try and take credit for my ramblings.

My guess after doing some more research on it is that they suddenly took offence to a link in the bookmarks section ( that had been there for the last four years at least ) to a torrent site which I won't name, but has links to obtain television in an easy manner. Pretty amazing to think that could qualify as copyright infringement.

I don't really care if they reinstate the ads or not, they kind of lower the tone a bit and mess up the page layout.

Two posts in two days

Tuesday, 10th September 2013

If you implement code to add posts to the database then its a whole lot easier to post stuff. Strange but true. Perhaps I should have put more effort into implementing that than implementing editing pages and there could have been updates for the last five years or so.

Also, I've changed all the URL's in the html for this site and in the database to use https and put in a permanent redirect so everyone should get here via https now. I did this for www.osoal.org.nz a while back and it seems to have worked okay.

New PGP key

Monday, 9th September 2013

I've got a new PGP key as of Sunday, the old one was expired and had been so many different places it probably should have been revoked anyway.

It's hard to tell if PGP is even any good against well funded organisations anyway, but here's hoping.

Text overload

Saturday, 8th March 2008

I've spent the last couple of hours converting my old text .plan posts into a suitable format for importing into the new database. I had no idea there were so many posts from back in the 1997-98 range. It looks like in my old age I write more crap per post and post less frequently than I used to.

I still have to hack something together to pull posts out of the database and dump them back to the old .plan format periodically.

There is so many posts now in the blog channel that I'm going to have to implement some sort of paging for the html views or maybe just view the last n posts or something as a stop gap measure.

I also did this nice looking login page before deciding to do the authentication on the site with client side certificates anyway, the login page is still there right now though because I don't have the heart to delete it, it's all pretty =)

First life?

Monday, 16th July 2007

If you have mucked about a little in second life, sat around with a bunch of people in some place and talked and pulled mad dance moves etc and then got bored, search around for one of the sandboxes scattered around the place.

Rather than just being a place where people not willing to commit to owning land can have a go at building stuff, you get all sorts turning out trying every crazy thing they can think of.

A typical sandbox includes a giant glass head, a couple of half attempts at wooden cottages, a rideable motor-penis, an absolutely huge klingon bird of prey, a fountain of bouncing mario bros and a single seater space ship making 'launch preperation' notification anouncements in a utilitarian female voice.

In practice, even with all that sort of fun going on I got a bit bored at one point and was about to fly off when I noticed a little block off in the sky. It turned out to be a big four poster bed way the hell up in the sky. I sat on it for a bit and watched the chaos going on down below as someone had written a script which took the bouncing mario image and caused them to explode out of control all over the sandbox, something like a hundred thousand of them.

As I was sitting there a witch complete with green face, flowing robes and pointy hat drove past in a flying delorean that looked suspiciously like the one in the back to the future movies.

Much more fun than sitting around scripting dance moves.

Secret

Friday, 8th June 2007

2 tblspn paprika
1 tblspn onion salt
1 tspn celery salt
1 tspn rubbed sage
1 tspn garlic powder
1 tspn ground allspice
1 tspn ground oregano
1 tspn chili powder
1 tspn black pepper
1 tspn crushed basil leaves
1 tspn finely crushed marjoram leaves

Combine and mix with a few cups of flour, dip chicken into beaten egg, coat with mixture and deep fry.

Domestic depeering

Wednesday, 30th March 2005


http://list.waikato.ac.nz/pipermail/nznog/2005-April/009978.html

About the second point that the Telstra representative makes in this interview is that Telstra has not withdrawn from the peering exchanges.

I have a different view.

As best I can tell I am the first person from Wellington to fill out the 'application form' to establish paid peering with Telstra over Citylink in Wellington. The RFS date ( The date they clai
m service will be established ) came and went, and eventually after much harrasment they have come back to us with a fairly straight up and honest explaination for why they had not put up a BGP s
ession with us.

An excerpt from the explanation we recieved:

"Citylink is a shared network, which means that we don't see individual
customers, but an aggregate of customers. If we try and rate-limit one
customer, we end up rate-limiting all customers. There are various technical
solutions we're looking into that might fix this situation, but for the time
being we're stuck with being unable to rate-limit the tail circuit."

The end result is that they will not put up a peering session with us over Citylink until they can rate limit it to the bandwidth we are prepared to pay for. I see that the Telstra representative
in this interview was careful not to point out that ( at the time of this interview ) they had not established a single peering session across Citylink in Wellington, nor had they even put any t
hought to how they might do it if anyone did ask.

Before Telstra de-peered at WIX the traffic used to cross from our network directly to Telstra across Citylink, about 4 hops all up and with a nice 10-15ms latency. We would save money by not hav
ing to transit the traffic to Auckland and Telstra would save money by not having to pay to transit the traffic from Auckland to Wellington.

Heres a practical example of a traceroute between two _Telstra_ cable modems, physically about 0.5km apart in Lower Hutt. One cable modem is routed by us, and the other end routed by Telstra.

[ ~ ]$ traceroute 203.79.83.200
traceroute to 203.79.83.200 (203.79.83.200), 30 hops max, 38 byte packets
1 gw.cable4.linuxnet.co.nz (202.21.136.33) 12.628 ms 17.647 ms 19.260 ms
2 v4core0.citylink.linuxnet.co.nz (202.21.136.193) 16.447 ms 9.375 ms 12.979 ms
3 203-118-147-1.ihug.net (203.118.147.1) 14.158 ms 13.311 ms 13.116 ms
4 203-118-147-249.ihug.net (203.118.147.249) 34.679 ms 28.716 ms 27.988 ms
5 203-109-156-225.ihug.net (203.109.156.225) 21.921 ms 20.597 ms 23.141 ms
6 g1-0-1642.u12.telstraclear.net (203.98.18.161) 27.055 ms 25.553 ms 24.340 ms
7 g1-0-1043.u12.brh.telstraclear.net (203.98.23.17) 21.601 ms 23.277 ms 29.583 ms
8 10.65.32.1 (10.65.32.1) 23.285 ms 22.639 ms 23.568 ms
9 10.65.32.250 (10.65.32.250) 30.656 ms 32.414 ms 37.072 ms
10 10.69.0.2 (10.69.0.2) 34.500 ms 29.589 ms 37.861 ms
11 a12-3-23.u21.tar.telstraclear.net (203.98.23.34) 33.659 ms 36.030 ms 46.302 ms
12 fa7-4-1042.bertha.tce.telstraclear.net (203.98.23.42) 35.320 ms 34.269 ms 34.117 ms
13 203-79-83-200.cable.paradise.net.nz (203.79.83.200) 58.400 ms 46.904 ms 53.262 ms

We pay for the traffic to go to auckland to where our domestic transit provider peers with Telstra and then Telstra pays for the traffic to come back to Wellington for it to be routed to our cust
omer.

It is very frustrating to see stupid political games by telephone companies impacting on operational matters.

Random IPv6 address assignments

Monday, 28th March 2005


I happened to be logged into a little router that is connected to a wireless network that we run in Lower Hutt today and noticed that the wireless facing interface on it had been assigned ( autoc
onfigured ) an ipv6 address:

inet6 addr: 2002:9f63:7204:4:250:fcff:fee3:4e2a/64 Scope:Global

Well thats odd I thought, I hadn't got around to adding ipv6 connectivity to that particular network, and in any case the address was in 2002 space. Dusting off the cobwebs in my head, 2002::/16
is allocated for 6to4 prefixes, which is space allocated to anyone with an ipv4 address to tack on 2002 at the beginning, their ipv4 address in hex in the middle, and the remaining 80 bits are t
heirs to use however they wish ( 65535 /64's if they so desire ).

As the box was set to use ipv6 autoconfiguration, pretty much anyone with a wireless adapter and a smallish antenna could connect and start making their subnet broadcasts, so the only interesting
bit was who on earth would expend time and effort to assign addresses to random people.

As this was a 6to4 address, you can work out the original ipv4 prefix by converting the 32 bits after the 2002: into decimal and putting it back into a dotted quad:

2002:9f63:7204:4:250:fcff:fee3:4e2a/64 gives us:

9f63:7204 so the following results:

9f = 159
63 = 99
72 = 114
04 = 4

So the original ipv4 address was 159.99.114.4.

Looking this up in the arin whois database gives us:

OrgName: Honeywell Ltd Australia
OrgID: HLA
Address: 2801 4th Ave So
City: Minneapolis
StateProv: MN
PostalCode: 55408
Country: US

NetRange: 159.99.0.0 - 159.99.255.255
CIDR: 159.99.0.0/16
NetName: HLA
NetHandle: NET-159-99-0-0-1
Parent: NET-159-0-0-0-0
NetType: Direct Assignment
NameServer: FISHERY.HONEYWELL.COM
NameServer: DNS3.HONEYWELL.COM
Comment:
RegDate: 1992-03-31
Updated: 1999-10-14

TechHandle: ZH1-ARIN
TechName: Honeywell Inc.
TechPhone: +1-612-951-1707
TechEmail: WCieslik@honeywell.com.au

This network still appears to be originated by AS1221 and in use by honeywell, so what are these guys doing connecting to random wireless networks around the place?

Previous Next

© 2009 Lincoln Reid <lincoln@osoal.org.nz>