GNS3-Topology: ACL Test Lab for ACLs and NAT/PAT
Written by LBSources from http://www.gns3-labs.com on October 15th, 2009 | 2 Comments“Hello World!’ - Hey so it’s been while since posting last and some things are getting back to normal since the move. One of them is my office
Very happy about that! One thing that has not gotten back to normal is routine studying - I’m so far behind from my goal - but I do have 2 months before the year is out to complete the BSCI - Don’t know if I can do it though. I’m just not in the zone. Well anyway, here is a lab I’ve been meaning to put together to share with you all. It’s a lab involving NAT/PAT and Overload .. Sean shares this with us.
I setup this lab up to help me better understand ACLs (Standard, Extended, Dynamic, and Reflexive) and NAT’ing (e.g. Overload, Dynamic, and Static).
The IOS used is a 3640 version 12.4. The special topic about this lab is I did this on a Mac Book Pro and used the TAP/TUN drivers to attach my MBP into the simulation. So this config requires that GNS3 be run as root (e.g. sudo) in order to allow the TAP device to be created. Information on the TAP/TUN drivers for OS X can be found here:
Sean
Thanks for the lab dude! You too can share labs - You can either create a post here on the site with your lab and send all files necessary to the lab to postmy AT gns3-labs.com. You can also skip posting it and just send all files necessary to the lab to postmy AT gns3-labs.com. Thanks to all the help from contributors like Sean - you call help keep this site going!
Routers Used: 3640
IOS: c3640-ik9o3s-mz.124-25b
Feature of Topology: Static NAT, Dynamic NAT, Overload NAT, Network Address Translation (NAT), Port Address Translation (PAT), Access Control Lists
Image: 
Download: GNS3-Labs-ACL Test Lab for ACLs and NAT-PAT By Sean
Cheers!
LB
6,232 viewsTags: 3640, Access Control List, Dynamic NAT, GNS3 Topology, Network Address Translation, Overload NAT, PAT, Port Address Translation, Static NAT









October 16th, 2009 at 5:04 am
hello,
could you please share a simple tpology (4 routers max) where nat overload is implemented and working. I have tried it on several router platforms, it just doesn’t work.
exemple:
R1——R2——-R3——–R4
nat is implemented on R2
eigrp is emplemented on R3,R2,R4 and the network linking R1 and R2 is not advertised. default route on R1 (pointing towards R1)and R2 (pointing towards R3)
when I try to ping R3 from R1: nothing
when I use an extended ping from R2 with ping source as the interface facing R1, the access-list is hit, ping to R4 is successful ,and i can see nat translations and statistics.
I am not asking how to configure NAT, the question is: is nat supported on GNS3. static NAT works fine
November 2nd, 2009 at 6:48 am
Good Post! Have you also tested ASA on Qemu particularly latest code v8.2 ?