-
Notifications
You must be signed in to change notification settings - Fork 260
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
There is an error in the network interface assignment. #70
Comments
Quite likely. Looks like after the device has finished booting some service is started which segfaults. The proper way to diagnose the issue is to investigate which services are launched after boot and try by disabling them one by one. |
If you check the logs after boot, you won't be able to tell exactly which service is causing the crash. Can you give me some helpful information? This is an attached part of the log that appears to be an error. |
Hi, I'm adding a firmware file for this issue. |
Log into the router shell and disable the firewall by running |
qemu.initial.serial.log
qemu.final.serial.log
If you extract the firmware through the ./fat.py script and try to emulate it, the IP is assigned to the br-lan interface of 192.168.1.254.
However, this is an IP that is no longer available after some time has elapsed during the boot process. Host is down problem.
So I checked the qemu boot log of the firmadyne tool to confirm that it was a boot process problem. Does it have something to do with the Segmentation Fault error that occurs during boot?
We need a way to solve this problem. thank you!
The text was updated successfully, but these errors were encountered: