micolous.id.au

the result of a blogging accident

Saturday, January 23, 2010

Linux iSCSI COW Images, and Windows integration.

Filed under: Coding, Computers, Lanning — micolous @ 20:08

More stuff for RetroLAN PCs, yay!

I’ve now got all the RetroLAN PCs running out of a copy-on-write image. This means I now have a single 4GB “base” image with an installation of Windows XP, instead of having 10 of them. It also means it is very trivial to reset the machine’s disk images, which I achieved with a bit of scripting.

First up, I needed to setup the copy-on-write images through device-mapper. This program is designed to let you setup software RAID, but it also allows snapshotting disks to provide a backup of a device at a point in time. Unfortunately, dmsetup doesn’t support accessing file images, only actual devices, so I need to create some loopback devices first.

1
2
3
4
# setup loop0 as the "master" image, and mark it as read-only so no changes ever get written back.
losetup -r /dev/loop0 /store/master.img
# we need to get the size of the image in sectors for use later on.
cow_size=`blockdev --getsize /dev/loop0`

The next step is to create a blank image file and loopback device to commit changes to. For my setup, I created 200MB images. Be aware of things like disk-based caches and automatic defragmentation will use up the allocated space very quickly, and when you run out of space in this file further writes will not be allowed, and Windows will soon crash with a blue screen of death. (More on dealing with this in a bit)

1
2
3
4
5
6
7
8
# remove any existing COW image
rm /store/pc-1.cow
 
# create a new 200MB image (it's actually comes out 5% more than stated, but it allows for overheads in the filesystem)
dd if=/dev/zero of=/store/pc-1.cow bs=1M count=200
 
# now hook it to a loopback device
losetup /dev/loop1 /store/pc-1.cow

Now we have two devices, /dev/loop0 which contains the master image, and /dev/loop1 which will contain any changes made to the disk. The next step is to use dmsetup to create a device mapper which will layer the COW image ontop of the original image.

1
2
# create the cow!
echo "0 ${cow_size} snapshot /dev/loop0 /dev/loop1 p 64" | dmsetup create pc1

This will create a device called /dev/mapper/pc1. You can use it in your iSCSI setup with something like this in your /etc/ietd.conf:

1
2
Target iqn.2010-01.lan.someplace.iscsihost:pc1
        Lun 0 Path=/dev/mapper/pc1,Type=fileio

You can then start ietd.

Now the next part is writing a script to let you reset the COW images. ietd does not like you changing things while it is running, so you’ll need to make sure your script suspends all disk activity before blanking out the COW image. Something like this:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
# disconnect the COW image #1
ietadm --op delete --tid 1 --lun 0
 
# suspend dm activity
dmsetup suspend pc1
 
# clear the cow cache
dd if=/dev/zero of=/dev/loop1
 
# reload the cow table
master="/dev/loop0"
cow_size=`blockdev --getsize ${master}`
echo "0 ${cow_size} snapshot ${master} /dev/loop1 p 64" | dmsetup reload pc1
 
# resume dm activity
dmsetup resume pc1
 
# reconnect the COW image #1
ietadm --op new --tid 1 --lun 0 --params Path=/dev/mapper/pc1

You could change this script around so that it allows you to pass in a PC number as a command-line argument, and then hook in a CGI script that will call it to reset it remotely. In my setup, I’m using gPXE to boot from iSCSI, but it can also be used to access a URL via HTTP. So your CGI script reads in the request IP address, and if it is one of the resettable machines, it will reset it’s COW image. Then it sends back a gPXE script instructing it to run a DOS .com file that will reboot the computer. For this to work you need to have your CGI script execute the command as the superuser (root).

One of the things about the COWs is if you reset them or they become full while Windows is running, Windows will very soon crash, and refuse to boot up again. To better inform both yourself and users about the usage levels, you can read the information from dmsetup:

1
2
# dmsetup status pc8
0 8385930 snapshot 55296/409600

In this example, it is indicating that the full image is 8385930 sectors, and 55296 of 409600 sectors are used in the COW image. So I wrote a Python CGI script that reports this in a parsable fashion to clients:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
#!/usr/bin/env python
 
print "Content-Type: text/plain\r\n\r"
 
from os import environ
from subprocess import Popen, PIPE
 
