Repository navigation
Network interface not working and no IP assigned. #17
Description
I'm getting the following error:--
__ _
/ _| | |
| |_ __ _ | |_
| _| / _` | | __|
| | | (_| | | |_
|_| \__,_| \__|
Welcome to the Firmware Analysis Toolkit - v0.2
Offensive IoT Exploitation Training - http://offensiveiotexploitation.com
By Attify - https://attify.com | @attifyme
[?] Enter the name or absolute path of the firmware you want to analyse : /home/r00tb3/Desktop/dir-816/firmware/AP699E8C.CW125A-5-DLINK-R1B011D81870(0519085924)(1).img
[?] Enter the brand of the firmware : dlink
[+] Now going to extract the firmware. Hold on..
[+] Firmware : /home/r00tb3/Desktop/dir-816/firmware/AP699E8C.CW125A-5-DLINK-R1B011D81870(0519085924)(1).img
[+] Brand : dlink
[+] Database image ID : 1
[+] Identifying architecture
[+] Architecture : mipsel
[+] Storing filesystem in database
[+] Building QEMU disk image
[+] Setting up the network connection, please standby
[+] Network interfaces : []
[+] Running the firmware finally
[+] command line : sudo /home/r00tb3/re-tools/firmware-analysis-toolkit/firmadyne/scratch/1/run.sh
[*] Press ENTER to run the firmware...^CTraceback (most recent call last):
Why isn't it enabling any network interface?
How do I get this working and get and IP assigned to it?
Waiting for replies!!
Activity
extremecoders-re commentedon Apr 3, 2018
Unfortunately, not all firmware image work out of the box with firmadyne. Looks like the inferNetwork.sh script failed to detect any interface. Try increasing the timeout value in inferNetwork.sh which is a part of upstream firmadyne.
Steps here
r00tb3 commentedon Apr 3, 2018
@extremecoders-re The problem is that Init crashes:--
I think I'll have to recompile the libnvram but I don't know how to do it.
Pls, help me with this.
Thanks for the reply!!
extremecoders-re commentedon Apr 4, 2018
You can include additional entries by modifying config.h.
r00tb3 commentedon Apr 4, 2018
@extremecoders-re
What additional entries do I have to add?
I'm figuring that out.
extremecoders-re commentedon Apr 4, 2018
Check the error messages
nvram_get_buf: Unable to open key:DerZc commentedon Jan 9, 2019
@r00tb3 Have you solved this problem? How did you do?
r00tb3 commentedon Feb 25, 2019
No i haven't solved the problem yet.
anindya14 commentedon Apr 29, 2021
did you get the solution of it @r00tb3 ?
mark0519 commentedon Mar 21, 2022
Is anyone able to solve this problem now?
devika6001 commentedon Nov 14, 2023
@mark0519 are you able to solve this problem?
sdahiasdba commentedon Apr 2, 2024
@mark0519 @extremecoders-re @anindya14 @r00tb3 @DerZc @mark0519 Anyone solve this problem?!!!
adi0x90 commentedon Sep 25, 2026
The empty interface list doesn't tell me whether this DIR-816 image booted far enough to configure its network.
FAT 2's native
qemu-directsystem mode uses host-port forwarding instead of the old network-inference script. The guest still needs to boot and start its services, and DIR-816 isn't covered by the successful extraction tests listed here.Please add the image hash, backend, and extraction/preflight/serial output from a v2 run. That'll show where this particular image first gets stuck.
adi0x90 commentedon Sep 26, 2026
I found the DIR-816 filename in your log, but have not found a working download for that specific build:
AP699E8C.CW125A-5-DLINK-R1B011D81870(0519085924)(1).img.Could you share a current download link and the file's SHA-256? PR #108 improves extraction, but I have not tested this exact image or resolved its init/network failure.
For a retry, please use FAT 2.0.1, a fresh project, and include the backend and new serial log.