easyfind. public IP vs NAT

7 posts / 0 new
Last post
vchakravarthy
easyfind. public IP vs NAT

Hi,

we are using easyfind with virtualhere package installed on synology. our remote clients with public IP are connecting with easyfind without any issues. but remote clients behind a nat gateway are unable to connect. is there any specific port we have to open for this to work?

Michael
.

Easyfind works through NAT's but won't work through good firewalls, so it might be a firewall issue. UDP 443 is used for easyfind

vchakravarthy
Thank you Michael,

Thank you Michael,
if I have to whitelist the easyfind server along with UDP 443, which IPs should I use?

vchakravarthy
quick update.

quick update.
opened UDP/443 bi-directional for 0.0.0.0/0. Still cannot see USB Hub

Michael
.

OK something is blocking it e.g mutliple levels of NATs some of them symmetric (e.g https://dh2i.com/kbs/kbs-2961448-understanding-different-nat-types-and-h...) , so it looks like you will have to use a relay.

VirtualHere easyfind wont support relays (they are too slow) but try something like zerotier instead of easyfind. (That will use a relay if it cannot connect direct). It will be slow so it depends on what you want to pass through .If its just e.g a licensing dongle it should be ok. If its something else e.g like a disk or serial device you will need to just directly open tcp 7575 to allow direct communications

vchakravarthy
we use aws NAT gateway and

we use aws NAT gateway and they are symmetric. and zerotier may also not work ( https://zerotier.atlassian.net/wiki/spaces/SD/pages/31358977/Common+AWS+... ) with symmetric NAT

Michael
.

It will work, but it will use a relay. I havent bothered adding relays to easyfind because its just too slow. There is an extra hop and data copy for every single data packet.

Log in or register to post comments