Thanks Andrew!
Our firewall is set up so a public static IP is answered by the jail/Pound
of 192.168.0.161:80. (NAT/Portforwarding is used.)
Before I broke Pound, Pound would direct the 192.168.0.161:80 request to
the backend of 192.168.0.160:8080, which is the www.xxxxxxxxxxx.com
address.
Please forgive my sloppy description of how Firewall/Jail/Pound does this.
It works well. I've only messed wiith Pound.
192.168.0.161:80 and www.xxxxxxxxxxx.com both return the message:
'Theservice is not available. Please try again later.'
Directly viewed, the backend 192.168.0.160:8080 resolves to the correct
html page,
which indicates Apache is listening fine as per usual.
/usr/jails/proxy.xxxxxxxxxxx.com/usr/local/sbin/poundctl -c /var/run/pound:
0. http Listener 192.168.0.161:80 a
0. Service active (5)
0. Backend PF_INET 192.168.0.160:8080 active (5 0.000 sec) alive
-1. Global services
If the output above is wrong for what should be listed - please suggest how
to correct.
Thanks!!!
-----------------------------------------------------------------------------------------------------------------------
Send big files for free. Simple steps. No registration.
Visit now http://www.nawelny.com
--
To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.
