efforg/rayhunter#627

View on GitHub →
#627 Introducing “Rayhunter + Tailscale + Telegram” for the TP‑Link M7350 V9 🚀

Hello Rayhunter community 👋

I’m pleased to share a companion project I built that runs alongside Rayhunter to enable secure remote access and boot-time alerts on the TP-Link M7350 V9, using Tailscale and Telegram.

📦 Project repo: MHSEA / Rayhunter‑Tailscale‑Telegram


🔧 Why I Built This

Rayhunter is a fantastic tool. However, monitoring the device remotely, particularly when it’s behind CGNAT, makes it difficult to retrieve logs after boot or determine the device’s status (such as IP address, uptime, and warnings) when not physically present.

By integrating Tailscale and Telegram, my goals were to:

  • ✅ Automatically start Tailscale on boot and generate logs
  • ✅ Enable secure remote access via Tailscale
  • ✅ Receive a Telegram alert with IP addresses, device status, and uptime
Telegram alert preview

💬 Feedback & Requests

I’d love to hear from the community:

  • Suggestions for improving reliability, error handling, or security
  • Ideas for new features (e.g. integration with the Rayhunter web UI)
  • Bug reports or compatibility feedback from other supported devices

Thanks to the EFF and the Rayhunter community for building the foundation. Special thanks to @simonft for the idea and inspiration.

Looking forward to your thoughts, questions, and contributions 🙏
MHSEA

Comments (5)

nice! i looked at the code and it seems that you only need to replace /media/sdcard with /data/rayhunter to make this work on older TP-Link versions and the Orbic. /data/rayhunter should be a symlink to /media/sdcard or /media/card depending on version so it should work regardless.

Thanks for taking the time to check out the code, really appreciate it! That’s a great tip about using /data/rayhunter as a symlink for broader compatibility. I’ll look at incorporating that into the next update to better support older TP-Link models and the Orbic. As the M7350 V9 is the only model I have on hand, I’m not too familiar with the structure of other TP-Link or supported devices.

I’m also planning to release another version of the script that uses ntfy.sh for notifications as an alternative to Telegram. It should be a great option for those who prefer a lighter or self-hosted setup.

ntfy.sh support is built into ray hunter (you can scroll to the bottom to configure it). but it notifies on different things than your script

Thanks for sharing! For me, the real advantage of using a Telegram bot instead of ntfy would be being able to interact with Rayhunter remotely without needing Tailscale, and being able to retrieve alert content and PCAPs. But that requires more work and integration into the Rayhunter code (at least to capture alerts).

Cool project, but I don’t think I would merge this into main. Telegram is horrendously insecure and I don’t want to encourage people to use it at all.