Meshnet Device IP Conflict Resolution via Alternate Address Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In mesh networks, conflicts arise when subnet IP addresses assigned to different local area networks overlap, leading to inadvertent packet transmission and resource inefficiency, as meshnet devices struggle to communicate with intended devices due to identical IP addresses, resulting in delays and resource wastage.

Innovation Solution

An external meshnet device receives connection information from multiple meshnet devices, calculates IP address ranges, identifies conflicts, and maps alternate IP addresses to resolve these conflicts, enabling efficient communication by using the alternate addresses instead of the conflicting subnet IP addresses.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If meshnet devices use subnet IP addresses for communication, then communication capability is enabled, but IP address conflicts cause packet transmission errors and communication failures

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidIP address conflict
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The patent introduces an intermediary mechanism where meshnet devices share connection information about their respective LANs, including subnet IP address ranges. This intermediary data exchange enables devices to detect potential IP address conflicts before attempting communication, allowing the system to prevent harmful packet transmission by identifying and avoiding conflicting addresses.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary action by having meshnet devices calculate and compare subnet IP address ranges in advance, before actual data transmission occurs. By performing this detection and conflict identification step beforehand, the system prevents IP address conflicts from causing packet transmission errors, ensuring reliable communication from the outset.

Inventive Principle:
Principle #10Preliminary action

2Ease of manufacture

If meshnet devices dynamically self-organize, then installation overhead is reduced and workload distribution is improved, but IP address conflicts still occur across different LANs

Engineering Contradiction:
Improveinstallation overheadVSAvoidcommunication reliability
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where meshnet devices continuously share connection information about their LAN configurations. This feedback loop enables devices to detect when IP address ranges overlap across different LANs, allowing the self-organizing system to adapt and resolve conflicts dynamically while maintaining the ease of installation and workload distribution benefits.

Inventive Principle:
Principle #23Feedback

3Speed

If meshnet devices transmit data without IP conflict detection, then communication speed is maintained, but packet retransmission and resource wastage occur

Engineering Contradiction:
Improvecommunication speedVSAvoidresource wastage
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

The patent performs preliminary IP address range calculation and conflict detection before data transmission begins. By conducting this detection step in advance using connection information shared between meshnet devices, the system identifies potential IP conflicts early, preventing packet retransmission and the associated resource wastage while maintaining efficient communication speed.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20240396865A1Optimizing access to local network devices via mesh network devices
Publication Date: 2024.11.28 UAB 360 IT
  • US20240396865A1 patent drawing
  • US20240396865A1 patent drawing
  • US20240396865A1 patent drawing

AI summary

A method, in an external meshnet device in communication with a first meshnet device and a second meshnet device, includes determining, based on comparing (i) a first range of first subnet IP addresses associated with a first LAN connected to the first meshnet device and (ii) a second range of second subnet IP addresses associated with a second LAN connected to the second meshnet device, a conflict that a first subnet IP address assigned to a first LAN device in the first LAN is the same as a second subnet IP address assigned to a second LAN device in the second LAN; mapping, based on determining the conflict, an alternate IP address to correspond with the first subnet IP address; and communicating with the first LAN device based on utilizing the alternate IP address instead of the first subnet IP address is disclosed. Various other aspects are contemplated.