NAT - extendable keywords aren't added when natted to interface

From: nhatphuc (nhatphuc@gmail.com)
Date: Sat Feb 09 2008 - 09:38:12 ARST

• Next message: Fawaz Habeeb: "CIFS"
• Previous message: nagendra kumar: "Error messages seen in switches"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi Group,

When I configure static nat to an IP address, IOS add extendable keyword
automatically:

Rack1R5(config)#do sh run | in static
ip nat inside source static tcp 173.1.5.100 25 192.10.1.5 25 extendable
ip nat inside source static tcp 173.1.5.100 80 192.10.1.5 80 extendable
ip nat inside source static tcp 173.1.5.100 110 192.10.1.5 110 extendable
ip nat inside source static tcp 173.1.5.100 443 192.10.1.5 443 extendable
Rack1R5(config)#

But When I configure static nat to interface, IOS doesn't add the keyword:

Rack1R5#sh run | in static
ip nat inside source static tcp 173.1.5.100 110 interface FastEthernet0/0
110
ip nat inside source static tcp 173.1.5.100 25 interface FastEthernet0/0 25
ip nat inside source static tcp 173.1.5.100 443 interface FastEthernet0/0
443
ip nat inside source static tcp 173.1.5.100 80 interface FastEthernet0/0 80
Rack1R5#

Do they work the same? Why IOS doesn't add extendable keyword in 2nd
scenario?

Thanks

Phuc

• Next message: Fawaz Habeeb: "CIFS"
• Previous message: nagendra kumar: "Error messages seen in switches"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Sat Mar 01 2008 - 16:54:48 ARST