This is my first post and I wanna show a issue I found in VirtualBox 4.0.6, using two Linux guests. My scenario have a Debian Lenny like AAA server for a Cisco router emulated in another Debian Squeeze. The idea is to make the router connection to his AAA Server. It was working perfectly until the 4.0.6 version. The schema show the hosts:
This is the GNS3 work screen:
At GNS3 I used brigde option to grant access of router to my host-only network through my eth1 interface
As you can see in the picture below, the router can not find the other hosts in the virtual network.
I searched the internet and found a site that made ??reference to this video: http://www.youtube.com/watch?v=ZbiyxUVY6Sc , then follow the tutorial and made ??this script after installing the needed packages.
Code: Select all
#!/bin/bash
tunctl -t tap0 > /dev/null
ifconfig eth1 0.0.0.0 promisc up
ifconfig tap0 0.0.0.0 promisc up
brctl addbr br0
brctl addif br0 eth1
brctl addif br0 tap0
ifconfig br0 192.168.1.2 up
and made the suggested settings:
Managed IP access to the same machine that GNS is running, but not the other machine's host-only network
So I opened the wireshark and started to analyze the traffic. The example below is resuIts a ping from the router to the machine that the GNS is operating. Note that the process is normal, the router tries the first package, but as there is nothing on the table ARP sends an ARP request to discover the MAC of 192.168.1.2 and then concludes the ping.
When I try to ping the other virtual machine at IP 192.168.1.10, the analysis shows that the ARP process ends without the router get the IP of the AAA server. Note that in the middle of traffic appear LOOP packages labeled as I do not know what it is. If the command is extended to several repetitions of these packages it keeps coming up, they also realized in response to the CDP. I believe it is a mistake of layer 2.
Using version 4.0.4 the two ways to access the host-only network of GNS work perfectly. I'm showing that one can check that it is a bug in the new version or if you know how to fix it. I lost some time with this problem ...
I'm new at this forum, if I put the post in the wrong place, please move it.
05.18.11 - After installing the version 4.0.8 the problem remains. I tried upgrading the VBoxLinuxAdditions and exchange virtual network adapter of the machines but the above problem remains unsolved.
06.29.11 - Version 4.0.10, the problem stil unsolved.