Doesn't look like the devices are laid out the same, so I'm unclear it the same trick works. Don't have an OTA dongle, I have to manually flip it to host mode in Maemo.

Log says:
D/SettingsWifiEnabler( 1261): Received wifi state changed from Disabling to Disabled
I//system/bin/wlan_loader( 1318): stlc45xx calibration tool not present.
I//system/bin/wlan_loader( 1318): Device will operate sub-obtimal.
I//system/bin/wlan_loader( 1318): Download it from: http://stlc45xx.garage.maemo.org/
I//system/bin/wlan_loader( 1318): Then place it at /usr/bin/stlc45xx in the initfs partition.
D/SettingsWifiEnabler( 1261): Received wifi state changed from Disabled to Enabling
V/WifiMonitor( 617): Event [CTRL-EVENT-SCAN-RESULTS Ready]
V/WifiMonitor( 617): Event [Trying to associate with 00:1b:2f:3e:78:52 (SSID='home2' freq=2452 MHz)]
V/WifiMonitor( 617): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3]
I/BluetoothHeadset( 617): Proxy object is now connected to Bluetooth Headset Service
D/SettingsWifiEnabler( 1261): Received wifi state changed from Enabling to Enabled
V/WifiStateTracker( 617): Connection to supplicant established, state=ASSOCIATING
D/dalvikvm( 617): GC freed 14086 objects / 599112 bytes in 240ms
V/WifiStateTracker( 617): Changing supplicant state: ASSOCIATING ==> ASSOCIATING
V/WifiMonitor( 617): Event [CTRL-EVENT-SCAN-RESULTS Ready]
V/WifiMonitor( 617): Event [CTRL-EVENT-SCAN-RESULTS Ready]
V/WifiMonitor( 617): Event [Authentication with 00:1b:2f:3e:78:52 timed out.]
V/WifiMonitor( 617): Event [CTRL-EVENT-STATE-CHANGE id=0 state=0]
V/WifiStateTracker( 617): Changing supplicant state: ASSOCIATING ==> DISCONNECTED
V/WifiMonitor( 617): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2]
V/WifiStateTracker( 617): Changing supplicant state: DISCONNECTED ==> SCANNING
V/WifiMonitor( 617): Event [CTRL-EVENT-SCAN-RESULTS Ready]
V/WifiMonitor( 617): Event [Trying to associate with 00:1b:2f:3e:78:52 (SSID='home2' freq=2452 MHz)]
V/WifiMonitor( 617): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3]
V/WifiStateTracker( 617): Changing supplicant state: SCANNING ==> ASSOCIATING
D/WifiStateTracker( 617): Deconfiguring interface and stopping DHCP
D/SettingsWifiEnabler( 1261): Received network state changed to NetworkInfo: type: WIFI, state: DISCONNECTED/DISCONNECTED, reason: (unspecified), extra: (none), failover: false, isAvailable: true
V/WifiMonitor( 617): Event [Authentication with 00:1b:2f:3e:78:52 timed out.]
V/WifiMonitor( 617): Event [CTRL-EVENT-STATE-CHANGE id=0 state=0]
V/WifiStateTracker( 617): Changing supplicant state: ASSOCIATING ==> DISCONNECTED
V/WifiMonitor( 617): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2]
V/WifiStateTracker( 617): Changing supplicant state: DISCONNECTED ==> SCANNING
V/WifiMonitor( 617): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2]
V/WifiStateTracker( 617): Changing supplicant state: SCANNING ==> SCANNING
D/WifiStateTracker( 617): Deconfiguring interface and stopping DHCP
D/SettingsWifiEnabler( 1261): Received network state changed to NetworkInfo: type: WIFI, state: DISCONNECTED/DISCONNECTED, reason: (unspecified), extra: (none), failover: false, isAvailable: true

Mac address filtering? I have it turned on, but my NIT is already added. However, does Android use that MAC address? Or does the MAC address come out as 00:02:EE:C0:FF:EE ?? I see that one as "available to add".

YES! The MAC address is coming out screwy. If you have MAC addree filtering on (and mine is at two levels) id doesn't authenticate.

I can confirm:
had the same prob,
disabled filtering for now untill fixed ;-(

The MAC address seems to always be 0002EEC0FFEE, so you could add that to the filter. Probably safer to prevent the casual security cracker.

Yeah, but now everyone is going to be checking 0002EEC0FFEE.

And Coffee? LOL.....

But without MAC address filtering, everyone who reads this thread will know how to get past that MAC address.... AND the entire world that doesn't will be able to get on to your network if they can crack the other security, So long as you're at least using WPA, the fact a MAC address is public isn't going to help anymore than not filtering at all - but not everyone reads this thread :-) (assuming that Google didn't set that MAC address..)

A quick Google shows only NIT hits for that MAC address really. A few for this thread (bloomin' eck that was fast Google!) and some on a thread sating Debian falls bacl to that MAC address. So I'm guessing it's either kernel/driver/chipset doing it?!?!!

The fake MAC address problem is because you need the binary calibration tool for the new driver as pointed by the logcat output. It can't be shipped with NITdroid as it is not distributable by Nokia but you can download it and place it in the right place (again as suggested by the logcat output) and NITdroid will use it.

It is optional but if present the calibration tool will set the real MAC address, better calibration data plus other undisclosed parameters (maybe region frequencies, etc).