Quoting Marc Joliet <[EMAIL PROTECTED]>:
Right now I got it working without using a bridge. I can ping my
Windows XP VM and it can ping everything else on my side, however,
nmap won't work. I wonder why? Does the Windows firewall block it off?
nmap runs on the guest?
After all this, create a small bash script in /usr/bin. I called
I would think such a script belongs in /usr/local/bin?
Errr.. Yup. But I don't know why VB doesn't get my $PATH.
The interface is create and destroyed on demand.
I would do that (create a bridge without any IFs attached and
then have them added dynamically), except the VBoxAddIF script in
virtualbox-ose-2.0.2 craps out on a missing file
(/var/run/VirtualBox/vboxnet). Google didn't yield anything useful.
[EMAIL PROTECTED] ~ % sudo VBoxAddIF vbox0 marcec br0
VirtualBox host networking interface creation utility, version _VERSION_
(C) 2005-2007 Sun Microsystems, Inc.
All rights reserved.
Creating the permanent host networking interface "vbox0" for user marcec.
Failed to add the interface "vbox0" to the bridge "br0".
And where's your br0 in /etc/conf.d/net? I can't find it.
When looking at the relevent line (237), apparently it's because the
directory doesn't exist so it can't create the file. What does it look
like on your system? Shouldn't the ebuild have created that directory?
I have no /var/run/VirtualBox... but I use virtualbox-bin-2.0.2.
Regards,
Norberto
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
