virtualbox fans?

[Bart Silverstrim]

Derek Broughton wrote:
> Bart Silverstrim wrote:
> 
>> I was afraid of that. Just when I told myself I can live with that as
>> long as it has the "shared folders" feature, that doesn't seem to work!
>>
> 
> The shared folder feature isn't SMB networking, though.  It's just exposing
> particular folders on the host to the client.

I understand that. In the directions for VirtBox, it said to go to net 
neighborhood, etc. etc. to get to the share, or "net use x: 
\\vboxsrv\sharename" to create the drive letter. As of 1.5 it was 
network-browseable, so my assumation is their implementation of shared 
folders was tied to the networking subsystem...separate, but similar to 
the Windows network shares, but I understand it's separate.

> To have your client visible on the LAN, it needs to be using "Host"
> networking (which then needs to be bridged via your host's network
> interface).

Yeah, would be nicer, but I'd rather not go through the jumps to get a 
tun interface working and tied up properly on the host.

> Now, everybody says that Host networking can't work via a bridge on a wifi
> IF.  That makes no sense to me, and I wish someone would explain it.  In
> any case, unless your client is getting a DHCP address from the LAN's DHCP
> server, you probably won't be able to address it by name, though you may be
> able to address it by IP.

Wifi: No idea. Not trying it over that.

DHCP: not bridged, so the guest is getting it's current config from the 
DHCP mechanism of the vbox network module (10.0.2.x)