Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Admin pages drift to different IP addresses. #11

Open
chanjuping opened this issue Jun 1, 2023 · 2 comments
Open

Admin pages drift to different IP addresses. #11

chanjuping opened this issue Jun 1, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@chanjuping
Copy link
Member

Describe the bug
For reasons unclear to us, 192.168.100.100 is not always the standard admin login page, but may become 192.168.100.101 too. It should be consistent. Similar to how all Mikrotik devices default to the same IP address for setup and administration across all models.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 192.168.100.100
  2. Sometimes fails, different IP address selected.

Expected behavior
The same IP address, through all of time and all of space.

Additional context
This also eliminates the need for a desktop app just to find the IP address on a Windows machine. And negates the need for a desktop app.

@chanjuping chanjuping added bug Something isn't working enhancement New feature or request labels Jun 1, 2023
@KahJunC
Copy link

KahJunC commented Jun 2, 2023

Default setting :

QTS adapter is DHCP client mode , it connects to router LAN.

Router enable DHCP server and provide 192.168.100.100~192.168.100.150 IP pool.

DHCP server will provide 192.168.100.100 for first request client and 192.168.100.101 for second request client and so on.

Sometimes we also connect a PC(or several DHCP client) to router LAN , so DHCP server will provide IP depend on request sequence.

It's DHCP server operate behavior.

Here is some suggestion

Suggestion 1 :

Use Qfinder to know , what is the QTS IP.
MicrosoftTeams-image (5)

Suggestion 2 :

Configure DHCP server reserved IP function to assign fixed IP for QTS device. The reserved IP must in DHCP pool.

Reboot QTS to get reserved IP.
MicrosoftTeams-image (7)
Adapter 2 MAC can check in NVS.
MicrosoftTeams-image (6)

Suggestion 3 :

Go to QTS NVS setting , configure adapter 2 to fixed IP and the same router IP subnet.

Suggest the fixed IP is not in router DHCP pool to aviod IP conflict.
MicrosoftTeams-image (8)

@chanjuping
Copy link
Member Author

chanjuping commented Jun 5, 2023

The QMiroPlus device we are referencing here is the actual router. It's playing the role of assigning IP addresses, including to itself. I am clarifying that by default, all of the steps above should not be necessary for this product, if it itself is its own DHCP server, and consistently assigns the same IP address to itself out of the box.

This is a usability bug because we are distributing these items to schools that may for simplicity, reset these devices to the factory state before heading into the admin page. That means whatever settings we may have done (or in this case being suggested) may be lost. It is better for there to be a consistent IP address we know will work every single time.

I pointed out Mikrotik devices as an example because barring any actions, it will always default to 192.168.88.1, and it is that default behaviour that would be immensely beneficial for setup.

@chanjuping chanjuping removed the bug Something isn't working label Jun 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants