{"action":"created","issue":{"url":"https://api.github.com/repos/attify/firmware-analysis-toolkit/issues/1","repository_url":"https://api.github.com/repos/attify/firmware-analysis-toolkit","labels_url":"https://api.github.com/repos/attify/firmware-analysis-toolkit/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/attify/firmware-analysis-toolkit/issues/1/comments","events_url":"https://api.github.com/repos/attify/firmware-analysis-toolkit/issues/1/events","html_url":"https://github.com/attify/firmware-analysis-toolkit/issues/1","id":188092374,"number":1,"title":"Firmware not showing on network after running","user":{"login":"pabb85","id":3263002,"avatar_url":"https://avatars.githubusercontent.com/u/3263002?v=3","gravatar_id":"","url":"https://api.github.com/users/pabb85","html_url":"https://github.com/pabb85","followers_url":"https://api.github.com/users/pabb85/followers","following_url":"https://api.github.com/users/pabb85/following{/other_user}","gists_url":"https://api.github.com/users/pabb85/gists{/gist_id}","starred_url":"https://api.github.com/users/pabb85/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pabb85/subscriptions","organizations_url":"https://api.github.com/users/pabb85/orgs","repos_url":"https://api.github.com/users/pabb85/repos","events_url":"https://api.github.com/users/pabb85/events{/privacy}","received_events_url":"https://api.github.com/users/pabb85/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2016-11-08T20:15:12Z","updated_at":"2016-11-09T13:00:11Z","closed_at":null,"body":"Dear Sir,\r\n\r\nSo I have the following output;\r\n\r\n```root@kali:~/tools/firmadyne# ./fat.py \r\n\r\n\tWelcome to the Firmware Analysis Toolkit - v0.1\r\n\tOffensive IoT Exploitation Training  - http://offensiveiotexploitation.com\r\n\tBy Attify - https://attify.com  | @attifyme\r\n\t\r\nEnter the name or absolute path of the firmware you want to analyse : Dlink_firmware.bin\r\nEnter the brand of the firmware : Dlink\r\nDlink_firmware.bin\r\nNow going to extract the firmware. Hold on..\r\n/root/tools/firmadyne/sources/extractor/extractor.py -b Dlink -sql 127.0.0.1 -np -nk \"Dlink_firmware.bin\" images \r\ntest\r\nThe database ID is 1\r\nGetting image type\r\nPassword for user firmadyne: \r\nFound image type of  mipsel\r\nPutting information to database\r\nTar2DB\r\nCreating Image\r\nExecuting command \r\n\r\nsudo /root/tools/firmadyne/scripts/makeImage.sh 1\r\nPassword for user firmadyne: \r\nmke2fs 1.43.3 (04-Sep-2016)\r\nPlease check the makeImage function\r\nEverything is done for the image id 1\r\nSetting up the network connection\r\nPassword for user firmadyne: \r\nqemu-system-mipsel: terminating on signal 2 from pid 1925\r\nQuerying database for architecture... mipsel\r\nRunning firmware 1: terminating after 60 secs...\r\nInferring network...\r\nInterfaces: [('br0', '192.168.0.1')]\r\nDone!\r\n\r\nRunning the firmware finally : \r\n```\r\n\r\nBut nothing is coming up, demonstrated like so;\r\n\r\n```\r\nroot@kali:~# nmap 192.168.0.1\r\n\r\nStarting Nmap 7.31 ( https://nmap.org ) at 2016-11-08 20:11 GMT\r\nNmap scan report for 192.168.0.1\r\nHost is up (0.00045s latency).\r\nAll 1000 scanned ports on 192.168.0.1 are filtered\r\nMAC Address: 00:DE:FA:19:C0:02 (Unknown)\r\n\r\nNmap done: 1 IP address (1 host up) scanned in 34.69 seconds\r\n```\r\n\r\nAny tips on where to start debugging this?\r\n\r\nCheers,\r\nP.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/attify/firmware-analysis-toolkit/issues/comments/259409139","html_url":"https://github.com/attify/firmware-analysis-toolkit/issues/1#issuecomment-259409139","issue_url":"https://api.github.com/repos/attify/firmware-analysis-toolkit/issues/1","id":259409139,"user":{"login":"pabb85","id":3263002,"avatar_url":"https://avatars.githubusercontent.com/u/3263002?v=3","gravatar_id":"","url":"https://api.github.com/users/pabb85","html_url":"https://github.com/pabb85","followers_url":"https://api.github.com/users/pabb85/followers","following_url":"https://api.github.com/users/pabb85/following{/other_user}","gists_url":"https://api.github.com/users/pabb85/gists{/gist_id}","starred_url":"https://api.github.com/users/pabb85/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pabb85/subscriptions","organizations_url":"https://api.github.com/users/pabb85/orgs","repos_url":"https://api.github.com/users/pabb85/repos","events_url":"https://api.github.com/users/pabb85/events{/privacy}","received_events_url":"https://api.github.com/users/pabb85/received_events","type":"User","site_admin":false},"created_at":"2016-11-09T13:00:11Z","updated_at":"2016-11-09T13:00:11Z","body":"[Diagnosis-FAT-001.txt](https://github.com/attify/firmware-analysis-toolkit/files/580732/Diagnosis-FAT-001.txt)\r\n\r\nThen also no response :(\r\n\r\nAlthough the emulated system IP address is resolved to the following mac addy which may be for the emulated system; 00:DE:FA:19:C0:02 "}}
{"actor":{"display_login":"pabb85"}}