Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.networking > #3513 > unrolled thread

Network for a VM

Back to article view | Back to comp.os.linux.networking

Contents

  Network for a VM Paulo da Silva <p_s_d_a_s_i_l_v_a_ns@netcabo.pt> - 2015-10-02 06:09 +0100
    Re: Network for a VM Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-10-02 07:03 +0000
      Re: Network for a VM Paulo da Silva <p_s_d_a_s_i_l_v_a_ns@netcabo.pt> - 2015-10-02 08:25 +0100
    Re: Network for a VM [SOLVED] Paulo da Silva <p_s_d_a_s_i_l_v_a_ns@netcabo.pt> - 2015-10-02 08:23 +0100
      Re: Network for a VM [SOLVED] Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2015-10-02 16:50 +0000
        Wireless bridging [Was: Network for a VM] Ian Zimmerman <itz@buug.org> - 2015-10-03 09:20 -0700
          Re: Wireless bridging [Was: Network for a VM] Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2015-10-05 17:44 +0000
            Re: Wireless bridging [Was: Network for a VM] Ian Zimmerman <itz@buug.org> - 2015-10-06 21:26 -0700
              Re: Wireless bridging [Was: Network for a VM] Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2015-10-07 16:47 +0000
            Re: Wireless bridging [Was: Network for a VM] Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> - 2015-10-09 22:58 +0200

#3513 — Network for a VM

Hi all!

I usually use a VM (virtualbox) with all default net configurations.
It works fine.
ifconfig reports its IP address as 10.0.2.15.
This works fine for VM to outside world.

Now I need to run a server in that VM.
How do I configure it (and its host) in order to make it accessible from
the host or other machines of my network (192.168.1.x).

I don't know too much of networking except for the very basic.

BTW, all OS are kubuntu 14.04.

Thanks for any help.

[toc] | [next] | [standalone]

#3514

On Fri, 2015-10-02, Paulo da Silva wrote:
> Hi all!
>
> I usually use a VM (virtualbox) with all default net configurations.
> It works fine.
> ifconfig reports its IP address as 10.0.2.15.
> This works fine for VM to outside world.
>
> Now I need to run a server in that VM.
> How do I configure it (and its host) in order to make it accessible from
> the host or other machines of my network (192.168.1.x).
>
> I don't know too much of networking except for the very basic.

If all you need is one TCP port, a simple solution is port forwarding.
You can tell Virtualbox that "a packet to port X on host should be
passed on to the VM's port Y".

/Jorgen

-- 
  // Jorgen Grahn <grahn@  Oo  o.   .     .
\X/     snipabacken.se>   O  o   .

[toc] | [prev] | [next] | [standalone]

#3516

Às 08:03 de 02-10-2015, Jorgen Grahn escreveu:
> On Fri, 2015-10-02, Paulo da Silva wrote:
>> Hi all!
...

> If all you need is one TCP port, a simple solution is port forwarding.
> You can tell Virtualbox that "a packet to port X on host should be
> passed on to the VM's port Y".
> 

As I said (see my 2nd post please), bridging from VBOX solved my problem.

Anyway, thank you very much.

[toc] | [prev] | [next] | [standalone]

#3515 — Re: Network for a VM [SOLVED]

Às 06:09 de 02-10-2015, Paulo da Silva escreveu:

In the meanwhile I could see that VBOX has an option to bridge.
This has an advantage to not have to create another network and so avoid
firewall complications.

I was searching for network "special" configurations but VBOX bridging
works out of the box!!!

Thank you.
Paulo

[toc] | [prev] | [next] | [standalone]

#3517 — Re: Network for a VM [SOLVED]

On 2015-10-02, Paulo da Silva <p_s_d_a_s_i_l_v_a_ns@netcabo.pt> wrote:

> Às 06:09 de 02-10-2015, Paulo da Silva escreveu:
>
> In the meanwhile I could see that VBOX has an option to bridge.
> This has an advantage to not have to create another network and so avoid
> firewall complications.
>
> I was searching for network "special" configurations but VBOX bridging
> works out of the box!!!

Speaking of bridging, has anyone else had problems with wifi?  I've never
been able to bridge the wireless adapter to my Windows virtual machine,
although the Ethernet port works just fine.

-- 
/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
\ /  I'm really at ac.dekanfrus if you read it the right way.
 X   Top-posted messages will probably be ignored.  See RFC1855.
/ \  HTML will DEFINITELY be ignored.  Join the ASCII ribbon campaign!

[toc] | [prev] | [next] | [standalone]

#3518 — Wireless bridging [Was: Network for a VM]

On 2015-10-02 16:50 +0000, Charlie Gibbs wrote:

> Speaking of bridging, has anyone else had problems with wifi?  I've never
> been able to bridge the wireless adapter to my Windows virtual machine,
> although the Ethernet port works just fine.

I think that many, if not most, wireless access points will refuse to
communicate over the wireless link with an IP host that has not
associated with the AP on the wireless level.  The more tweakable APs
have a setting to defeat this (maybe as a list of static routes).  So
you should explore your AP/router settings.

