Automic VaultAutomic Vault

brew

ip_relay mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für ip_relay in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install ip_relay

local Homebrew formula metadata

Überblick

Paketzusammenfassung

TCP traffic shaping relay application

Befehle und Aliase

  • ip_relay

Verlauf

Projektgeschichte und Nutzung

ip_relay is Gavin Stewart's Perl TCP relay for shaping proxied traffic to a chosen bandwidth. It is an early home-user bandwidth-control tool: simple, single-user, and intentionally user-space rather than a router or kernel traffic-control system.

Projektgeschichte

The project page says ip_relay grew out of Stewart's modem Internet use, where a large download could make interactive activities such as telnet, web browsing, or voice traffic unpleasant. The README dates the documented release line to 2000-01-05 and describes the program as a TCP relay with traffic-shaping behavior.

Version 0.71, announced on 2000-05-27, added daemon mode and a command-line bandwidth option. The changelog attributes the daemon-mode request to Eduardo Augusto Alvarenga and notes command-line bandwidth selection as the other release change.

Adoptionsgeschichte

The official site preserves only a small release archive, and Homebrew packaging gives the tool most of its package-manager visibility. That makes it a niche package rather than a broadly adopted network daemon.

Its adoption story is strongest as preserved Unix networking craft: a small Perl program kept installable for users who want an inspectable TCP proxy to reproduce old bandwidth conditions or throttle a few streams.

Wie es verwendet wird

The common pattern is `ip_relay.pl local_port:remote_host:remote_port`, then optionally setting a total byte-per-second bandwidth cap shared by forwarded streams. The README walks through using it as an SSH or proxy relay and changing the bandwidth interactively while traffic flows.

The FAQ is explicit about the tradeoffs: ip_relay is not authenticated, not secure, not designed for multiple users, and single-threaded. It is best understood as a local testing and personal bandwidth-shaping tool.

Warum Paket-Nerds sich dafür interessieren

ip_relay is interesting to package nerds because it captures a pre-broadband style of Unix utility: a short Perl program solving a concrete modem-era problem with almost no infrastructure.

Its Homebrew formula keeps a tiny historical networking tool available without pretending it is a modern traffic-control framework.

Zeitleiste

  • 1999: The README examples identify the program as copyright Gavin Stewart 1999.
  • 2000-01-05: README date for the documented ip_relay.pl release line.
  • 2000-05-27: Version 0.71 announced with daemon mode and command-line bandwidth selection.
  • 2000: Older revision 0.7 and release 0.71 preserved on the project site.
  • Homebrew era: The tool was packaged as `ip_relay` for one-command installation.

Related projects

  • Conceptually related tools include SOCKS proxies, local HTTP proxy setups, traffic-shaping routers, and operating-system traffic-control facilities, but ip_relay is much narrower: it forwards selected TCP streams through a user-space Perl process.
  • The README also describes using it to simulate modem speeds while testing VNC over faster Ethernet links.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 1 Plattformziele verfügbar.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
ip_relaycliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-08
Manager-Version0.71
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://stewart.com.au/ip_relay/

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz
  • InfoRelease/tag comparison is only available for GitHub repositories.https://stewart.com.au/ip_relay/none Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:ip_relay
Version0.71
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/ip_relay
Homepagehttps://stewart.com.au/ip_relay/
Upstream-Dokumentationhttps://stewart.com.au/ip_relay
LizenzGPL-2.0-only
Quellarchivhttps://stewart.com.au/ip_relay/ip_relay-0.71.tgz
Bottleverfügbar (auf all)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameip_relay
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment