WiFi configuration

Last Updated on Thursday, 12 January 2012 06:03 Written by admin

If you don’t have a remote control for your NeTV, or you lost it, you can still configure wifi via command line interface (ssh).

Do the following:

  • Plug NeTV into the USB port of your computer
  • wait for NeTV to boot and register as an ethernet device.
    If this is the first time you’re plugging the device in, you’ll probably have to wait for the NeTV to boot, register as an ethernet device, and then reboot it. The reason is that there is a 10-second window where the startup script checks for a valid ethernet connection to decide if to turn on sshd or not. If you miss the window, even though netv is booted and connected via USB, sshd will not be on.
  • ssh to 10.0.88.1 as root
  • from here, you will need to do the following:
 cd /psp
 cat > network_config
 <configuration allocation="dhcp" encryption="AES" auth="WPAPSK" key="foobar" ssid="yourssid" type="wlan" />
 ^D
 killall hostapd
 killall dnsmasq
 /etc/init.d/NetworkManager restart

This should get your device onto the wifi network with the specified SSID and encryption mechanism.

Other example network_config templates:

'''open'''
 <configuration allocation="dhcp" encryption="NONE" auth="OPEN" hwaddr="" ssid="ChumbyTest" type="wlan" />

'''WEP'''
 <configuration type='wlan' ssid='wepAP' allocation='dhcp' auth='WEP' key='1234567890' encoding='hex' encryption='WEPAUTO'/>

'''WPA2'''
 <configuration allocation="dhcp" encryption="AES" auth="WPAPSK" key="foobar" ssid="yourssid" type="wlan" />

3 Comments

  1. JaseNo Gravatar   |  Monday, 06 February 2012 at 9:31 pm

    It seems that this is out of date, and/our incomplete. When writing to the network_config file, I just got an error message that the filesystem was read only.

    After remounting the fs with r/w permissions, I was able to write the file.

    I still haven’t managed to get the device to talk to my wlan, so I’m not sure if there’s something else missing in these instructions, or if I’m just doing something wrong (perhaps it doesn’t like the particular combination of auth/encryption I’m using – is there a complete list of what is supported?).

    There was also an error from the second killall command, but that may be benign (i.e. there was nothing to kill).

  2. bunnieNo Gravatar   |  Wednesday, 08 February 2012 at 7:27 pm

    /psp should always be mounted as read/write. If it’s mounted as read-only, that means there may be a filesystem error that could be causing other problems. If it fails to fsck, it will mount the filesystem as ro. Does anything show up in dmsg about a mounting error, or does mount show anything unusual?

    It should support at least open, WPA2 with AES, and WEP. It can also do WPA with TKIP. WEP configuration is a little bit tricky because there is no standard way to go from WEP passwords to the binary form it requires.

    The device uses NetworkManager. You should be able to use nmcli to get more visibility into what’s going on in the connection process.

  3. Kent SmithNo Gravatar   |  Saturday, 03 March 2012 at 8:12 am

    After following this procedure, I initially was successful attaching to my WiFi Lan.

    The SSID is “Columbusparkllc 2.4″

    After pressing the setup button on the side, I was asked to Select a WiFi network.

    The SSID presented on the NeTV GUI was “Columbusparkllc+2.4″
    The blank following .”…llc” is being represented with a + character.

    Now, I can not connect to the network….

    Please advise.

    Thanks
    Kent Smith

Leave a Reply