-
Notifications
You must be signed in to change notification settings - Fork 2
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
Unable to access web server at 1.1.1.100 #5
Comments
Here is the output from an interrupted auto boot:
|
Hi there. Looks like it is in fact
However, later in the log you see
at which point it stops responding to all traffic. The long and short of it is that you need to be quick to make a web request. For my firmware (yours looks to be the same) it prints the |
If that turns out to be the factory default for you then please feel free to submit a PR with updated documentation :) |
Here is the config_get:
|
Looks like the same config_get as other posts I have seen. There is a very short amount of time between the starting web server, and the stop ip/arp traffic. Maybe my timing is just off, I will keep trying.
|
Had a quick look through old logs (no serial access right now) and they look very similar to what you have... Also, once you have a backup of your firmware you could try flashing my modified firmware (which would likely include config changes I had made at the time?) and see if that does the trick. Though obviously it'd be better to find out what changes one can make on the CLI without a programmer. Try issuing a Edit: updated the |
Here is the params.txt:
Now I see the stop_ip parameter! I am going to backup firmware (ordered the ch341_SOIC clip, will be here later today) and then flash your firmware. Thank you! |
After setting stop_ip to zero and rebooting, I can now access the web page. 👍🏻 |
Great to hear! Do you think that |
I didn't run format_cfg at all. Setting the stop_ip parameter is what allowed me to get into the web console. Once I set that stop_ip to 0, it behaved as you described, where I had 1 minute to call the web service. After 1 minute, it would send a "stop ip/arp traffic !" in the serial console. |
I can do a PR to update the Readme. |
Thanks for your feedback, I updated the readme to reference setting |
Thank you @danieltwagner! I have uploaded my flash extract from my qsw-2104-s2-a. The md5 checksum is different than your extract, so I am uploading in case somebody else needs it. |
Mind if I add it to the repo? |
Not at all. Do you want me to do a PR? |
Sure, that way you'll show up as a contributor :) |
I added it just now |
Thank you for all the work on documenting this. I have the qsw-2104-s2-a switch, and started down the path of opening the case and connecting a serial port to the J1 header to understand why it wasn't recognizing my Finsar sfp+ module. I found this repo while looking, and attempted to follow the instructions in the Readme.
I am unable to access the webserver at 1.1.1.100. I have manually set my ip to 1.1.1.200, I have tried every port. It never maps 1.1.1.100 to an arp, and never connects.
Here is the output from the serial port:
Is there a specific port you need to be connected to for the web server to work? I suspect that they made a change to the "-A" switch that blocks the web server from being accessed.
Here is the dump of my json/config.jsn file.
I am going to connect an SOIC and download the firmware, I suspect it is slightly different.
The text was updated successfully, but these errors were encountered: