about EVE-NG bridging to physical network
Moderator: mike
-
- Posts: 13
- Joined: Wed May 31, 2017 6:26 am
- Location: Shanghai
about EVE-NG bridging to physical network
this is quite a simple topology, i bridge the switch to my physical network which is 192.168.1.0/24
the thing is i can reach switch e0/1(192.168.1.10) from my physical PC, but not able to reach 10.1.1.0 network
i checked the ARP table on my PC, i found that the MAC address of 192.168.1.10 is the MAC of the computer where VMWare installed in instead of the real MAC of switch e0/1
is there any possibility that i can reach the network behind the direct connected network ?
thank you
the thing is i can reach switch e0/1(192.168.1.10) from my physical PC, but not able to reach 10.1.1.0 network
i checked the ARP table on my PC, i found that the MAC address of 192.168.1.10 is the MAC of the computer where VMWare installed in instead of the real MAC of switch e0/1
is there any possibility that i can reach the network behind the direct connected network ?
thank you
You do not have the required permissions to view the files attached to this post.
-
- Posts: 5086
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
-
- Posts: 5086
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: about EVE-NG bridging to physical network
of course you will not be able to reach network behind 192.168.1.0...
simple ccna task..no routes between 192.168.1.0 and 10.x.x.x
UD
simple ccna task..no routes between 192.168.1.0 and 10.x.x.x
UD
-
- Posts: 13
- Joined: Wed May 31, 2017 6:26 am
- Location: Shanghai
Re: about EVE-NG bridging to physical network
thanks UD, i will definitely go through the cookbook
a quick question here if you don't mind,
there is no routes problem here, both my physical PC and R2 point the gateway to the switch.
e0/1 belongs to vlan 10 and e0/0 belong to vlan 20, and i have interface vlan 10 and interface vlan 20 configured.
so on switch viewpoint, both 192.168.1.0 and 10.1.1.0 are direct connected.
the point is when i ping 10.1.1.0 from my physical PC on 192.168.1.0, the packet doesn't arrive switch e0/1 as the result of packet capture
my lab is all based on vmware workstation by the way
a quick question here if you don't mind,
there is no routes problem here, both my physical PC and R2 point the gateway to the switch.
e0/1 belongs to vlan 10 and e0/0 belong to vlan 20, and i have interface vlan 10 and interface vlan 20 configured.
so on switch viewpoint, both 192.168.1.0 and 10.1.1.0 are direct connected.
the point is when i ping 10.1.1.0 from my physical PC on 192.168.1.0, the packet doesn't arrive switch e0/1 as the result of packet capture
my lab is all based on vmware workstation by the way
-
- Posts: 5086
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: about EVE-NG bridging to physical network
turn off ip cef on switch
no ip cef
and your native PC knows about 192.168.1.0/24 network, but knows nothing how to reach 10.1.1.0
UD
no ip cef
and your native PC knows about 192.168.1.0/24 network, but knows nothing how to reach 10.1.1.0
UD
-
- Posts: 13
- Joined: Wed May 31, 2017 6:26 am
- Location: Shanghai
Re: about EVE-NG bridging to physical network
hi UD, it has nothing to do with the routes, i configured the static route on my PC alright.
if you have interest, you can create the same lab in your environment, just like this: R1 —— R2 —— Cloud0 —— Physical PC
try to ping R1 from your physical PC(not a virtual machine but a physical PC), you will never make it
i tested the same lab in ESXi environment, it works perfectly fine, but it doesn't work out in VMware workstation
if you have interest, you can create the same lab in your environment, just like this: R1 —— R2 —— Cloud0 —— Physical PC
try to ping R1 from your physical PC(not a virtual machine but a physical PC), you will never make it
i tested the same lab in ESXi environment, it works perfectly fine, but it doesn't work out in VMware workstation
-
- Posts: 5086
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: about EVE-NG bridging to physical network
Read section 10 in our cook book. It is for EVE Pro, but most stuff regarding clouds is same in the EVE community
http://www.eve-ng.net/images/EVE-COOK-BOOK-1.0.pdf
Another thing it can be wifi adapter issue if you have bridged cloud with wifi interface
UD
http://www.eve-ng.net/images/EVE-COOK-BOOK-1.0.pdf
Another thing it can be wifi adapter issue if you have bridged cloud with wifi interface
UD
-
- Posts: 13
- Joined: Wed May 31, 2017 6:26 am
- Location: Shanghai
Re: about EVE-NG bridging to physical network
awesome, thats it, the wifi adapter is the cause!Uldis (UD) wrote: ↑Thu Jul 12, 2018 3:30 pmRead section 10 in our cook book. It is for EVE Pro, but most stuff regarding clouds is same in the EVE community
http://www.eve-ng.net/images/EVE-COOK-BOOK-1.0.pdf
Another thing it can be wifi adapter issue if you have bridged cloud with wifi interface
UD
i just test bridging cloud to the ethernet adapter and everthing is fine!
but whats the difference between bridging to wireless adapter and bridging to wired adapter?
thanks UD anyway
-
- Posts: 5086
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: about EVE-NG bridging to physical network
Because not all wifi adapters (manufacturers) are supported by VM ware
-
- Posts: 13
- Joined: Wed May 31, 2017 6:26 am
- Location: Shanghai
Re: about EVE-NG bridging to physical network
that makes sense, perfect