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

As we moved to another firewall with fewer connectors (PIX 515 -> ASA 5510), I had to prune the network infrastructure a bit, so one of the subnets had to go. Now we've got one piece of hardware that still insists on reaching one of the servers via a hard-coded ip address. It might be a while until I get an update, so I need some tricks to work around that.

Now, as we were waiting for the new firewall, I had a temp Linux server set up, where I could forward any connections originating from one machine to the new address. Somehow I can't manage to do this over the ASDM.

So basically I need the following setup: Treat address old-ip (removed) as new-ip (new address), preferably only on machine rogue-client.

This is on a ASA 5510, IOS 8.2, ADM 6.3.

share|improve this question
Is the rogue client and the server on different network segments? – Zypher Aug 16 '10 at 21:03
Two different interfaces/subnets, yes. – mhd Aug 16 '10 at 21:50

You could try doing a policy NAT (sorry it's been about a year since i've done this so i'm a little rusty)

Something like the following should get you going:

(config)#access-list rougue_box permit host <old_ip>
(config)#static(<pre-nat_int>,<post-nat_int>) <new_ip> access-list rouge_box
share|improve this answer

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.