Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The Client, running Suse 10. The Server, also running Suse10, and is a Cluster with a float IP. Now there is a problem about the echo communication:

Client send echo request server's float IP, and The Server reply to the Client with th source IP as its physical IP. and Firewall bock the relpy because the source IP changed.

I need the Server reply echo with its source IP as float IP. How to do that?


share|improve this question

Then you have some seriously strange configuration. IP stacks typically send replies with the exact same source IP as the IP the original package was targeted at. Else you will not be able to have any IP communication at all, as the communication partner can not match the connection.

You probably have some loadbalancing solution which adapts IP packages (like LVM). These can be rather delicate to configure. But on your sparse information, we can not really decide what's wrong.

share|improve this answer
thanks you relpy. The server side is installing veritas cluster server. so there are float ip and its physical IP. When server sending relpy, it use the physical IP as source IP. – Mingo Mar 8 '11 at 12:15

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.