Mount /storage from NFS during boot with WLAN?

[macrule]

I'm running OpenELEC 3.0.0 on a Raspberry PI. I have successfully managed to use boot parameters like "ip=dhcp disk=NFS=...." to mount /storage from an NFS server via wired network (all well described in the sticky thread "[IMPORTANT] Changes to kernel boot parameters, Please Read!").

Now my question: is it possible to do the same on a protected WLAN network? I haven't found any mention that it works or does not work. There would have to be parameters to specify the SSID and authentication and I can't find those documented. I would look in the source, but I don't even know if that is part of firmware, linux kernel, etc.

If it's not possible via boot parameters, is there a recommended way to do it by autostart.sh or something? Any pointers would be appreciated.

[LossAngeles]

I don't think so. The wlan driver isn't loaded at the time the boot process requests an IP address. The only way I can think of is to put the driver on the /system and load it in the cmdline.txt file if possible.

[LossAngeles]

If it's not possible via boot parameters, is there a recommended way to do it by autostart.sh or something? Any pointers would be appreciated.

Nothing in autostart.sh will help as it's not mounted yet !

[macrule]

Thanks for the answers. I suppose, at least I can stop looking for how to do it :-)

The idea with autostart.sh was to somehow mount an NFS storage at /storage after the boot (so there is oej34_kunena_messages.csv oej34_kunena_messages_text.csv oej34_kunena_messages_text.sql oej34_kunena_users_banned.csv oej34_kunena_users.csv replace.sh table_posts update_sample.sql local /storage, but not *the* /storage during boot). But I suppose that leads to all sorts of issues, with the autostart.sh residing on a mount that is supposed to go away while it's still runing. Maybe I just have to resort to mounting "safe" directories from NFS (like .xbmc).

[LossAngeles]

Thanks for the answers. I suppose, at least I can stop looking for how to do it :-)

The idea with autostart.sh was to somehow mount an NFS storage at /storage after the boot (so there is oej34_kunena_messages.csv oej34_kunena_messages_text.csv oej34_kunena_messages_text.sql oej34_kunena_users_banned.csv oej34_kunena_users.csv replace.sh table_posts update_sample.sql local /storage, but not *the* /storage during boot). But I suppose that leads to all sorts of issues, with the autostart.sh residing on a mount that is supposed to go away while it's still runing. Maybe I just have to resort to mounting "safe" directories from NFS (like .xbmc).

Re: safe directories , yes I'm doing that as well with the NFS mounted storage (only with a wire). I wanted certain items saved to favorites to appear on all the Pi devices in my home. The 3 wired devices have their own /storage mount (gd-oe-*) and the other items are meta data links to a NAS device that acts as a central repository for that data =) The interesting part of it all is that while all /storage is mounted at boot from the NAS on the cmdline.txt, the autostart.sh mount works perfectly on top of that as well =))

NAS export:
-----------------------------------

gd@wz-nas:/share/public/xbmc.meta$ ls -l
total 24
drwxrwx--- 2 xbmc video 4096 2013-01-26 13:03 1channel
lrwxrwxrwx 1 gd finance 30 2013-01-12 08:40 OE.bkup -> /share/dev/gd/OE.Ion.bkup
drwxrwx--- 7 xbmc video 4096 2013-03-01 18:22 plugin.video.icefilms
drwxrwx--- 4 xbmc video 4096 2013-04-12 08:20 script.module.metahandler
drwxrwx--- 18 root video 4096 2013-03-21 16:43 storage.gd-oe-br2
drwxrwx--- 19 root video 4096 2013-03-21 16:42 storage.gd-oe-lr
drwxrwx--- 16 root video 4096 2013-03-21 19:23 storage.gd-oe-of
gd@wz-nas:/share/public/xbmc.meta$


