Ive been trying to run Slackware in Virtual Box. But my problem, aside from my english, is that i cant seem to be able to bring my wireless network over to my virtual pc.
My PC is a Lenovo Ideapad S10-3.

Im currently running another operating system, but my aim is to be able to run Slackware with everything working.

I dont know where to start.

brgds

Hi -

It should work just fine:

1. Define a virtual interface (the default is probably Am79C973; any of the supported virtual network adapters should work).

2. Use NAT mode (again, there are many choices which should work, but use the default: NAT).

3. Configure port forwarding on any service you would like to access from outside your VM (i.e. any services you want to "export" from the VM).

4. Configure your virtual interface like you normally would configure any interface.

Voila! Done.

It should be fairly straightforward. Again: choose defaults whenever possible (wait until you've got everything working before you start experimenting with other alternatives).

These links give more details:

http://www.virtualbox.org/manual/ch06.html

http://cheznick.net/main/content/vir...access-via-nat

'Hope that helps .. PSM

PS:
You're a big star, aren't you?

At least in Taurus

VM's interact with the host. You don't use wireless on the VM. It has a virtual NIC. That virtual nic connects through a Virtual router to the host network.

Uh, Jefro - that's what I just said.

Didn't I ?

Aldebaran -

It's really fairly easy. Just look at the links I sent you (or Google for alternate links you might prefer).

Please post back with any specific questions you might have.

And, above all - have fun!

Ok. First of all: Thanks for quick and informative replies.

As far as I understand the Virtual box takes my wireless card, "translates" it and presents it to my virtual machine as one of the cards listed as adapter types. This means my virtual Slackware will not recognize the wireless card as the same type as is in the laptop.

This again mean I have to install the kernel drivers, if they`re not already present, to the cards listed in Virtual box adapter types.

I know this probably isn`t technically correct, but have I managed to get the basic hang of it?

brgds

ps: Aldebaran is indeed a big star. My favorite

Yeah, that is right. One of the main ideas behind virtual machines is that they don't have any interaction with anything real.

That's right. My experience is that the virtual cards are generic enough that almost any modern distro has the right drivers right out of the box.

I think you've got the hang of it quite nicely.

Basically correct. In reality, there are TWO network adapters: your "real" adapter (which happens to be a wireless NIC), and your "virtual" NIC.

Yes, because your virtual NIC is a *separate* NIC.


Yes, indeed

PS:
This is also basically what Jefro was trying to say. But the relationship between your virtual NIC and your physical interface can come in any of several "flavors":

a) NAT mode (this uses a virtual router, like Jefro said)
b) Bridged mode (in this mode, your virtual NIC is on the same subnet as your physical NIC. Here, you have a virtual "bridge" instead of a virtual "router")
c) Host-only (here, there is *no* network communication between your virtual NIC and "the real world")
d) Etc (there are other variations, depending on your specific configuration and specific needs)

'Hope that helps .. PSM

The host OS (probably WinBloze) passes wireless networks to the guest via a virtual Ethernet device. Therefore, it's eth0 that you need to configure in the guest OS, not any wireless network device as would be the case with a host OS.

I tried to make it simple.


You don't use wireless on the VM. The VM has a virtual NIC. That virtual nic connects through a Virtual router to the host network.


Just install your VM application. Set VM properties to NAT. Install your OS. (some OS's may need a driver for virtual nic).

Let it rip.

The Virtual machine has a software router to transfer your VM's data to your hosts nic.