/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 blog.coffinsec.com
orbi hunting 0x0: introduction, UART access, recon | hyprblog
| | sinrega.org
Enabling KVM virtualization for Raspberry Pi 2 - Sergio López's Blog
3.0 parsecs away

Travel
| | [AI summary] A technical guide detailing how to enable KVM virtualization on a Raspberry Pi 2 by configuring isolated CPU cores, compiling custom kernels, and running guest operating systems.
| | gist.github.com
Work-in-progress U-Boot bootloader (still linked with the libdram blob) booting 32-bit Linux kernel on Pine64+ board · GitHub
2.7 parsecs away

Travel
| | Work-in-progress U-Boot bootloader (still linked with the libdram blob) booting 32-bit Linux kernel on Pine64+ board - gist:67ebb38e8f8f2b9b5ee6
| | harrisonsand.com
Reverse engineering an EV charger | Harrison's Sandbox
3.7 parsecs away

Travel
| | This blog post walks through the efforts of reverse engineering the Zaptec Pro, an electric vehicle charger found in many parking lots and apartment buildings around Norway.
| | willhaley.com
Recovering a TP-Link Archer C59 Router - Will Haley
5.5 parsecs away

Travel
| I had tinkered with OpenWrt on my TP-Link Archer C59 (v1) AC1350 (US) Router, but decided it's not for me. I appreciate all the work put into that project, but I didn't like the experience and wanted to restore my router to it's original stock OEM firmware. This is where I made a mistake. I uploaded an incorrect firmware file to restore things and rendered my router unusable or "bricked" (not permanently, thankfully). It would not boot into a state where I could use it. The admin web UI was inaccessible and only one LED light was on. I put it in a closet for a few months before trying to restore it. I don't remember much about exactly what firmware file I uploaded to break things.