Btw, why?  Are you really running a server on a Windows VM?

-- 
Please *no* private copies of mailing list or newsgroup messages.
Rule 420: All persons more than eight miles high to leave the court.

[toc] | [prev] | [next] | [standalone]

#3521 — Re: Wireless bridging [Was: Network for a VM]

On 2015-10-03, Ian Zimmerman <itz@buug.org> wrote:

> On 2015-10-02 16:50 +0000, Charlie Gibbs wrote:
>
>> Speaking of bridging, has anyone else had problems with wifi?  I've never
>> been able to bridge the wireless adapter to my Windows virtual machine,
>> although the Ethernet port works just fine.
>
> I think that many, if not most, wireless access points will refuse to
> communicate over the wireless link with an IP host that has not
> associated with the AP on the wireless level.  The more tweakable APs
> have a setting to defeat this (maybe as a list of static routes).  So
> you should explore your AP/router settings.
>
> Btw, why?  Are you really running a server on a Windows VM?

No, I have a laptop running Debian Jessie, and to do Windows stuff
needed for work I run a Windows VM under VirtualBox.  It works great
in every respect except for wifi.  The native Linux OS can use both
Ethernet and wifi with no problems.  VirtualBox can bridge the Ethernet
port to the Windows VM, which queries my DHCP server for its own IP
address distinct from that for the native Linux Ethernet interface.
However, the wireless adapter will not bridge; the Windows VM only has
network access when the Ethernet cable is plugged in.

I did a bit of googling on this a while ago, and from other people's
posts I got the impression that this is a known problem, so I haven't
worried about it too much.  But it sounds sufficiently close to the
subject of this thread that I thought I'd throw it out again.

-- 
/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
\ /  I'm really at ac.dekanfrus if you read it the right way.
 X   Top-posted messages will probably be ignored.  See RFC1855.
/ \  HTML will DEFINITELY be ignored.  Join the ASCII ribbon campaign!

[toc] | [prev] | [next] | [standalone]

#3522 — Re: Wireless bridging [Was: Network for a VM]

On 2015-10-05 17:44 +0000, Charlie Gibbs wrote:

> > Btw, why?  Are you really running a server on a Windows VM?
> 
> No, I have a laptop running Debian Jessie, and to do Windows stuff
> needed for work I run a Windows VM under VirtualBox.

If you don't run a server on the VM, why do you need bridging?  Can't
VirtualBox do a virtual routed network with NAT?  KVM certainly can.

Here is the real snafu, in addition to the picky AP one:

http://v.gd/UkTM1Y

-- 
Please *no* private copies of mailing list or newsgroup messages.
Rule 420: All persons more than eight miles high to leave the court.

[toc] | [prev] | [next] | [standalone]

#3524 — Re: Wireless bridging [Was: Network for a VM]

On 2015-10-07, Ian Zimmerman <itz@buug.org> wrote:

> On 2015-10-05 17:44 +0000, Charlie Gibbs wrote:
>
>>> Btw, why?  Are you really running a server on a Windows VM?
>> 
>> No, I have a laptop running Debian Jessie, and to do Windows stuff
>> needed for work I run a Windows VM under VirtualBox.
>
> If you don't run a server on the VM, why do you need bridging?  Can't
> VirtualBox do a virtual routed network with NAT?  KVM certainly can.

Perhaps.  Bridging is just so darned convenient, though - and it
works perfectly on an Ethernet connection.

> Here is the real snafu, in addition to the picky AP one:
>
> http://v.gd/UkTM1Y

Ouch.  I'll check out your other suggestions if I find the time.
It's a low priority, though, since most of the time I'm either
within reach of an Ethernet cable, or can work offline.

-- 
/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
\ /  I'm really at ac.dekanfrus if you read it the right way.
 X   Top-posted messages will probably be ignored.  See RFC1855.
/ \  HTML will DEFINITELY be ignored.  Join the ASCII ribbon campaign!

[toc] | [prev] | [next] | [standalone]

#3528 — Re: Wireless bridging [Was: Network for a VM]

Charlie Gibbs a écrit :
> 
> No, I have a laptop running Debian Jessie, and to do Windows stuff
> needed for work I run a Windows VM under VirtualBox.  It works great
> in every respect except for wifi.  The native Linux OS can use both
> Ethernet and wifi with no problems.  VirtualBox can bridge the Ethernet
> port to the Windows VM, which queries my DHCP server for its own IP
> address distinct from that for the native Linux Ethernet interface.
> However, the wireless adapter will not bridge; the Windows VM only has
> network access when the Ethernet cable is plugged in.

The ability to bridge a wireless interface in managed mode has been
disabled some time ago because it just does not work. The standard
802.11 frame header format does not have room for both the wireless
client MAC address and the host MAC adress behind the bridge. This
requires specific WDS or 4-address mode.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.networking

csiph-web