LISTSERV mailing list manager LISTSERV 16.5

Help for SCIENTIFIC-LINUX-USERS Archives

   

SCIENTIFIC-LINUX-USERS Archives

SCIENTIFIC-LINUX-USERS Archives


SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

SCIENTIFIC-LINUX-USERS Home

SCIENTIFIC-LINUX-USERS Home

SCIENTIFIC-LINUX-USERS  April 2016

SCIENTIFIC-LINUX-USERS April 2016

Subject:

Re: Virtual Box MS Win 7 guest no NAT issue now understood

From:

Tom H <[log in to unmask]>

Reply-To:

Tom H <[log in to unmask]>

Date:

Wed, 6 Apr 2016 10:34:37 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (93 lines)

On Wed, Apr 6, 2016 at 7:19 AM, Yasha Karant <[log in to unmask]> wrote:
>
> I have now resolved the cause of the lack of NAT Internet connection
> on a Virtual Box MS Win 7 guest.  After I installed SL 7.2 on my
> wife's new laptop, I restored (via a cp from an external USB hard
> drive that held all of the files that were not SL installed, including
> all of the Virtual Box guest files) the Virtual Box guest files from
> her previous laptop to the new machine.  I installed the Virtual Box
> EL7 RPM, configured VirtualBox to recognize the restored guest files,
> and the NAT network functioned over the 802.11 WNIC controlled by SL 7
> Network Manager -- everything worked (indeed, any statements that NAT
> would not work with 802.11 in "new" kernels were indeed red herrings).

Not at all. I even posted the kernel code where bridging's disabled for wifi.

VirtualBox doesn't use the Linux kernel's bridging.

This is from the VirtualBox documentation:

Bridging to a wireless interface is done differently from bridging to
a wired interface, because most wireless adapters do not support
promiscuous mode. All traffic has to use the MAC address of the host's
wireless adapter, and therefore VirtualBox needs to replace the source
MAC address in the Ethernet header of an outgoing packet to make sure
the reply will be sent to the host interface. When VirtualBox sees an
incoming packet with a destination IP address that belongs to one of
the virtual machine adapters it replaces the destination MAC address
in the Ethernet header with the VM adapter's MAC address and passes it
on. VirtualBox examines ARP and DHCP packets in order to learn the IP
addresses of virtual machines.

And this is from a laptop with a running VirtualBox VM. There's no
Linux bridge on the host (or a tun/tap interface either):

th@localhost:~$ VBoxManage list runningvms
"lubuntu" {65a3e709-e368-4717-8cd2-41e8751449ce}

th@localhost:~$ VBoxManage showvminfo lubuntu | grep "NIC 1"
NIC 1:           MAC: 080027A018CE, Attachment: Bridged Interface
'wlp18s0', Cable connected: on, Trace: off (file: none), Type:
82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy:
deny, Bandwidth group: none

th@localhost:~$ VBoxManage list bridgedifs
Name:            wlp18s0
GUID:            31706c77-7338-4030-8000-c0cb380f865a
DHCP:            Disabled
IPAddress:       192.168.1.223
NetworkMask:     255.255.255.0
IPV6Address:     2a02:1205:c6a3:b7d0:c2cb:38ff:fe0f:865a
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: c0:cb:38:0f:86:5a
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-wlp18s0

th@localhost:~$ sudo ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: wlp18s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UP mode DORMANT group default qlen 1000
    link/ether c0:cb:38:0f:86:5a brd ff:ff:ff:ff:ff:ff

th@localhost:~$ sudo bridge l

th@localhost:~$ sudo ip -4 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
3: wlp18s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UP group default qlen 1000
    inet 192.168.1.223/24 brd 192.168.1.255 scope global wlp18s0
       valid_lft forever preferred_lft forever

th@localhost:~$ ssh 192.168.1.224

th@yasha:~$ sudo ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP mode DEFAULT group default qlen 1000
    link/ether 08:00:27:a0:18:ce brd ff:ff:ff:ff:ff:ff

So "lubuntu" is running with an interface bridged using VirtualBox's
internal bridging and accessible from the host.

You were pointed at various ways to do this with Linux and KVM but
you'd have had to install and configure extra software to do so and it
never seemed to interest you.

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2023
September 2023
August 2023
June 2023
February 2023
January 2023
December 2022
November 2022
October 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
April 2004

ATOM RSS1 RSS2



LISTSERV.FNAL.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager