mirabox: initial configuration
i’ve just begun to try to match my sheevaplug’s (RIP) configuration on a mirabox. the only thing i’m struggling with so far is the wireless configuration…
serial config from windows:
port: COM3 (this varies)
speed: 115200
could not get the serial connection from linux to work should be /dev/ttyUSB0
/etc/network/interfaces:
#eth0
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.10
netmask 255.255.255.0
#eth1
allow-hotplug eth1
iface eth1 inet static
address 192.168.1.20
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 192.168.1.1
a DHCP config would resemble…
auto eth1
iface eth1 inet dhcp
#mlan0 (wireless)
auto mlan0
iface mlan0 inet dhcp
wpa-ssid <ssid>
wpa-psk <wpa key>
created a route by running:
route add default gw 192.168.1.1 eth1
wireless info (mostly from the mirabox user guide):
the mirabox will automatically boot up in an access point configuration by default, run wlan.sh to change to client mode.
scan for APs:
iwlist mlan0 scan
^i ran into my first issue here as the access point i wanted was set for 2.4GHz channel 13. which won’t show up in a US scan without tweaking.
scan tweak info here: http://penturalabs.wordpress.com/2013/05/16/is-your-wifi-ap-missing-channels-12-13/
related info:
root@mirabox-debian:/etc# iwlist mlan0 channel
mlan0 32 channels in total; available frequencies :
Channel 01 : 2.412 GHz
Channel 02 : 2.417 GHz
Channel 03 : 2.422 GHz
Channel 04 : 2.427 GHz
Channel 05 : 2.432 GHz
Channel 06 : 2.437 GHz
Channel 07 : 2.442 GHz
Channel 08 : 2.447 GHz
Channel 09 : 2.452 GHz
Channel 10 : 2.457 GHz
Channel 11 : 2.462 GHz
connect to AP:
iwconfig mlan0 essid “<SSID>”
dhclient mlan0
^2nd issue here as i’ve been unable to connect to any APs…
sources:
http://www.cyberciti.biz/faq/setting-up-an-network-interfaces-file/
http://www.cyberciti.biz/faq/linux-setup-default-gateway-with-route-command/
http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_basic_syntax_of_etc_network_interfaces
update 9/13/2014:
i was getting an “authentication failure” when using su as a non-root user. upon closer inspection, ls -l /bin/su revealed that the setuid bit was not set on the executable. i set it with chmod +s /bin/su.