Skip to content

CptMeetKat/OptusDNSBypass

Repository files navigation

OptusDNSBypass

An automated bypass to the locked DNS interface on the Optus Sagemcom 5393 router.

  • This bypasses the locked DNS settings by simulating the API calls made by the router to its internal firmware
  • This could be developed further to automate other router configurations

Target Router / Firmware

This information is available on the router admin login home page

  • Firmware version: SGKY10000893
  • Hardware version: FAST5393LTE-A
  • Serial number: N7230629B006867

Pre-requisites

  • Node v17.9.0

How to Use?

  1. Run npm install
  2. Copy settings.conf.sample and rename to settings.conf
  3. Populate the fields: host, password
    • username is default optus
  4. Run node app.js -vd in console
  5. You will see the current DNS settings logged to the console in the field "dnsservers":"<dns1>, <dns2>"
  6. Run node app.js -md <DNS-ip1> <DNS-ip2> to modify DNS
  7. Wait 10 seconds for the router to update its configurations
  8. Run node app.js -vd in console to verify results

Admin Panel Locked DNS

When attempting to customise the DNS from admin panel, you are only provided the options of choosing from a pre-selected list (see image). This may be sufficient for most purposes, however this would make infeasible to hook in a Pi-hole at the router level.

Note: There is no custom DNS option.

Locked router interface

FAQs

The DNS has not changed when viewing from the router admin panel?

  • This is expected, however when you view the DNS from the API using the scripts, you will see the newly applied DNS in the field "dnsservers":"<dns1>, <dns2>"
  • The router admin panel seems to get confused and will not display correctly as the new DNS is not from the pre-selected options
  • The current DNS settings can also be viewed by visiting http://<router-ip>/api/v1/dhcp after logging into the admin panel

About

Bypass locked DNS on Optus Sagemcom 5393

Topics

Resources

Stars

Watchers

Forks