A TCP NAT test carried out from the classic UI is always successful for me, whereas one done from the web interface always fails for me. Does this mean that the entries automatically added to Win7's firewall for Oneswarm during installation aren't enough for the web interface?
Also, a warning popped up on my desktop saying I need to check my 44074 UDP port as it's needed for decentralised tracker, but I'm not sure exactly which one of the two interfaces sent it. As there's no way to test for UDP in both classic UI and web interface, I was wondering what to make of the warning: is it safe to assume the web interface sends out the warning because it is as unable to detect UDP port openness as it is to detect the TCP one's, and everything is alright with my setup?
NAT problems or bug?
(4 posts) (3 voices)-
Posted 1 year ago #
-
I have the exact same "problem".
I dont know if it actually is a problem but its annoying that the web gui nat test always fails. classic ui nat test is successfull.Anyone knows what why the weg gui test dont go through?
Posted 1 year ago # -
This is a bug with the nat checker.
https://github.com/CSEMike/OneSwarm/issues/66Posted 1 year ago # -
Ok good to know. Thank you isdal!
Posted 1 year ago #
Reply
You must log in to post.