Open LateJunction opened 5 months ago
I have Warpinator running successfully on Mint 21.3 and Windows 10.
Mint Warpinator version 1.8.3 Windows 10 Warpinator version 0.1.2
I had a couple configuration items I needed to solve (which unfortunately I do not recall), but it works.
I don't have Warpinator running successfully on Mint 21.3 and Windows 10.
Mint Warpinator version 1.8.3 Windows 10 Warpinator version 0.4.1.0
Which is the more relevant statement?
Not sure, but can you guess why I suddenly don't care?
Distribution
Mint 21.3
Package version
1.8.3
Frequency
Always
Bug description
Warpinator on Mint connects for bidirectional transfers with Warpinator on MX but cannot 'see' Warpinator on Win10 (neither can Warpinator MX). Windows Warpinator cannot see either Mint or MX Warpinator. All versions are using the same groupcode and transfer/authentication settings. Mint and MX use identical ufw rules. Windows Defender Private Firewall rules appear to implement the same filters as ufw.
This looks to me like a Win 10 networking issue that is specific to one particular Windows PC on my private network but I do not see a place to report Windows Warpinator issues other than here.
Steps to reproduce
To reproduce this issue one would have to use my Windows 10 PC, otherwise I cannot be sure that you have an identical configuration in which Warpinator is running. I am using Warpinator version 0.4.1.0 downloaded from GitHub. Installing and configuring Warpinator with my GroupCode and port numbers is all that is required to reproduce this failure in Mint Warpinator, which reports 'No other computers found' (assuming the MX linux PC is off-line). Windows Warpinator reports 'No devices found'.
Running 'warpinator --debug' from a Windows command line produces absolutely no diagnostic data whatsoever. The log from running this command under Mint is attached as a file in 'Additional Information'
Expected behavior
Warpinator Mint should see Warpinator Windows and vice-versa
Additional information
warpinator log LJ 240202_2041.txt