逆向工程 Drobo 5N 網路協定
一位 Drobo 5N 擁有者使用 REA 對該裝置的遠端控制網路協定進行逆向工程,並發布了一個 Python 程式碼,用於執行握手並列印狀態、系統、網路與硬碟資訊。
關於這個案例
這篇 Reddit 貼文描述如何使用 reverse engineer anything(REA)來分析用於遠端控制作者自己的 Drobo 5N 的協定。在擷取封包並工作數小時後,作者發布了一個 Gist,其中包含一個標準函式庫 Python 程式碼,該程式碼會執行網路握手並收集 Drobo 的狀態、系統、網路與硬碟資訊。目標是與擁有者的老舊硬體互通,包括最終實現遠端關機,且作者邀請在其他 Drobo 5N 與 5N2 裝置上進行測試。
安裝設定
安裝方式請查看原始來源。
原文 / README
Long-time Drobo owner, first time poster! My Drobo 5N, bought more than a decade ago, on a different continent, is still going strong to this day (I had to replace its fan a couple of years ago). It is occasionally controlled by an equally aging MacBook Pro, leaving me wondering what I would do if the Mac gave up. So for a while I had this itch to throw Claude into the mix to try reverse engineering the protocol that is used to remotely control a networked Drobo. The most recent Opus 5.5 flat out refuses to go deep on this; luckily Opus 4.8 doesn't have these safeguards. So I spent my lazy Saturday morning using reverse engineer anything (a reverse engineering toolbox for agents) attempting to crack open that black box. A few hours, many packet captures and a lot of tokens later, here's the result: https://gist.github.com/tsak/6ecdab10def5731824411bd9b84a7a52 This Gist contains a Python script to execute the network handshake between my laptop and the Drobo, gathering my 5N's status, system, network and drive information, all printed neatly to the terminal. I have tested this with Python 3.11 and 3.15 on Linux. My hunch is that it might work on Windows/macOS and with anything from Python 3.10 onwards. It only uses the standard library. My ultimate goal is to be able to remotely shut the unit down, but for now being able to see how it's doing is quite neat. Because I only have that single unit, it would be cool if anybody could test this. I would be curious whether this works with a 5N2, and of course with other 5Ns. Anyway, cool to see that there's an active community of Drobo users! submitted by /u/Ok-Priority-Go to r/drobo [link] [comments]



