| 1 |
Am Wed, 17 Sep 2008 20:22:54 -0300 |
| 2 |
schrieb Norberto Bensa <nbensa@×××××.com>: |
| 3 |
|
| 4 |
> Quoting Marc Joliet <marcec@×××.de>: |
| 5 |
> |
| 6 |
> > Right now I got it working without using a bridge. I can ping my |
| 7 |
> > Windows XP VM and it can ping everything else on my side, however, |
| 8 |
> > nmap won't work. I wonder why? Does the Windows firewall block it off? |
| 9 |
> > |
| 10 |
> |
| 11 |
> nmap runs on the guest? |
| 12 |
|
| 13 |
No, on the host. I noticed the following works: |
| 14 |
|
| 15 |
marcec@marcec ~ % sudo nmap -PN 172.16.1.2 |
| 16 |
Passwort: |
| 17 |
|
| 18 |
Starting Nmap 4.53 ( http://insecure.org ) at 2008-09-18 02:28 CEST |
| 19 |
Nmap done: 1 IP address (0 hosts up) scanned in 0.273 seconds |
| 20 |
marcec@marcec ~ % |
| 21 |
|
| 22 |
So I assume nothing is wrong, it's probably Windows built in firewall. |
| 23 |
|
| 24 |
> |
| 25 |
> >> After all this, create a small bash script in /usr/bin. I called |
| 26 |
> > I would think such a script belongs in /usr/local/bin? |
| 27 |
> |
| 28 |
> Errr.. Yup. But I don't know why VB doesn't get my $PATH. |
| 29 |
|
| 30 |
Yeah, I thought it was something like that, I just wanted to be sure, |
| 31 |
though in retrospect I guess the question was superfluous. |
| 32 |
|
| 33 |
> |
| 34 |
> >> The interface is create and destroyed on demand. |
| 35 |
> > |
| 36 |
> > I would do that (create a bridge without any IFs attached and |
| 37 |
> > then have them added dynamically), except the VBoxAddIF script in |
| 38 |
> > virtualbox-ose-2.0.2 craps out on a missing file |
| 39 |
> > (/var/run/VirtualBox/vboxnet). Google didn't yield anything useful. |
| 40 |
> > |
| 41 |
> >> marcec@marcec ~ % sudo VBoxAddIF vbox0 marcec br0 |
| 42 |
> >> VirtualBox host networking interface creation utility, version _VERSION_ |
| 43 |
> >> (C) 2005-2007 Sun Microsystems, Inc. |
| 44 |
> >> All rights reserved. |
| 45 |
> >> |
| 46 |
> >> Creating the permanent host networking interface "vbox0" for user marcec. |
| 47 |
> >> |
| 48 |
> >> Failed to add the interface "vbox0" to the bridge "br0". |
| 49 |
> |
| 50 |
> And where's your br0 in /etc/conf.d/net? I can't find it. |
| 51 |
|
| 52 |
Sorry, that's because I had it commented out after the failure. It |
| 53 |
looks like this: |
| 54 |
|
| 55 |
config_br0=( "172.16.1.1 broadcast 172.16.1.255 netmask 255.255.255.0" ) |
| 56 |
brctl_br0=( "setfd 0" "sethello 0" "stp on" ) |
| 57 |
|
| 58 |
And that's it. |
| 59 |
|
| 60 |
I just created the directory /var/run/VirtualBox/ via mkdir and set |
| 61 |
the group to vboxusers. Then I ran your script. Now it seems to work, |
| 62 |
except for the fact that VirtualBox seems to not run the script, even |
| 63 |
with the full path. I can run the script manually, creating vbox1 and |
| 64 |
then start the VM and everything works, but with: |
| 65 |
|
| 66 |
Attached to: vbox1 |
| 67 |
Setup application: /usr/local/bin/addif.sh vbox1 up |
| 68 |
terminate application: /usr/local/bin/addif.sh vbox1 down |
| 69 |
|
| 70 |
the VM doesn't start and the TAP devices aren't created. How |
| 71 |
frustrating :/ . |
| 72 |
|
| 73 |
> > When looking at the relevent line (237), apparently it's because the |
| 74 |
> > directory doesn't exist so it can't create the file. What does it look |
| 75 |
> > like on your system? Shouldn't the ebuild have created that directory? |
| 76 |
> |
| 77 |
> I have no /var/run/VirtualBox... but I use virtualbox-bin-2.0.2. |
| 78 |
|
| 79 |
Hmm, odd. |
| 80 |
|
| 81 |
> Regards, |
| 82 |
> Norberto |
| 83 |
> |
| 84 |
> ---------------------------------------------------------------- |
| 85 |
> This message was sent using IMP, the Internet Messaging Program. |
| 86 |
> |
| 87 |
|
| 88 |
So, I'll try some more tomorrow, but now I really need some sleep :-) . |
| 89 |
-- |
| 90 |
Marc Joliet |
| 91 |
-- |
| 92 |
"People who think they know everything really annoy those of us who |
| 93 |
know we don't" - Bjarne Stroustrup |
Archives