Custom Query (16363 matches)
Results (1333 - 1335 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9012 | invalid | Bridge device assignments unreliable if two identical NICs are installed on a windows host. | ||
| Description |
I have two identical (same chipset and same driver) ethernet NICs installed in a Windows 7 SP1 host. They appear on the device manager as two devices with identical names. I'd like to bridge each to a different virtual interface in a Linux guest. Unfortunately, the VirtualBox machine configuration files identify interfaces in bridging configurations only by their name, leading to an ambiguity in this case (since both devices are identical) and resulting in the two devices being randomly re-assigned to a different virtual guest interface every time. A more precise way of specifying host network devices needs to be used, perhaps mac address or the windows UUID. |
|||
| #12633 | obsolete | Bridge network unreachable inside Debian guest of VB hosted in Windows 8.1 | ||
| Description |
I am deploying docker containers inside Debian guest VM, the host Windows 8.1 PC uses VB with bridged network. To make the individual container IP reachable from the LAN, I am using IP of same network as well as the containers are connected at a bridge configured in Debian guest. Now the guest and host are reachable from LAN, containers IPs are reachable from host and guest. but there is no reach-ability between LAN to container IPs. LAN--------Windows-8.1 host, bridge------[Debian Guest-[--eth0--[bridge]--ethlnk0]]---[eth0--[docker containers]] It seems that I can maximum cross one bridge hop. I configured "stp" on for the bridge configured inside Debian guest. |
|||
| #5065 | obsolete | Bridge networking reports duplicated ip address | ||
| Description |
I'm running virtualbox 3.0.6 on my windows xp host and i'm trying to use bridge networking into my guests. I'm trying to bridge the wireless adapter. No one of the guest could connect to any ip adrress, and as an additional input, all the windows guests reports duplicated ip address. I did some check and i discovered that the problem seems to reside in the arp protocol. As soon as the guest tries to connect to an ipaddress that is in the same subnet, what happen is that into the guest and into the host operating system the ip address is registered with the macaddress of the host adapter. If the destination ip address is on a remote network, that the macaddress registered is the one of the default gateway. To solve the problem i had simply to manually delete the wrong arp entries from the host, guestes and remote systems and registers the macaddress manually using the arp -s command. So i'm suspecting a problem with the bridge driver that fails in some way managing the macadrresses. |
|||

