-
Notifications
You must be signed in to change notification settings - Fork 119
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
Make Some Changes in firmae.config can make FirmAE Faster when facing a firmware image cannot be emulated. #56
Comments
Thank you for your code. Thank you. |
The firmae.config: [${START_TIME} + ${CHECK_TIMEOUT}] ] if (${WEB_RESULT}); then done echo "${RET_IP}" "${PING_RESULT}" "${WEB_RESULT}" "${PING_TIME}" "${WEB_TIME}" |
The Result: [IID] 166 |
Thank you for your reply. The reason I guess is that, the ${IPS} is empty. When the ${IPS[@]} is empty, IP is NONE and the for-loop will not be executed.Hope you can help me to explain this, thx. Maybe my solution can be better. |
Thank you for your reply. However, when I test the firmware on the Ubuntu 20.04. I can't reproduce your problem. As I mentioned before #56 (comment), any network information not be found in the inferring stage. And the FirmAE set the default network with 192.168.0.1 network. And stepped into the next real emulation stage. It will be good to share your environment to find the root-cause problem. Thank you. |
How to modify this default IP? |
First, thx for FirmAE tool. Very Useful.
Then, I find a problem when facing a firmware image cannot be emulated, FirmAE will enter an infinite loop in firmae.config code. Details below.
There is a "check_network" function in firmae.config.
When the ${IPS[@]} is empty, IP is NONE and the for-loop will not be executed. So the CURRENT_TIME will always equals START_TIME. Therefore, the WHILE will be an infinite-loop and never break.
So the simple solution put the code out of the FOR-loop and in the WHILE-loop.
Waiting 4 reply. Thx Again~.
The text was updated successfully, but these errors were encountered: