Automic VaultAutomic Vault

brew

Installer ip_relay avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de ip_relay pour les workflows d'agents IA.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install ip_relay

local Homebrew formula metadata

aperçu

Résumé du paquet

TCP traffic shaping relay application

Commandes et alias

  • ip_relay

historique

Historique du projet et usages

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.

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

  • 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.

posture de sécurité

Niveau de risque : vert

narrow executable package without higher-risk signals.

Classificateur de risque

risque vert · confiance faible · appliance

Pourquoi

  • narrow executable package without higher-risk signals

Signaux

  • metadata:no-higher-risk-signals

Comportement d'installation

  • Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
  • Les métadonnées de bottle Homebrew sont disponibles pour 1 plateformes.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

exécutables

Exécutables installés

CommandeTypeExpositionNote
ip_relaycliexécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-08
version du gestionnaire0.71
gestionnaire mis à jour
données localesOK
amontnot checked
dernière version détectéenon détecté

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

  • infoNo package-manager update timestamp was available.confiance faible
  • infoRelease/tag comparison is only available for GitHub repositories.https://stewart.com.au/ip_relay/confiance none

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:ip_relay
Version0.71
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/ip_relay
Page d'accueilhttps://stewart.com.au/ip_relay/
Docs amonthttps://stewart.com.au/ip_relay
LicenceGPL-2.0-only
Archive sourcehttps://stewart.com.au/ip_relay/ip_relay-0.71.tgz
Bouteilledisponible (sur all)
post-install Homebrewnon défini
Serviceaucun déclaré

faits du registre

Détails de la base source

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

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • 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