ip = environ['REMOTE_ADDR']
d = int(ip.split(".")[3])
if d >= 41 and d <= 54:
  machine = d - 40
  try:
    p = Popen(('/sbin/dmsetup', 'status', 'retrocow%d' % machine), stdout=PIPE, stderr=PIPE)
    stdout, stderr = p.communicate()
    use, total = stdout.split(' ')[3].split('/')
    use, total = long(use), long(total)
    print "OK %d %d" % (use, total)
  except:
    print "ERR Problem getting parsing information"
else:
  # return error
  print "ERR Not a RetroLAN Machine"

For me, the RetroLAN machines have IPs ending in 41 to 54. That corresponds to their PC number (retro-01 to retro-14). This script outputs the following text file when requested via CGI if successful:

OK 55296 409600

This isn’t very usable for the end user, so I wrote a .NET 2.0 app called CowBell that runs in the system tray showing the percentage of COW usage, and notifies them if they’re over 75% usage (which means they will crash soon). I’ve made source code available for download, which you’ll need to modify frmMain.cs line 37 to include the path to where you put the CGI script, and uncomment the line otherwise it will not compile. If you make modifications to this program I do ask that you share your improvements with me.

This is the message that constantly pops up when you’re over 75% usage:

The application refreshes it’s status every 10 seconds, and if you right-click the icon it shows the COW usage in sectors.

Wednesday, January 20, 2010

Dynamically changing Windows’ wallpaper based on hostname

Filed under: Coding, Computers, Lanning — micolous @ 03:36

I have a situation where I’ve got 14 machines booting Windows XP over iSCSI, and they’ve all got the same computer name set, and they each need to have a different wallpaper set on each machine. This runs the “RetroLAN” machines at StreetGeek in the new setup, to make it much easier to roll out updates to machines. They’re all using the same base image, and this will get restored if things get broken. I’m using gPXE to boot the machines in the first place, and I’ve disabled NetBIOS over TCP/IP (to avoid the problem where Windows complains if two computers have the same name), and manually set the DNS search order (because when you boot Windows over iSCSI, Windows’ own DHCP client doesn’t get activated).

So I hacked together this VBScript that does a reverse DNS lookup on the IP, and uses that to get a specific wallpaper for the machine using a bit of copy-paste from the ‘net. The script requires you use JSWare’s JSSys addin for VBScript, so make sure you have that DLL installed and registered before trying to use my script. There’s a way to do it without JSWare using the registry, but it only applies after logging out and logging in again.

In the code it will try to grab the wallpaper from \logres\wallpapers. You’ll need to change this for your setup. To activate this, I added it to the Startup folder, so about 5 seconds after login, the wallpaper is automatically changed to be for the correct machine.

One minor caveat: Apparently my network card was network card #2, and there was no #1. You can check what ID your card is in HKLM\Software\Microsoft\Windows NT\CurrentVersion\NetworkCards\, and change the line in the script appropriately.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
' Automatically setup wallpaper (autowallpaper.vbs)

Function GetFQDN(ipaddress)
  set sh = createobject("wscript.shell")
  set fso = createobject("scripting.filesystemobject")
  Set Env = sh.Environment("PROCESS")
 
  workfile = fso.gettempname
  sh.run "%comspec% /c nslookup " & ipaddress & "  > " & workfile,0,true
  set sh = nothing
  set ts = fso.opentextfile(workfile)
  data = split(ts.readall,vbcr)
  ts.close
 
  set ts = nothing
  fso.deletefile workfile
  set fso = nothing
  for n = 0 to ubound(data)
    if instr(data(n),"Name") then
      parts = split(data(n),":")
      hostname= trim(cstr(parts(1)))
      Exit For
    end if
    hostname = "could not resolve IP address"
  next
 
  GetFQDN = hostname
End Function
 
Const HKCU = &H80000001
Const HKLM = &H80000002
 
Set objReg = GetObject("winmgmts:\\.\root\default:StdRegProv")
 
' Get NIC service name
objReg.GetStringValue HKLM, "Software\Microsoft\Windows NT\CurrentVersion\NetworkCards\2", "ServiceName", nicService
 
' Get IP address
objReg.GetMultiStringValue HKLM, "System\CurrentControlSet\Services\TCPIP\Parameters\Interfaces\" & nicService, "IPAddress", addrs
 
' Resolve name
fullname = GetFQDN(addrs(0))
shortname = split(fullname, ".")(0)
 
Dim objOps
Set objOps = CreateObject("JSSys3.Ops")
 
