https://github.com/cptmeetkat/optusdnsbypass

Bypass locked DNS on Optus Sagemcom 5393
https://github.com/cptmeetkat/optusdnsbypass

dns optus pihole router sagemc

Last synced: about 1 month ago
JSON representation

Bypass locked DNS on Optus Sagemcom 5393

• Host: GitHub
• URL: https://github.com/cptmeetkat/optusdnsbypass
• Owner: CptMeetKat
• Created: 2023-06-15T08:47:46.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2024-02-02T07:39:46.000Z (10 months ago)
• Last Synced: 2024-09-26T13:01:55.532Z (about 2 months ago)
• Topics: dns, optus, pihole, router, sagemc
• Language: JavaScript
• Homepage:
• Size: 68.4 KB
• Stars: 3
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# 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":", "`

6. Run `node app.js -md  ` 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](https://pi-hole.net/) at the router level.

**Note:** There is no custom DNS option.

 

![Locked router interface](./images/router_interface.jpg)

### 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":", `"

- 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://\/api/v1/dhcp **after** logging into the admin panel