For future reference, in order to put a fluksometer in a adhoc network, these are the steps I used:
+ setup an adhoc network on a pc and write down the bssid (AP hex number)
+ setup the flukso wireless on the web front-end
+ ssh into the fluksometer & change sta mode to adhoc mode in /etc/config/network
+ restart the network on the fluksobox
+ change the bssid on the fluksobox if it's not the same as the bssid noted above with: iwconfig ath0 ap xx:xx:xx:xx:xx
+ restart the fluksonetwork again
could be related: I added an ntp server for our local network, but this isn't working yet. The ntpclient command works from the fluksometer, but the web front-end only shows the correct system time, and not the last synchronization time. To be continued...
Edit: The communication with the ntpserver works flawless. I should have just saved the sensor page to show the correct last syncronization time.
Again for future reference: Instead of putting the FLM in ad-hoc, you can also install hostapd+dhcp+NAT on the laptop to make it behave like a access point en route the traffic from the fluksometer to the net. I followed this guide: http://nims11.wordpress.com/2012/04/27/hostapd-the-linux-way-to-create-v...
Minor bump in the guide: you have to give sufficient privileges for user "dhcp" to PID file /var/run/dhcp3-server/dhcpd.pid (with chown and chmod)
Thanks for testing out the adhoc mode on the FLM!