"L. F. Elia" <lfe...@yahoo.com> asks about networking on VirtualBox.

We too found its behavior different from other virtualization systems, 
and I tend to write copious notes about machine issues.  Here is a
fragment of those notes, with generalized hostnames:

The network setup on VirtualBox on vboxhost.example.com is unusual: its
initial network is not bidirectional!  It only connects outbound.

In order to get inbound connections for ssh, it is necessary to add a
second network adapter, which can only be down in powered-off state:

        VirtualBox control panel ->
                Settings -> Network -> Adapter2 -> Attached-to -> Host-only 
adapter
                Name: vboxnet0

plus
        Advanced ->
                Adapter Type -> Intel PRO/1000 MT +
                Promiscuous Mode: Deny +
                Cable Connected

For the original Adapter1, we have

        VirtualBox control panel ->
                Settings -> Network -> Adapter1 -> Attached-to -> NAT
plus
        Advanced ->
                Adapter Type -> Intel PRO/1000 MT +
                Promiscuous Mode: Deny +
                Cable Connected +
                Port Forwarding

On a reboot, the VM will have two networks, like this example for
guest.example.com:

        % ifconfig -a
        em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 
1500
                
options=85059b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,LRO,VLAN_HWFILTER,VLAN_HWTSO>
                ether 08:00:27:f2:0b:cc
                inet 10.0.2.15 netmask 0xffffff00 broadcast 10.0.2.255
                nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
                media: Ethernet autoselect (1000baseT <full-duplex>)
                status: active
        em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 
1500
                
options=85059b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,LRO,VLAN_HWFILTER,VLAN_HWTSO>
                ether 08:00:27:36:0b:70
                inet 192.168.56.101 netmask 0xffffff00 broadcast 192.168.56.255
                nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
                media: Ethernet autoselect (1000baseT <full-duplex>)
                status: active
        ...

sshd normally listens on all network interfaces, so from the
VirtualBox host, vboxhost.example.com, I can now do

        ssh USER@192.168.56.101

and with suitable $HOME/.ssh/config settings, such as this on
anotherhost.example.com,

        Host = guest.example.com guest
                User = jones
                HostName = 192.168.56.101
                ProxyJump vboxhost.example.com

I can now ssh from anotherhost to the VM on VirtualBox on vboxhost.

-------------------------------------------------------------------------------
- Nelson H. F. Beebe                    Tel: +1 801 581 5254                  -
- University of Utah                    FAX: +1 801 581 4148                  -
- Department of Mathematics, 110 LCB    Internet e-mail: be...@math.utah.edu  -
- 155 S 1400 E RM 233                       be...@acm.org  be...@computer.org -
- Salt Lake City, UT 84112-0090, USA    URL: http://www.math.utah.edu/~beebe/ -
-------------------------------------------------------------------------------

_______________________________________________
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Reply via email to