The routing should be the same ... you just pick another port ... one instead of 80 and route that to the internal box. I am assuming though that you would have to have the website listed in the name servers as something like ... 200.10.5.20:port .... so that when someone typed in the website name it would route through your firewall to the proper machine behind the firewall. I have not done it for web page servers, but a while back I did it so I could access an internal machine with ssh without having to stop at the router/server and then sshing to the next machine. Maybe this won't work for you ... but it is a thought. Randy ----- Original Message ----- From: "johnnyfulcrum" <johnnyfulcrum at mn.rr.com> To: <tclug-list at mn-linux.org> Sent: Monday, July 26, 2004 10:20 AM Subject: [TCLUG] multiple (physical) webservers behind a firewall > I've been using IPCop as a firewall at home, and have been able to route > web traffic to a box in the DMZ. Now I have multiple web servers running > on different boxes and need to route throught the firewall - IPCop seems > to be able to redirect to just one box (port 80). Is there a firewall > solution that allows me to route web traffic many physical boxes behind a > firewall? > > thanks > johnnyf > -- > Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > Help beta test TCLUG's potential new home: http://plone.mn-linux.org > Got pictures for TCLUG? Beta test http://plone.mn-linux.org/gallery > tclug-list at mn-linux.org > https://mailman.real-time.com/mailman/listinfo/tclug-list > _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota Help beta test TCLUG's potential new home: http://plone.mn-linux.org Got pictures for TCLUG? Beta test http://plone.mn-linux.org/gallery tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list