I have a startup script that changes my MAC address for me, but I noticed that after a successful suspend/resume it was changed back. So I did some research and put together a resume script that changes it back. I put in in /etc/pm/sleep.d/99_changemac-suspend. It actually points back to the original script in /etc/init.d that does the MAC change on boot and outputs $1 to a file so I can see that it ran and with what input.

The script runs fine when I execute it manually and I can tell it runs on resume because the output file shows the expected input of "resume", but my MAC is not as it should be. I can only assume that even with a start order of 99 something else is running after it which reinitializes the NIC and loses my custom settings.

What can I do to troubleshoot this issue? Is there a way to force my script to run last?

{edit} I'm using 11.11

Why are you not using udev rules for this?

---------- Post added 05-09-12 at 01:52 PM ----------

http://www.debianhelp.co.uk/udev.htm

I got my hopes up on this, but looking at the rulesets (http://linux.die.net/man/8/udev) I don't see one that allows you to specify a new MAC address the same way you can change the name. The best thing I could find was PROGRAM which allows you to run a program on a match.

So I made a rule like so:
# PCI device 0x8086:0x4222 (iwl3945)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:18:de:5b:6a:91", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan2", PROGRAM=="/etc/init.d/changemac"

But it doesn't have the intended result of changing my mac. Any other ideas?