Thanks for the response!
I get why the FW works as its doing the routing for you between the FLAT, and the internet. I do not want to add a device to this set up however. I want this to be solely on my MAC.
If I point my default on IOS-V to gi0/0 I can hit the the default gateway of the VIRL VM - 192.168.56.2, but no further... This is with the FLAT NIC on the fusion VIRL VM modified to NAT
Alternatively, when I have the FLAT NIC on the fusion VIRL WM set to custom custom, and enable vmnet3 (172.16.2.0/24), or vmnet2 (172.16.1.0/24) with the following settings, I can hit the GW of the VIRL VM - 192.168.56.2, but no further...
Again, I don't want an external device to bridge this network to allow for external connectivity. I just want reachability with the following flow:
IOS-V > FLAT > VIRL VM > MAC > Internet
I'm out of ideas, and thoughts from anyone would be appreciated!
So you want you workstation (MAC) to be the device to get out to.
First the static routing table are all the device address I use in VIRL.
Internal2 is 172.16.1.1, the device address that is next hop for VIRL to the real world.
172.16.1.203 is FLAT-1. The Static routes next hop back into VIRL
On the router connect to flat-1
ip route 0.0.0.0 0.0.0.0 172.16.1.1 (this is the next hop out to the real word)
ipv6 route ::/0 fd00:172:16:1::1 (IPv6 version of next hop to real world
So you need to setup your static routes on your computer to work the same way as my router. Then you need to use your IP address of your computer for the two static routes on the router connected to flat-1
OK, so I got this working.... After looking at the VMWare fusion VMNET2|3 respectively I realized the gateway needs to be .2 in order for the NAT to work, along with one other order of operation...
Here is what I did:
1. reinstalled the VIRL OVA (this time with 1.5)
2. once up, and VIRL was activated with the correct key
3. I then edited the shared FLAT1|2 with a host of .1, and a gateway of .2, and then applied the changes
4. I then started the simple simulation (one IOS-V, and one external FLAT), and enabled both interfaces with DHCP
#int range gi0/0-1
# ip addr dhcp
Now the router can ping external INET addresses like 220.127.116.11
With all this said, I also upgraded my VMWare fusion pro to 8.5, apparently their is a NAT mapping issue in previous releases...