RE: [suse-security] OWA with squid 2.5 stable6, problem with connect
-----Original Message----- From: edwin [mailto:edwin@nsi.co.id] Sent: Wednesday, March 23, 2005 3:31 PM
I implement same thing with no problem. What is firewall you use? Before go to squid.conf I think better to check the firewall.
firewall is ok
ifconfig eth0:1 your_external_IP_but_different_from_proxy_IP
after that you should forward all the request to your_external_IP_but_different_from_proxy_IP port https port forward it to your internal_OWA_IP port 80 or 443, set this on your firewall configuration
u meen nat right ? think thats my last problem now. i can enter username and password but after that i get redirected too the private ip, funny, private ip on the net. but nat isnt the way i want to go, if i handle it that way no squid needed and its a direct access to the internal lan. isnt there any other way ? or im complete wrong ?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dörfler Andreas wrote:
firewall is ok
u meen nat right ? think thats my last problem now. i can enter username and password but after that i get redirected too the private ip, funny, private ip on the net.
but nat isnt the way i want to go, if i handle it that way no squid needed and its a direct access to the internal lan. isnt there any other way ? or im complete wrong ?
AFAIK, if you want to access the OWA from internet you should publish it (it's MS terminology), means you should give it an unique public IP. Are you sure that the traffic passes through your firewall to OWA server? If you forward the request from https://host.domain.tld/ to your internal OWA http port, you have to make port forwarding and it is not squid job I think. Edwin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCQZxlkaMcq796kjoRAhq3AJ9RdE7pkkfaQVmp3npKuvWRb4NDtQCeOFZh WPm3TAtF2ToteVSU/TtcaGE= =35G8 -----END PGP SIGNATURE-----
participants (2)
-
Dörfler Andreas -
Edwin