You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please Note: This "issue" is still being worked on and is also supposed to provide possible solutions and alternatives to get Peer Discovery Working.
Describe the issue
There are many tools which utilize mechanisms like peer discovery to establish a connection between two devices on a local area network (LAN). Use of IPv4 & IPv6 addresses with UDP and TCP protocols is common in that regard.
There are several issues (#395, #421, #446, etc.) regarding Services which use Peer Discovery with the LAN IP Addresses to find other Devices.
The issue: Peer Discovery does not work with gnirehtet:
Clients are within a subnet and not the LAN network the Host Device is in ~ thus both devices cannot "find" each other via peer discovery.
Conclusion: Not being able to use Certain Services to Connect Client & Host Device breaks many workflows!
Describe the Solution you propose
Basically the needed functionality is for Client Devices to get a LAN IP-Address from the Routers DCHP-Server ~ and be in the Local Network of the Router rather than a (encapsulated) Subnet.
Maybe gnirehtet could "register" Clients as "Virtual Network Devices" and make the Host Device (Desktop) look like a switch to the DCHP - Server (which is usually running on the Router nowadays).
Or simply some kind of request forwarding or rerouting to allow Services on Both Devices to find each other.
Would it be possible to implement without much hassle?
The text was updated successfully, but these errors were encountered:
Please Note: This "issue" is still being worked on and is also supposed to provide possible solutions and alternatives to get Peer Discovery Working.
Describe the issue
There are many tools which utilize mechanisms like peer discovery to establish a connection between two devices on a local area network (LAN). Use of IPv4 & IPv6 addresses with UDP and TCP protocols is common in that regard.
There are several issues (#395, #421, #446, etc.) regarding Services which use Peer Discovery with the LAN IP Addresses to find other Devices.
The issue: Peer Discovery does not work with gnirehtet:
Clients are within a subnet and not the LAN network the Host Device is in ~ thus both devices cannot "find" each other via peer discovery.
Conclusion: Not being able to use Certain Services to Connect Client & Host Device breaks many workflows!
Describe the Solution you propose
Basically the needed functionality is for Client Devices to get a LAN IP-Address from the Routers DCHP-Server ~ and be in the Local Network of the Router rather than a (encapsulated) Subnet.
Maybe gnirehtet could "register" Clients as "Virtual Network Devices" and make the Host Device (Desktop) look like a switch to the DCHP - Server (which is usually running on the Router nowadays).
Or simply some kind of request forwarding or rerouting to allow Services on Both Devices to find each other.
Would it be possible to implement without much hassle?
The text was updated successfully, but these errors were encountered: