RE: routing problem

[Jason Staudenmayer]

Title: Message

Why not setup an IP alias on the firewall for 62.17.173.10 and then have your iptables/ipchains forward all traffic to the internal server. -----Original Message----- From: Lisa [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 29, 2003 1:15 PM To: [EMAIL PROTECTED] Subject: routing problem Hi,   If anyone out there can help me with this I'd be extremely grateful..   I have a firewall with external ip 62.17.173.173 The gateway is 62.17.173.254   We have a machine inside the firewall with private ip addresses. I need to have a setup where this machine is visible to the outside world on the external ip address 62.17.173.10 ( there is no physical machine with this ip address, its a virtual ip address). At the moment I have a rule in my firewall that sends any packets destined for ip address 62.17.173.10 to the internal webserver.   The problem is that when packets come destined for this ipaddress they get lost. When I did a trace route on the 62.17.173.10 ip I got as far as the gateway address 62.17.173.254 and no further. Is there some other configuration that I need to do to get the packets destined for 62.17.173.10 to go through my firewall and onto the rulebase to divert the packets to the internal machine?   Thanks Lisa