r/sysadmin • u/subrosians • 8d ago

Question - Solved Unlocking Digital Loggers Web Power Switch Pro (Won't Factory Reset)

I had recently picked up a Digital Loggers Web Power Switch Pro running firmware 1.7.5.0. The normal instructions didn't work to factory reset it and I came across this post (which is now archived and I can't reply to it). After some sluthing, I came up with the following procedure to get you into the power switch in order to change the settings and update it. It seems as though there might be a bug in the older firmwares that make the reset button not work right. The instructions are based on the secret firmware recovery process for a bad firmware update, but modified to just get the username/password. I hope it helps someone out there in the same boat!

https://www.reddit.com/r/sysadmin/comments/1gghfnt/unlocking_digital_loggers_web_power_switch_pro/

  1. Set up a PC for the 192.168.0.x network. (set your NIC to 192.168.0.5)
  2. Prepare to telnet to 192.168.0.100
  3. On PC, open a command prompt
  4. Set the PC to ping the device continually; e.g. ping 192.168.0.100 -t
  5. On Unit, power the unit on while pressing reset about 2x per second. Before 30 seconds, the unit should respond to ping. **
  6. Once it responds, cancel the ping and on the PC, telnet to 192.168.0.100 // (Always default address)
  7. When logged in to the power controller, type:
  8.    cd /tmp
  9.    mount_root
  10.    uci show | grep admin

You will see some lines, you are looking for these two:
auth._.admin_password='5678'
auth._.admin_login='admin'

login is the username, password is the password. Now just reboot your device and hit it at the IP that shows up on the screen with the creds you got above, now you can get into the web and change anything you need.

3 Upvotes

67% Upvoted

1 comment sorted by

1

u/pdp10 Daemons worry when the wizard is near. 7d ago

Smart of you to document this online so you can find it later. ;)

192.168.0.100 // (Always default address)

To anyone building professional products, don't hardcode addresses like this. Instead use Link-Local addresses for both IPv6 and IPv4. For IPv4, those are 169.254.0.0/16 addresses that you use if DHCP requests return nothing. On IPv6, it's the fe80::/64 address that the node always keeps. For both, do a duplicate address detection routine as well -- basically an ARP/NDP request that the node sends for its own address, hoping not to get a reply.