Hi John,
There are a lot of ways to handle this. At 3dicc we did a major rewrite of all of this for Terf so this is mostly from memory. Have a look at ReWrite rules on OpenQwaq-http.conf in /etc/httpd/conf.d.
You can tell the server to forward other ports to 1234 internally. You can also adjust OpenQwaq-iptables or manage forwarding with a hardware firewall.
We did have some objections to 1234, but after our rewrite we use TLS for encryption, we stopped having questions about 443 since its standard purpose generally is for TLS traffic. We did that work for the US Army but it allowed us to significantly increase performance and scale.
Things do get a bit more complicated when you add additional severs. And even more complicated when you have multiple service providers.
All the best,
Ron Teitelbaum
Head Of Engineering
3d Immersive Collaboration Consulting
Follow Me On Twitter: @RonTeitelbaum
--
You received this message because you are subscribed to the Google Groups "OpenQwaq Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openqwaq+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Sebastian,
The 9991 port is an internal port for servers to talk to each other. External connections only require the client get to the external port 1234, 443 or 80. (although 999n ports need to be open and accessible to internal or local connections).
All the best,
Ron Teitelbaum
Head Of Engineering
3d Immersive Collaboration Consulting
Follow Me On Twitter: @RonTeitelbaum