I think you are missing the point of why people want to have this feature. Also, I don't think you really understand how remote connections to your HAVA device actually work. The way remote viewing works is:
- You specify a HAVA Name/ID and password for your HAVA device
- That Name/ID and password (?) are stored on a server that is maintained by Monsoon
- Your device periodically contacts the Monsoon remote viewing server to update its information
- Upon connection, the HAVA software connects to the server to determine where the actual device is located physically.
Essentially, this just equates to a proprietary form of DDNS, however that is how remote connections to a HAVA device work (to the best of my knowledge).
However, the problem doesn't just relate to remote viewing. There are plenty of other reasons why someone would want to have direct access to our HAVA devices. For one, this would give you the ability to have more than one HAVA on your network. For another, it could help fix issues MANY people are having related to the HAVA device not being detected locally by the HAVA software. Additionally, someone may not necessarily want to rely on Monsoon to maintain the servers that map device names/ids to IP addresses for remote viewing. Imagine the problems that would arise (say for example in HAVA HOSTING's situation) if those servers were to go down. These are just a few reasons I came up with off the top of my head for adding direct access through IP.
Reference these topics I set up multiple HAVAs and multiple Set Top Boxes on one lan.