Have a read of this and you can see why a), one should seek permission, b) hard-coding is a (really) bad idea. If you have any Dlink products mentioned you might take some time to change the defaults.

I was waiting for a Linux kernel to compile the other day, so I was attempting to use the time to clear out my inbox, when i came across an email on the amsat-bb mailing list. It was from g7iii announcing aprstlm.

A telemetry viewer for APRS telemetry capable satellites. aprstlm connects to an APRS server, and monitors the APRS stream for telemetry packets from the appropriate satellite. It can also (optionally) connect to a predict server, to retrieve details about the satellite, such as longitude, latitude, range, orbit number, and eclipse.

I was interested, as I’ve never really had the time to write one myself (and I’m supplying telemetry data for PCSAT2), so I downloaded the source and had a look. It compiled and ran first time, and, as I’m working in the general area, I fired off an email to Iain asking if he had any interest in adding Ipv6 support.

Shortly thereafter my compile finished, I rebooted and had to go again ( I forgot to include the IDE subsystem). As it was a slow machine I decided to have a go at adding IPv6 support myself.

As it turns out, it wasn’t that difficult. As aprstlm is only new, it was pretty much a clear cut case of following the examples given in this howto. Hopefully he will include my patch in the next release.

That then got me thinking again, why is there still code been written today to support Ipv4 only?

I’ve been working on the MII 10K for a few different things recently, over the course of the last few days I’ve been trying to get the Dlink DWL-AG530 and then the DWL-G650 working with this motherboard.

I tried the PCI card first, thinking it would be the most straight forward, when I went to load the madwifi driver to get my (USA purchased) AG 530 I got the following error message:

ath0: unable to collect channel list from hal
ath0: possible regdomain 18 countrycode 0

Bummer, anyways, after a bit of Googling I came across this post. It didn’t work (yet!), so back to Google to find this post, and it worked like a charm, kudos guys.

That left me with the DWL-G650. After putting the card in and rebooting I got

PCI: Failed to allocate mem resource

More googling came up with this post, which worked like a charm. This solution is now summarised in here. If I get time next week I’ll investigate it a bit further.

Hopefully that information may be of use to someone and save them some time. Now that these cards are working, I can begin…

Here is an interesting article from the BBC site about fake Access Points.

Something similiar on Wi-Fi Networking News

“People using wireless high-speed net (wi-fi) are being warned about fake hotspots, or access points.

The latest threat, nicknamed evil twins, pose as real hotspots but are actually unauthorised base stations, say Cranfield University experts.”

It is very interesting to me as this is precisely what I’m trying to do at the moment on the SEINIT project where I work. I’m currently trying to put together a wireless linux distribution and the plan is to add Intrusion Detection (IDS) functionality. Part of that functionality would be to assume the Identity of Access Points that are being attacked in order to ‘lure’ an attacker into attaching to the ‘fake’ access point. Unfortunately I’m still fighting with a CF to IDE adapter :(.

Kathy Ivens posted this article along these lines on the O’Reilly Network. She gives some simple solutions to her ‘Top 5’ Network problems with Microsoft Windows machines. I’m still not sure if she is being funny or not. Either way its worth a read.

I got this link from Slashdot. To summarise “….But the risks are real enough that responsible engineers should take note: This is not merely an academic threat, systems designed with MD5 now need to take far more care than they would if they were employing an unbroken hashing algorithm, and the problems are only going to get worse.”

Here is the source site. Some good stuff on here. I particularly like using DNS for one-to-many streaming data dissemination, in fact the whole ‘DNS tunneling’ area is very interesting, well worth coming back to I think.

I’m in Brussels for the Global IPv6 Launch on behalf of the TSSG. Yesterday I attended the IPv6 Cluster meeting. I though the following observations as to Barriers for IPv6 deployment most interesting.
Continue reading IPv6 In Europe →