I posted this a while ago and thought I would try again as it has again become an issue and I still have no solution. I'm trying to run Loggernet V4.2 within an intranet that has a web proxy server and where the only open ports are 80 and 443. I have changed the ports used by our remote CR1000 loggers to 443 for LoggerNet/Pakbus and kept 80 for html. Within the intranet a browser with the proxy server settings can see the remote loggers but as proxy settings can not be set within LoggerNet, Loggernet can not communicate with the remote loggers with IP modems and or the RF Modems hanging off them. A sort of workaround was to try just to use html which works for the loggers with IP modems but not for the loggers within the associated RF networks. We have found a few OS hacks, software to redirect web traffic and work around's but the IT department is not overly keen on those solutions.
Is CSI looking at adding proxy server capability to Loggernet in future versions? If not any work around for this would be appreciated.
What about running Loggernet on a cloud server?
There are various types of proxy servers and many of them deal specifically with HTTP (Squid is an example of this). Depending on the type of proxy being used, you may be able to accomplish what you need using generic modem scripts. However, in order to answer your question fully, we would need to know the specific type of proxy server that needs to be negotiated.