Yes, I get that, but it seems useless in this case. I mean you specify the the start and stop address so what does it matter what the prefix is?
For instance these all do the same thing right?
ip nat pool ovrld 172.16.10.1 172.16.10.1 prefix 24
ip nat pool ovrld 172.16.10.1 172.16.10.1 prefix 25 ip nat pool ovrld 172.16.10.1 172.16.10.1 prefix 26 ip nat pool ovrld 172.16.10.1 172.16.10.1 prefix 27
I don't know. I thought it'd have something to do with the routing table or CEF or something but I just threw a config together and it didn't affect that stuff at all.
Yes, I get that, but it seems useless in this case. I mean you specify the the start and stop address so what does it matter what the prefix is?
For instance these all do the same thing right?
ip nat pool ovrld 172.16.10.1 172.16.10.1 prefix 24
ip nat pool ovrld 172.16.10.1 172.16.10.1 prefix 25 ip nat pool ovrld 172.16.10.1 172.16.10.1 prefix 26 ip nat pool ovrld 172.16.10.1 172.16.10.1 prefix 27
Yes, I get that, but it seems useless in this case. I mean you specify the the start and stop address so what does it matter what the prefix is?
Just off the top of my head... if your NAT'ing to the internet, wouldn't it be useful to know the network/broadcast addresses of the subnet you are on?
Just off the top of my head... if your NAT'ing to the internet, wouldn't it be useful to know the network/broadcast addresses of the subnet you are on?
Yes and those are defined on the interface itself. The NAT pool simply defines a pool of addresses to use for the translation. Since you define the start and stop points of that, it just seems like the prefix is unnecessary. There may be some use for it that I am not aware of though.
At a guess, if the address has a prefix, it could then be filtered with a prefix-list. I'm not sure if thats definitely the case, but its possible I guess.
Yes and those are defined on the interface itself. The NAT pool simply defines a pool of addresses to use for the translation. Since you define the start and stop points of that, it just seems like the prefix is unnecessary. There may be some use for it that I am not aware of though.
Here you go!
The required netmask (or prefix) parameter performs a kind of verification check on the range of addresses. If the address range would not be in the same subnet assuming the configured netmask was used, then IOS will reject the IP NAT POOL command.
The required netmask (or prefix) parameter performs a kind of verification check on the range of addresses. If the address range would not be in the same subnet assuming the configured netmask was used, then IOS will reject the IP NAT POOL command.
Nice find. Still odd in my book, but good to know.
Comments
For instance these all do the same thing right?
ip nat pool ovrld 172.16.10.1 172.16.10.1 prefix 24
ip nat pool ovrld 172.16.10.1 172.16.10.1 prefix 25
ip nat pool ovrld 172.16.10.1 172.16.10.1 prefix 26
ip nat pool ovrld 172.16.10.1 172.16.10.1 prefix 27
http://www.mashtronauts.com
hmmm.....not you've got me thinking.....
Just off the top of my head... if your NAT'ing to the internet, wouldn't it be useful to know the network/broadcast addresses of the subnet you are on?
Yes and those are defined on the interface itself. The NAT pool simply defines a pool of addresses to use for the translation. Since you define the start and stop points of that, it just seems like the prefix is unnecessary. There may be some use for it that I am not aware of though.
http://www.mashtronauts.com
CCIE Progress - Hours reading - 15, hours labbing - 1
Here you go!
The required netmask (or prefix) parameter performs a kind of verification check on the range of addresses. If the address range would not be in the same subnet assuming the configured netmask was used, then IOS will reject the IP NAT POOL command.
Nice find. Still odd in my book, but good to know.
http://www.mashtronauts.com
Well it's very interesting, I suppose the range has to be within a subnet. Sounds like it can't crossover to another network.