r = objOps.SetWallpaper("\\logres\wallpapers\" & shortname & ".bmp", "center")

Tuesday, August 22, 2006

Windows CE 2.0 and OpenSSH

Filed under: Computers, Toys — micolous @ 21:13

I’ve found a good howto on installing OpenSSH on Windows CE 2.0. The only problem with it, is that you require an ActiveSync partnership with the device in order to insert the nessesary registry keys. I’ve found a way to install OpenSSH without needing any ActiveSync partership. I did this on a HP 320LX H/PC (which runs WinCE 2.0 on SH3).

To do this, install Registry Explorer on your device. If you don’t want to boot Windows (or can’t), you can use this copy of the files, which has the CAB files you’ll need to install it to your device. You can then follow the HOWTO, then use Registry Explorer to add in the registry entries. Registry Explorer uses a GUI similar to the standard Win32 Registry Editor.

For convienience, I’ve created a copy of my registry entries, which you can import using the Registry Explorer software. Be aware that I store my UNIX root in \Storage Card\unix, due to limited internal memory. I’ve found that SSH will still try to store it’s known_hosts file in the \unix directory, so you’ll need to create that directory anyway (just leave it empty – don’t copy your UNIX root into it). The space used by the known_hosts file is minimal. My registry dump also uses the default username of “michael”, which you’ll need to change so it matches what you wrote in your /etc/passwd file.

One final thing is that ncurses apps (like irssi) seem to have some problems with the terminal type being set to ‘wince’. I’m presently working on getting a working terminfo file for Linux systems, so that they can properly handle OpenSSH on WinCE.

Wednesday, August 16, 2006

Bridged OpenVPN and DHCP

Filed under: Computers — micolous @ 01:06

I’ve setup a VPN recently, and I created a large bridged VPN. I had a little problem though – the DHCP server from the remote network was leaking through to mine, causing all sorts of troubles, as my network devices were trying to use the remote router, which I had of course blocked VPN access to the Internet.

So, lets take a hypothetical network:

  • eth0: Internet Connection (192.168.0.2)
  • eth1: LAN Connection
  • tap0: VPN Connection
  • br0: Bridge between eth1 and tap0 (10.0.1.1)

Now, your local DHCP server is saying the subnet is 10.0.0.0/8, and it gives out IPs in the range 10.0.1.100 – 10.0.1.200. The remote end (10.0.2.1) gives out 10.0.2.100 – 10.0.2.200, and sets the routing accordingly. I found running the DHCP server on the bridge was a problem, particulary with the ISC DHCP server, as it uses raw sockets, thus making it quite hard to try and firewall out. The solution?

Set an IP for eth1 locally (and remotely), that is in the range, say 10.254.1.254, with the netmask 255.255.255.252. Bind your DHCP server (in /etc/default/dhcp3-server) to eth1. Then restart the DHCP servers, and voila. The DHCP servers only give out addresses locally. To your clients it will appear that 10.254.1.254 is giving out IP addresses.

Monday, October 3, 2005

It’s been a while.

Filed under: Computers, Life — micolous @ 14:37

It has been a while since I last blogged, so I’d better write a long update on what’s happening.

ratemyrackmountedserver.com expired while I was moving. I decided to leave it dead, as this site kinda bellyflopped anyway. So there’s lots of nice broken links out there to my site… I apologise in advance for all that. I was stuck on dialup for about three weeks at my new house. It took a little longer to get DSL provisioned than I had planned. So it’s back to mic.kyed.com for a little while.

iPrimus is the shittyest ISP ever. I like how their prepaid access kits were easy to use, but due to them having nonstandard Windows servers running the dialins, I had to use Windows as a gateway for a while. So I ended up setting up a Windows 2003 box with ICS for a few weeks. That’s now been wiped, and was probably comprimised during that time. Good on them. Also due to having to put a Windows server in the way and iPrimus’ very strict 5 hour session limits, my website was down for a while.

I’m now back up again, as of about two weeks ago. I just haven’t been bothered to write anything :) Now I think I may finally be bothered to get a new domain for myself… maybe. Once I find some spare money.

On the Saturday after my birthday, I had a rather subdued 18th party, due to the fact half of us had the flu. Oh well, good to catch up with some people. Last Saturday I went to LPC with some friends. It was good, though much bigger and slightly more serious than I’m used to. I wasn’t too worried, and we (myself, sherman, Hotsuma, Eecore) managed to trick Thrashbarg into having Windows running on his computer. It was only Windows 95, but Thrashbarg’s earlier zealotry on IRC made it still rather good. He argues that it didn’t count because it wasn’t installed on his hard drive. Oh well :)

Older Posts »

Powered by WordPress