![]() ![]() To avoid adding routes manually I can think of 2 possible solutions (I have not done any of them so I cannot provide detailed info, but I am mentioning them in case they help you) You could also add a "wider" range on this route like 10.0.0.0/16 if this helps to overcome the "particular network" issue that you mention (and assuming that the whole 10.x.x.x network is not used anywhere else) It (VM) does not know which interface to use to return the PING replies.īecause there is no specific route for 10.x.x.x IPs on the VM, so it sends these packets to the default gateway "default via 192.168.221.2 dev ens33"Ī route should exist in the VM so that it knows where to send the packages for 10.x.x.x and that is why everything works when you add: I do not know if it is possible to use the OSPF routing protocol also in the Ubuntu VM, and it will solve the communication problem between the VM and the routers.įrom the Ubuntu VM I can PING loopback interfaces of R1 and R2 but only if I set the output interface I would like to integrate the best possible Ubuntu VM in the GNS3 network so that the VM could behave as directly connected to interface g0/0 of R1. Also, with this solution in this particular network, I would have to PING from R2 indicating the source IP 10.0.0.2, which is not desired. I can add a static route through virbr0: IP route add 10.0.0.0/24 via 192.168.122.1 dev virbr0īut this is a solution that can only work in this particular network and not in a general scenario with different IP assignation. I have to indicate the interface to use un the PING requests. It looks like the Ubuntu VM receives the PING requests from router R2 (Lo: 10.0.0.2) but it does not know which interface to use to return the PING replies.īesides, the PING requests from the Ubuntu VM also have the same problem. In the Ubuntu VM host, the routes are: $ ip routeĭefault via 192.168.221.2 dev ens33 proto dhcp metric 100ġ69.254.0.0/16 dev ens33 scope link metric 1000ġ72.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdownġ92.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1ġ92.168.221.0/24 dev ens33 proto kernel scope link src 192.168.221.143 metric 100įrom the Ubuntu VM I can PING loopback interfaces of R1 and R2 but only if I set the output interface: $ ping -I virbr0 10.0.0.2 For example, they can PING each other's loopback interfaces. Gateway of last resort is 10.1.1.1 to network 0.0.0.0Ĭ 10.0.0.2/32 is directly connected, Loopback0Ĭ 10.1.1.0/24 is directly connected, GigabitEthernet0/0 ![]() O - ODR, P - periodic downloaded static route Ia - IS-IS inter area, * - candidate default, U - per-user static route I - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2Į1 - OSPF external type 1, E2 - OSPF external type 2 I am using the OSPF routing protocol in R1 and R2.Ĭodes: C - connected, S - static, R - RIP, M - mobile, B - BGPĭ - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area The cloud in the topology represents the connection with the Ubuntu VM host. I am using the virtual bridge interface, virbr0:192.168.122.1, to connect the two routers R1 and R2 with the VM Ubuntu. ![]() The network in GNS3 has two routers with this topology: ![]() TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Interfaces in my VM are: docker0: flags=40 I would like to use monitoring software installed in an Ubuntu VM to manage the network emulated into GNS3, which is also installed in the Ubuntu VM. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |