This tftp server won't listen to broadcasts!

I was attempting to downgrade/upgrade code on an access point to change it from CAPWAP to Autonomous, or back again and ran into a headache on the Mac.

Seems like everything I need to do with this Mac is complicated. I've been using TFTPD32 by Jounin for seemingly forever, and I've never had an issue with it not working. The problem is, it doesn't work on a Mac.

I know, I know - you're saying just dive into the Unix command line and check the permissions on my tftpd.plist file, right?

@JenniferLucille try these instructions pastebin.com/PCjFTa95
— Sevan Janiyan (@sevanjaniyan) July 15, 2012

Well, I did that and it still didn't work. I'm using a known good IOS file - one I just used to perform the same task on a Windows 7 machine and it worked as it should. When I try to use the same file on the Mac with the TftpServer app by Fabrizio La Rosa / found via @Etherealmind, the access point tells me the file ended unexpectedly & that it isn't a valid IOS image.

Looks like @santinorizzo hit it on the head again with this:

@JenniferLucille @packetslave Cisco APs try to connect to the broadcast address for tftp. Your server needs to be set to listen for it.
— Santino Rizzo (@santinorizzo) July 15, 2012

@JenniferLucille @packetslave The switch to set the listen address would go in the Program Args, but no switch exists for tftpd in OS X.
— Santino Rizzo (@santinorizzo) July 15, 2012

@Sevanjaniyan was helpful in assisting me with creating the /private/tftpboot folder:

@JenniferLucille pastebin.com/BSkCNf4L
— Sevan Janiyan (@sevanjaniyan) July 15, 2012

It seems that if I'm going to be able to convert access points back and forth between autonomous and lightweight code, I need parallels, bootcamp or a native Win7 client.