Closed Photon9 closed 1 month ago
Sorry, I can't help with macOS. I had troubles on windows getting pc to recognise bootp ip address. I tried hard code IP / network but wasn't being recognised. My network is in 192.168.1.x. I had to change my network to 192.168.0.x, reboot pc so it picked up a new 192.168.0.x ip address, then manually set ip address as per instructions.
Sorry, I can't help you with macOS either. And I know only a little bit about networking.
However, it is actually waiting to respond to a DHCP request. Your device won't be able to download the firmware unless it gets an IP address from tch-exploit.
The DHCP response is also the key to making the exploit work to get root access.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
So, I have followed the instructions (I believe, I changed the commands to use ifconfig rather than ip because I don't have ip on my mac). Got the firmware to downgrade to.
When running the command to downgrade firmware I get the first part of the expected output:
Wireshark pcap shows I am receiving all of the BOOTP packets.
I can see tftp.coffee is instantiating the tftp server.
So that means that my computer simply isn't responding to the BOOTP packets... well that means I gotta look at bootpd.
If anyone has any advice on how to configure bootd on macOS to do this I would be very appreciative.