Support and News Forum

Hello guys, first of all you in advance for any idea about my problem...
~My goal: It is to connect my eve-ng topology with my real "lan", full access.. from my lan to eve and eve to my lan..
-What I did: I tried first doing nat from my eve-ng router to my real lan, but after talking with some guys, I realized that maybe nat is not net, so now I just have a router in eve-ng that connect to my lan"192.168.0.0" and that has a internal lan of "10.0.100.0"
Now from my vpc I am able to ping my real pc.. and from my real pc I am able also to ping my vpc.. Bun from my real pc I cant ping the V_ROUTER "10.0.100.254" for example.. and I have a static route in my pc to the network.. not to the host...


interface GigabitEthernet0/0
ip address 10.0.100.254 255.255.255.0
ip virtual-reassembly in
duplex auto
speed auto
media-type rj45
!
interface GigabitEthernet0/1
description interface_lan
ip address 192.168.0.105 255.255.255.0
ip virtual-reassembly in
duplex auto
speed auto
media-type rj45
!
interface GigabitEthernet0/2
no ip address
duplex auto
speed auto
media-type rj45
!
interface GigabitEthernet0/3
no ip address
duplex auto
speed auto
media-type rj45
!
ip forward-protocol nd
!
!
no ip http server
no ip http secure-server

!

what can be the problem ? bellow I leave my routing table in my real pc and some tests.. thanks..

I dislike such static toutes adding on home PC.
Best way is to do NAT on Lab router connected to cloud0
Static default route on lab router
and NAT

and all woll work
no need touch home windows at all

You will achieve scenario like in real life