I am working on a lab built in EVE-NG, and I am racking my head on why I am unable to ping the outside from the Virtual PC connected to SW1. The "Net" Cloud is actually a NAT cloud within EVE-NG. I am able to ping google and other domains with a source of the e0/1 interfaces on R1 and R2.
Here is the IP addressing scheme.
PC = 10.1.1.50/24
R1 (e0/0) = 10.1.1.1/24
R1 (e0/1) = DHCP Assigned Address
R2 (e0/0) = 10.1.1.2/24
R2 (e/01) = DHCP Assigned Address
The three interfaces on the switch (e0/0, e0/1,e0/2) are all part of VLAN 10.
From the PC, I can ping R1, R2, the Virtual Router (10.1.1.254/24). This particular IP address is set as the default gateway for the PC and should remain the same no matter if R1 or R2 becomes the main router.
R1 is configured as Active with a priority of 200 and preemption configured.
R2 is in standby mode and is set to take over if R1 were to fail.
I want the switch to act as an L2 access switch and not as an L3 routed switch. I did not turn on IP routing because of this.
Should I be focusing on a routing protocol to get out to the outside? I feel like that is not necessary since everything on the inside in within the same VLAN.
