How kucer0043/givemeip works
Main Components
• Client Device: Represents any device on the network with a “grey IP” (or private/non-white IP). These devices are initiating requests or receiving data.
• Retranslator Device: A network node with a “white IP” that acts as an intermediary, receiving requests from one client and forwarding messages to another.
• Network Connections: The communication links between clients and retranslator(s), including ports and protocol-specific details.
• Protocol Specification: While not a software service per se, the protocol markdown files (protocol.md and protocol_rus.md) define the communication semantics (like IP format: “IP:Port::Last4RandomChars”) used in the system.
Relationships and Interactions
• A Client selects its associated retranslator.
• When one client (with a grey IP) wants to reach another, it sends a message to the retranslator associated with the target client.
• The retranslator, already connected to its client, receives the request and then routes the message/data to the correct destination.
Architectural Patterns and Design Principles
• Mediator Pattern: The retranslator acts as a mediator between clients.
• Decoupling of Client-Server Roles: Clients do not interact directly; all communication goes through retranslator nodes.
Relevant Technologies/Protocols
• The unique addressing scheme using a combination of the retranslators’ IP, a designated Port, and a suffix (like “::OOMG”) is a critical part of the design.
• Network layering and possible API layer – even if this proposal is high-level, it is important to indicate how data is encapsulated and forwarded.