static NAT on a subnet

[Cooky]

So far I've only done one to one static NAT for our servers.
Until today, when I'm studying for CCSP, the study guide has this example:
static (inside, outside) 192.168.100.0 10.1.100.0 netmask 255.255.255.0

How does that work?
Does 192.168.100.1 map to 10.1.100.1 or whichever's available in the "pool"?

 

[Cooky]

Anyone?

 

[jlazzaro]

statics are a one to one translation, so there is no "pool" per say.

192.168.100.1 > 10.1.100.1
192.168.100.2 > 10.1.100.2
...
192.168.100.254 > 10.1.100.254

wierd example though, in the real world you would use a nat statement for local inside to global outside, not a static.

http://www.cisco.com/en/US/products/sw/...chapter09186a00801cd841.html#wp1026694

 

[James Bond]

Thats a weird example.

Router(config)#ip nat inside source static tcp 192.168.1.100 80 131.107.2.200 80

 

[spyordie007]

static (inside, outside) 192.168.100.0 10.1.100.0 netmask 255.255.255.0

It's been a while since I've done a lot of work on PIXes, but I believe that statement will translate the whole network to a single address. What you want is simply:
static (inside, outside) [outside-IP] [inside-IP]
than make sure to apply an ACL allowing whatever protocols/ports back that you need.

http://www.cisco.com/en/US/products/hw/...oducts_tech_note09186a0080094aad.shtml

Erik

 

[Cooky]

Thanks for everyone's replies; jlazzaro's is what I was looking for.