lanet 0.3.0 → 0.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 63793d57879f73e9391c3fe104d23d85e6fb67c8eeb2f87c20dcb5aa7166a1d8
-  data.tar.gz: 90157da24d774e9066f2a4ae7c31df2410bec002724e91a3db16e27cae265728
+  metadata.gz: 8c54bf6a4ec7bdeafe5e225e2cbbe34a181c1990254cd2fb1d3b975fbe670451
+  data.tar.gz: a3c802ffc1435b5797b32c2083f1512de1ca74309c25387bdf5fa87110c1fa41
 SHA512:
-  metadata.gz: db2199bbc4023df5e242152283e6ef3fe458dd06df80b931ebf1daebc3607cad6f73bd58cc1ec0f192b08fc0c467f86c92ecc3e19c07c829bbb41066d2d5ad35
-  data.tar.gz: e53ef8a5e71aa920f487c0d8437976c78c8102baf41923b069c414512b1b9930a0804cac9e44023668cf0923c80afc71b6c0c7eb82f6f4cfb7d542676f1842bc
+  metadata.gz: 54aa773fe7dc3a6699e7d04de688174f656151dd507bfe439c9780a5efa6521dddbc26d7a97e6e4889f5e17d505cbc2e8926567ef9dc0b30b04f171fcdfcb1d9
+  data.tar.gz: c564091430f87f22ef93046ceb2c5a28c210610e9fee78e6d87e082a7380440c20547e1b449b34321bfed8c80e1a83d1707f9daa822fd70cbf053384e8827c00

data/CHANGELOG.md

@@ -5,6 +5,25 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.5.0] - 2025-03-12
+
+### Added
+- Advanced traceroute functionality for network path analysis
+- Multiple protocol support for traceroute: ICMP, UDP, and TCP
+- Load balancing detection in traceroute results
+- CLI command: `traceroute` with protocol selection and customizable parameters
+- Ruby API for programmatic traceroute operations
+- Comprehensive documentation and examples for traceroute feature
+
+## [0.4.0] - 2025-03-10
+
+### Added
+- Mesh networking functionality for decentralized communication
+- Auto-discovery of mesh nodes
+- Message routing through intermediate nodes
+- CLI commands for mesh network operations: `mesh start`, `mesh send`, `mesh info`
+- Ruby API methods for creating and managing mesh networks
+
 ## [0.3.0] - 2025-03-08
 
 ### Added

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    lanet (0.3.0)
+    lanet (0.5.0)
       thor (~> 1.2)
 
 GEM

data/README.md

@@ -19,6 +19,8 @@ A lightweight, powerful LAN communication tool that enables secure message excha
 - **Configurable:**  Adjust port settings, encryption keys, and network scan ranges.
 - **Digital Signatures**: Ensure message authenticity and integrity
 - **File Transfers**: Securely send encrypted files over the LAN with progress tracking and integrity verification
+- **Mesh Networking**: Create resilient mesh networks for decentralized communication, enabling messages to be routed through multiple hops without central infrastructure
+- **Advanced Traceroute**: Analyze network paths using multiple protocols (ICMP, UDP, and TCP)
 
 ## Security Features
 
@@ -301,6 +303,68 @@ Receive encrypted files with signature verification:
 lanet receive-file --output ./downloads --encryption-key "my_secret_key" --public-key-file lanet_public.key
 ```
 
+#### Mesh Networking
+
+Create a decentralized mesh network where devices can communicate even without direct connectivity:
+
+```bash
+# Start a mesh network node
+lanet mesh start
+
+# Start a mesh network node with custom settings
+lanet mesh start --port 5050 --max-hops 15
+```
+
+Send messages through the mesh network:
+
+```bash
+# Send a message through the mesh network to a specific node ID
+lanet mesh send --target a1b2c3d4-5678-90ef-ghij --message "Hello Mesh Network"
+
+# Send an encrypted message through the mesh network
+lanet mesh send --target a1b2c3d4-5678-90ef-ghij --message "Secret mesh message" --key "secret-key"
+
+# Send a signed message through the mesh network
+lanet mesh send --target a1b2c3d4-5678-90ef-ghij --message "Authenticated mesh message" --private-key-file lanet_private.key
+```
+
+View information about your mesh network:
+
+```bash
+# Display information about mesh network connections
+lanet mesh info
+```
+
+#### Tracing the route to a target host
+
+Basic traceroute using UDP (default protocol):
+
+```bash
+# Simple format
+lanet traceroute google.com
+
+# Option format
+lanet traceroute --host google.com
+```
+
+Trace using ICMP protocol:
+
+```bash
+lanet traceroute --host google.com --protocol icmp
+```
+
+Trace using TCP protocol:
+
+```bash
+lanet traceroute --host google.com --protocol tcp --max-hops 15
+```
+
+Customize traceroute parameters:
+
+```bash
+lanet traceroute --host github.com --protocol tcp --max-hops 20 --timeout 2 --queries 4
+```
+
 ### Ruby API
 
 You can also use Lanet programmatically in your Ruby applications:
@@ -393,8 +457,53 @@ file_transfer.receive_file('./downloads', 'encryption_key') do |event, data|
     puts "File saved to: #{data[:file_path]}"
   end
 end
+
+# Mesh Networking
+mesh = Lanet.mesh_network
+mesh.start  # Start the mesh node and discovery service
+
+# Send a message through the mesh network
+mesh.send_message(target_node_id, "Hello through the mesh!", "optional-encryption-key")
+
+# Get info about mesh connections
+puts "Node ID: #{mesh.node_id}"
+puts "Connected to #{mesh.connections.size} nodes"
+mesh.connections.each do |node_id, info|
+  puts "  #{node_id} (#{info[:ip]})"
+end
+
+# Properly stop the mesh node
+mesh.stop
+
+# Trace route to a host with different protocols
+tracer = Lanet.traceroute(protocol: :udp)
+hops = tracer.trace('github.com')
+hops.each do |hop|
+  puts "Hop #{hop[:ttl]}: #{hop[:ip]} - Response: #{hop[:avg_time]}ms"
+end
+
+# Use TCP protocol with custom parameters
+tcp_tracer = Lanet.traceroute(protocol: :tcp, max_hops: 15, timeout: 2)
+tcp_tracer.trace('google.com')
 ```
 
+## Mesh Network
+
+The mesh networking feature provides decentralized communication capabilities:
+
+- **Auto-discovery**: Nodes automatically find each other on the network
+- **Multi-hop routing**: Messages can be routed through intermediate nodes
+- **Self-healing**: Adapts to changing network conditions and lost connections
+- **Store and forward**: Messages persist until they can be delivered
+- **End-to-end security**: Messages remain encrypted across multiple hops
+- **Verification**: Digital signatures ensure message integrity through the mesh
+
+Ideal for:
+- IoT networks where devices may not have direct connectivity
+- Ad-hoc networks without fixed infrastructure
+- Networks requiring high resilience and redundancy
+- Applications needing peer-to-peer communication
+
 ## Configuration
 
 Lanet can be configured with several options: