Natting

[avicapri]

There is project specific setup .

I have created 3 vlans in 3560-L3 switch .Vlan 2 has the ip adrress 172.28.30.2/24, Vlan 3 - ip address 172.24.242.2/23 & Vlan 143 - ip address 10.117.143.4 .

Vlan 143 also exsists on the core switches , which is used for uplinks between L3 & Cores .

query is as 3560 does not support natting , i have natted 172.28.30.0/24 & 172.24.242.0/23 to 10.117.143.5 in the core switches , DOES THIS WORK ?

NATTING CONFIG IN THE CORE

ip nat pool CORP 10.117.143.5 10.117.143.5 netmask 255.255.255.0

ip nat inside source list 1 pool CORP

access-list 1 permit ip 172.28.30.0 0.0.0.255 any

access-list 1 permit ip 172.24.242.0 0.0.0.255 any

access-list 1 permit ip 172.24.243.0 0.0.0.255 any

[vijayasankar]

Hi Avinash,

Can you please explain more on whether this a overload NAT scenario or one to one NAT scenario?

Also explain you scenario in detail and why you are doing the NAT, to understand what you are trying to acheive.

Generally, All you need to the ensure is the forward and return traffic transit via the same core, where you have configured the NAT, for the translations to happen properly.

Hope this helps.

-VJ

[avicapri]

Yes its overload NAT.

172.X.X.X is clients specific subnet. Here we have 10.116.X.X 255.254.0.0 subnets for our corporate access , so NAT is required .