Closed qq1793228602 closed 1 year ago
This sounds like you need to use bridging and not routing - there was support added for bringing recently
(Unfortunately, the documentation in doc/Bridging.md is currently incomplete but you might find some hints in the thread that added this feature #1044)
On Fri, May 12, 2023 at 01:06:49AM -0700, qq1793228602 wrote:
I am now able to ping the IP of devices on the other party's LAN, and my local tool can also connect. At that time, my tool had a function of scanning devices and using the ARP protocol, which required the MAC address of the link layer. However, n2n is forwarded through a route and seems to not carry it. However, my tool cannot directly search for devices, resulting in the need to manually enter the IP
— Reply to this email directly, [1]view it on GitHub, or [2]unsubscribe. You are receiving this because you are subscribed to this thread. Message ID: @.***>
References
--
Use Linux! @.*
***** O- ***
... why haven't you indolent fleshers transformed the whole galaxy into chocolate?''
Give us time.''
Does the current version support it? I saw a supported version in the Q&A section https://github.com/emanuele-f/n2n/tree/switched_traffic2 But this is v2.4
Yes, the current dev branch contains support for bridging - the fork you found is quite old and is not relevant to the support that was merged into dev.
I am now able to ping the IP of devices on the other party's LAN, and my local tool can also connect. At that time, my tool had a function of scanning devices and using the ARP protocol, which required the MAC address of the link layer. However, n2n is forwarded through a route and seems to not carry it. However, my tool cannot directly search for devices, resulting in the need to manually enter the IP