Haiku Trouble with remote access

whumphrey

Member
Hello,
I have an OmniPro II and Haiku installed on my iPhone.  I have haiku successfully working from within my local network using a wifi connection.  I want to use Haiku remotely though via LTE.
I have set up a dynamic DNS and can successfully get to my routers outside public IP via the assigned host name.  In the router I have forwarded port 4369 (kept default port in OmniPro for now) to the OmniPro IP address. 
 
Final step was to edit controller connection in Haiku to address of my DDNS host name.  Everything else remains the same....port number, private keys, etc.
 
But....I get connection failure.
 
Is there more to it than this?  I'm also confused how it would ever work without the OmniPro having a default gateway IP address.  Doesn't it need this to know it's return path back to router?
What can I do to test if port forwarding is working correctly?
 
Thanks,
Warren
 
 
 
One more bit if info....when I try to connect via hostname with PC Access it get a "connection refused" error.
Thanks.
 
When you're getting this connection error, have you turned off wifi to ensure you're testing off-net?  Some home routers (and most enterprise routers) won't allow you to connect using the WAN IP when you're on the LAN - meaning it may work with wifi off via the cellular network using www.myhost.com but not when you're on your wifi - the wifi often requires you use the internal IP. 
 
This has some names like NAT Loopback, NAT on a stick, etc... basically the firewall prevents it.
 
Thanks Work2Play.  That was exactly the problem.  Once off wifi and on LTE it works fine.  As work around I will have to create two separate profiles in haiku app.
 
I am using a netgear WNDR3700 and it must allow it. I have never run into this issue.
 
One difference that might be helping is that I set up my dynamic (DynDNS) right into the router itself.
 
If your router allows this you might wish to give it a try. I would think it would be a hassle having two profiles.
 
Joe
 
Netgear has always been very friendly with the NAT loopback; other routers make it very difficult.  Even enterprise-class routers make it quite a pain (Cisco and the like).  Often times it's easier to have different DNS entries on the internal network.
 
Back
Top