df -h from Pi client (notice the 2 separate nfs mount points):
------------------------------------------
OpenELEC Version: 3.0.0
root@192.168.1.202's password:
gd-oe-lr:~ # df -h
Filesystem Size Used Available Use% Mounted on
none 185.1M 87.4M 97.7M 47% /dev
/dev/mmcblk0p1 124.7M 96.1M 28.7M 77% /flash
192.168.1.102:/share/public/xbmc.meta/storage.gd-oe-lr
590.6G 524.9G 35.7G 94% /storage
/dev/loop0 87.4M 87.4M 0 100% /
none 186.5M 0 186.5M 0% /dev/shm
/dev/mmcblk0p2 755.9M 228.9M 488.6M 32% /var/media/Storage
192.168.1.102:/share/public/xbmc.meta
590.6G 524.9G 35.7G 94% /storage/wz-nas.public
gd-oe-lr:~ #

Finally the addon_data sym links from /storage/.xbmc/userdata/addon_data
--------------------------------------------------------
gd-oe-lr:~/.xbmc/userdata/addon_data # ls -l
total 36
drwxrwxr-x 2 root 44 4096 Dec 31 1969 os.openelec.settings
drwxrwxr-x 2 root 44 4096 Jan 15 16:19 plugin.video.1channel
drwxrwxr-x 4 root 44 4096 Dec 9 13:41 plugin.video.SportsDevil
drwxrwxr-x 2 root 44 4096 Dec 27 19:54 plugin.video.hulu
lrwxrwxrwx 1 root 44 44 Mar 1 21:38 plugin.video.icefilms -> /storage/wz-nas.public/plugin.video.icefilms
drwxrwxr-x 6 root 44 4096 Dec 29 21:14 plugin.video.icefilms.bkup
drwxrwxr-x 2 root 44 4096 Mar 31 16:19 script.common.plugin.cache
lrwxrwxrwx 1 root 44 48 Dec 13 16:15 script.module.metahandler -> /storage/wz-nas.public/script.module.metahandler
drwxrwxr-x 2 root 44 4096 Jan 12 11:08 script.module.urlresolver
drwxrwxr-x 2 root 44 4096 Dec 7 19:47 script.xbmcbackup
drwxrwxr-x 3 root 44 4096 Dec 5 13:40 weather.wunderground
gd-oe-lr:~/.xbmc/userdata/addon_data

[macrule]

That's good to know :-) I'll definitely experiment a bit along those lines. Thanks

[KillerKelvUK]

I'm running OpenELEC 3.0.0 on a Raspberry PI. I have successfully managed to use boot parameters like "ip=dhcp disk=NFS=...." to mount /storage from an NFS server via wired network (all well described in the sticky thread "[IMPORTANT] Changes to kernel boot parameters, Please Read!").

Now my question: is it possible to do the same on a protected WLAN network? I haven't found any mention that it works or does not work. There would have to be parameters to specify the SSID and authentication and I can't find those documented. I would look in the source, but I don't even know if that is part of firmware, linux kernel, etc.

If it's not possible via boot parameters, is there a recommended way to do it by autostart.sh or something? Any pointers would be appreciated.

I've not actually done this but the solution would be to use iPXE as this Preboot eXecution Environment has the ability to start wireless adapters and takes parameters to enable it to log into your wifi network. This happens prior to loading your PXE config and so is agnostic to what you're attempting to boot e.g it should work with OpenELEC, CloneZilla or anyother bootable solution.

Check this out.

[macrule]

I've not actually done this but the solution would be to use iPXE as this Preboot eXecution Environment has the ability to start wireless adapters and takes parameters to enable it to log into your wifi network. This happens prior to loading your PXE config and so is agnostic to what you're attempting to boot e.g it should work with OpenELEC, CloneZilla or anyother bootable solution.

Check this out.

That does look interesting, but I can't find any references that it works on the Pi (or how to get it to work on the Pi). I did find this post, which suggests it's far from working out of the box: http://lists.ipxe.org/pipermail/ipxe-dev...01878.html