For many devices it’s nice to have them configured with DHCP, like mobile phones. But a powerbar’d better have an IP that won’t change…

By default the mPower devices come with DHCP enabled (with fallback to 192.168.1.20), in this post we’ll have a look at setting a static IP address for both the mPower mini and mPower Pro devices.

Now ssh into the device on their pre-configured or DHCP-obtained IP. If it’s not been connected to the mFi controller the defaults credentials are ubnt:ubnt. Otherwise it’s the credentials used for the controller. This will you a BusyBox shell via the Dropbear SSH server:

BusyBox v1.11.2 (2014-06-09 19:20:46 PDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

MF.v2.0.24#

Assuming we want to configure the devices as such:

  • gateway: 192.168.178.1
  • netmask: 255.255.255.0
  • mPower mini: 192.168.178.2
  • mPower pro (wired): 192.168.178.3
  • mPower Pro (wireless): 192.168.178.4

The configuration file location is the same for both devices, /tmp/system.cfg.

Now ensure the lines below are recorded into this file, changing any existing lines where applicable.

mPower mini⌗ 

dhcpc.1.status=disabled
netconf.1.ip=192.168.178.2
route.1.devname=eth1
route.1.gateway=192.168.178.1
route.1.ip=0.0.0.0
route.1.netmask=0
route.1.status=enabled

mPower Pro⌗ 

dhcpc.1.status=disabled
dhcpc.2.status=disabled
netconf.1.ip=192.168.178.3
netconf.2.ip=192.168.178.4
route.1.devname=eth1
route.1.gateway=192.168.178.1
route.1.ip=0.0.0.0
route.1.netmask=0
route.1.status=enabled

If both wired and wireless are on the same network you won’t need to define any route.2. entries.

Now save the settings and reboot the device:

save
reboot

When the orange LED stops blinking and has turned solid blue you can reach it on the configured IP.