It's most likely not Apache httpd... which is why it's not already on
port 80. He's probably using Apache Tomcat, which listens on an
alternate port (8080) to not conflict with a concurrently running Apache
httpd on port 80.



On Thu, 2008-08-07 at 11:07 -0700, James G. Sack (jim) wrote:
> Michael J McCafferty wrote:
> > All,
> >     I have a customer that we are redirecting inbound connections to port
> > 80 to port 8080 for him, using our equipment in front of his servers.
> > However, that equipment is being replaced and the the same functionality
> > is not going to be available on the new gear.
> >     The customers OS is CentOS 5. I need to make the correct iptables rules
> > on his servers to do this on each host instead of putting something in
> > front of his servers to do it... 
> 
> At the risk of sounding stupid, why don't the individual servers that
> want to receive inbound port 80 just configure their apache(?) to listen
> on 80?
> 
> >..Do I really need to do NAT on the local
> > servers to make this work ? I have been using PF on BSD for firewalls
> > for so long, I think I do not know what I need to do on the RedHat box
> > to make this redirect happen.
> > 
> > In PF it's just:
> > rdr on $public proto tcp from any to <customer-IP> port 80 ->
> > <customer-IP> port 8080
> > 
> > How do I do it in RedHat ? All of the docs I can find seem to discuss
> > how to do it as a network firewall. 
> > 
> 
> Regards,
> ..jim
> 
> 
-- 
************************************************************
Michael J. McCafferty
Principal, Security Engineer
M5 Hosting
http://www.m5hosting.com

You can have your own custom Dedicated Server up and running today !
RedHat Enterprise, CentOS, Ubuntu, Debian, OpenBSD, FreeBSD, and more
************************************************************


-- 
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to