VirtualBox

Opened 9 years ago

Closed 9 years ago

#14103 closed defect (invalid)

Setting internal network on other NIC's stops bridged network on 1st NIC from working

Reported by: OzyLondon Owned by:
Component: other Version: VirtualBox 4.3.26
Keywords: network internal bridged Cc:
Guest type: BSD Host type: Mac OS X

Description

Host machine: MBP15 retina running Yosemite. Virtual box 4.3.26

Guest machines: Created 4 virtual machines (A, B, C & D). Installed FreeBSD 11 on all of them. All machines have their first NIC set to bridged using wireless NIC of MBP15

  • Can ping/ssh thru from MBP to all 4 guess machines as expected
  • Can ping/ssh thru from all 4 guest machines to the other 3 guest machines as expected

Added 3 additional NIC's to all 4 virtual machines and configured them to use default internal network. Did not bind ip stack to additional NIC's but they were visible in the guests

  • Cannot ping/ssh from MBP to all 4 guess machines - expect to be abled to reach.
  • Can ping/ssh from all 4 guest machines to the other 3 guest machines as expected.

Changed the internal network used for guests A & B to a new internal network called north Changed the internal network used for guests C & D to a new internal network called south

  • Cannot ping/ssh from MBP to all 4 guess machines - expect to be able to reach.
  • Can still ping/ssh from A to B and from B to A (ie within internal network called north) as expected.
  • Can still ping/ssh from C to D and from D to C (ie within internal network called south) as expected.
  • Cannot ping from A or B to C or D and vice versa (ie from internal network south to north and vice versa) - would expect to be able to reach

IP stack was only every bound to the first (bridged) interface in the FreeBSD guests. All pings and ssh activity happened/was attempted thru bridged NIC

In summary is seems that configuring addition NICS to use an internal network not only sandboxes the NIC's bound to the internal network but other (bridged) NIC's as well, thus rendering the guest inaccessible from any other machine (virtual or otherwise) that does not also have a NIC bound to the same internal network

I don't not think logs are relevant here so I have not attached

Change History (2)

comment:1 by OzyLondon, 9 years ago

Please close.

FreeBSD guest were found to misconfigured. When corrected all worked fine

comment:2 by Valery Ushakov, 9 years ago

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use