LAN with 2 modem routers, one as a repeater for both the WiFi (2.4 Ghz and 5GHz) and hard wired ethernet connections with 3 Linux MInt systems and 2 Android phones. The primary modem is the DNS server for the LAN and the connection to the internet. ALl IPs are 10.0.0.x and warpinator on each device uses the same group code. 2 of the Linux boxes are usually connected by hard wired ethernet to the LAN and 1 by WiFi and the phones by WiFi. I can also connect the 2 hardwired linux boxes by WiFi.
If everything is running on WiFi I have no issues, Warpinator on all devices sees all other devices and transfers work fine. If my two Linux boxes are connected only via the hard wired ethernet, they cannot see each other or devices connected by WiFi and cannot initiate transfers. I have manually selected the hardwired interfaces in Warpinator on both the hardwired Linux boxes in Preferences when I have had them connected only by the ethernet interfaces with WiFi interfaces disabled. This only seems to have started occurring around 6 months ago. All Linux boxes have UFW setup to allow Warpinator through and all can ping each other on all interfaces.
I can obviously just run everything on WiFi, but I have occasional reasons for preferring the hardwired connection. I don't remember this being a problem when I first started using Warpinator around2 years ago but it is possible that both the ethernet and Wifi connections were both enabled and Warpinator may have been using the WiFi. Is this expected behaviour?
Steps to reproduce
No specific steps. It was happening when Auto selection of the network interface was enabled and when the hardwired ethernet interface was manually selected in Warpinator on both devices. If the WiFi interface was manually selected then Warpinator worked fine on all devices.
Expected behavior
I would expect that Warpinator should see all devies on my LAN irrespective of whether they are connected by ethernet or WiFi.
Distribution
Mint 21.3
Package version
1.8.3
Frequency
Always
Bug description
LAN with 2 modem routers, one as a repeater for both the WiFi (2.4 Ghz and 5GHz) and hard wired ethernet connections with 3 Linux MInt systems and 2 Android phones. The primary modem is the DNS server for the LAN and the connection to the internet. ALl IPs are 10.0.0.x and warpinator on each device uses the same group code. 2 of the Linux boxes are usually connected by hard wired ethernet to the LAN and 1 by WiFi and the phones by WiFi. I can also connect the 2 hardwired linux boxes by WiFi.
If everything is running on WiFi I have no issues, Warpinator on all devices sees all other devices and transfers work fine. If my two Linux boxes are connected only via the hard wired ethernet, they cannot see each other or devices connected by WiFi and cannot initiate transfers. I have manually selected the hardwired interfaces in Warpinator on both the hardwired Linux boxes in Preferences when I have had them connected only by the ethernet interfaces with WiFi interfaces disabled. This only seems to have started occurring around 6 months ago. All Linux boxes have UFW setup to allow Warpinator through and all can ping each other on all interfaces.
I can obviously just run everything on WiFi, but I have occasional reasons for preferring the hardwired connection. I don't remember this being a problem when I first started using Warpinator around2 years ago but it is possible that both the ethernet and Wifi connections were both enabled and Warpinator may have been using the WiFi. Is this expected behaviour?
Steps to reproduce
No specific steps. It was happening when Auto selection of the network interface was enabled and when the hardwired ethernet interface was manually selected in Warpinator on both devices. If the WiFi interface was manually selected then Warpinator worked fine on all devices.
Expected behavior
I would expect that Warpinator should see all devies on my LAN irrespective of whether they are connected by ethernet or WiFi.
Additional information
No response