Making sure routers and firewalls see the package IP, not the nodename IP

[JOHN FONTANILLA]

Hi,

We're logged in a HP-UX v11i machine with MCSG running. When we telnet or ping a router from this box, the routers sees the ping coming from stationary hostname IP instead of the floating IP.

Because of security, our firewalls and routers
only allow the floating IP.

How do I force the router to see the floating IP instead?

Should I just run the command below on the
machine which currently runs the package?

route add [router ip] [floating ip]

Thanks!

JohnF

[Sanjay_6]

Hi John

You should allow the firewall to allow the system ip to pass through. Since the system ip is the contant and the package ip is virtual. hostname is going to return the server name of the system on which the package is running and this hostname resolves to the ip address of the system and not the package.

Hope this helps.

Regds

[melvyn burnard]

The system will always report the fixed or stationary IP Address. The only way you get the relocatable ip address to be shown as the source is if you have a software package that is compiled or configured to bind() to the relocatable address. Tjis would not be visible to the router/firewall, so you will have to change the router/firewall configuration to allow the fixed or stationary ip address as well.

[Mark van Hassel]

Hi,

Try the following as you suggested:

route add host [router ip] [virtual ip]

You can configure this in the package startup script and add a 'route delete' as well offcourse.

[JOHN FONTANILLA]

The company's decided to let both
hostname IP addresses through the
firewall and router.

[Jeff Schussele]

As it should be.

Also we ALWAYS added our virtuals to DNS - so that users could ping the virtuals to determine whether or not the pkg was up.

Saved us a lot of "IS THE PKG UP!!!" calls.

Jeff