Skip to content

[ 210.320000] firmadyne: ioctl: 0x4 #85

Description

@Abib-web

Hi,

I have this output on terminal however pings to 192.168.0.1 address does not work and page does not show for dlink firmware

image

Activity

  1. johnathanhuutri commented on May 29, 2023

    @johnathanhuutri

    I also got this too when running on ubuntu 20.04 with 2CPU, 4GRAM. It gave me the ip interface ['br0', '192.168.0.1'] but then it said that

    br0: link is not ready
    

    And the error:

    image

  2. johnathanhuutri commented on May 29, 2023

    @johnathanhuutri

    Ah I see, as extremecoders-re mentioned this on issue #12, the ioctl error is because of firmadyne, not firmware analysis toolkit

  3. adi0x90 commented on Sep 25, 2026

    @adi0x90
    Member

    The firmadyne: ioctl message comes from the emulation environment. I can't tell from that line alone why the web page isn't reachable.

    FAT 2 has a native qemu-direct system path with port forwarding. Using it changes the kernel and backend, but the firmware may still depend on device-specific operations that need attention.

    Please share the D-Link model/version, selected backend, full serial log, and mapped endpoint from a v2 run. I'd like to find the startup failure behind the missing page before marking this fixed.

  4. adi0x90 commented on Sep 26, 2026

    @adi0x90
    Member

    PR #108 improves firmware extraction, and a local D-Link sample now passes the content comparison against independent reference extraction. This thread does not identify the model or version, so I cannot claim that result applies to your image yet. These extraction checks used case-sensitive APFS.

    Please share the firmware model/version and a download link or SHA-256. If it is the Dlink_firmware.bin discussed in #84, confirming its hash there would be enough to match the sample.

    Please retry with FAT 2.0.1 in a fresh FAT project so an old extraction manifest is not reused. Keep the executable and its matching share directory together. Use case-sensitive output storage if the image contains filenames that differ only by case.

    I'm keeping this open for the unreachable web interface. For a new attempt, please include the backend and full serial log so we can see what happens before the repeated ioctl messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions