VirtualBox

Ticket #3754 (closed defect: fixed)

Opened 5 years ago

Last modified 4 years ago

vboxnet0 causes ndp,nwam startup to fail -> fixed in 2.2.2

Reported by: gwr Owned by:
Priority: major Component: network
Version: VirtualBox 2.2.0 Keywords: nwam
Cc: gordon.ross@… Guest type: Solaris
Host type: Solaris

Description

After installing VirtualBox 2.2.0 on Solaris Nevada (snv_111) these services fail during boot:

svc:/network/routing/ndp:default svc:/network/physical:nwam

I'm not really sure why this is happening, but I've posted fairly complete details in this thread on networking-discuss:  http://www.opensolaris.org/jive/thread.jspa?threadID=99651

It looks like something doesn't like the vboxnet0 i/f.

I've marked this "major" as it prevents network startup.

Attachments

nwam.txt Download (2.7 KB) - added by gwr 5 years ago.
service states and data
nwam-vboxnet1.log Download (18.0 KB) - added by gwr 5 years ago.
debug log from nwam

Change History

Changed 5 years ago by gwr

service states and data

comment:1 Changed 5 years ago by ramshankar

Could you post the output of sudo ifconfig -a here please?

comment:2 Changed 5 years ago by ereitmaier

I have the same problem, hereby my ifconfig -a output:

root@opensolaris:~# ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

e1000g0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2

inet 0.0.0.0 netmask ff000000 ether 0:15:b7:c:bb:ed

wpi0: flags=1000802<BROADCAST,MULTICAST,IPv4> mtu 1500 index 3

inet 0.0.0.0 netmask 0 ether 0:1b:77:3e:5a:dd

vboxnet0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 4

inet 0.0.0.0 netmask ff000000 ether 0:8:27:4e:b5:49

lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1

inet6 ::1/128

e1000g0: flags=2004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index 2

inet6 fe80::215:b7ff:fe0c:bbed/10 ether 0:15:b7:c:bb:ed

root@opensolaris:~#

comment:3 Changed 5 years ago by ramshankar

I wasn't able to reproduce this with NWAM and vboxnet0 on OpenSolaris 08.11. Could you try one thing please.

Change /etc/nwam/llp to have

vboxnet0     static 1.1.1.1

and see if that helps?

comment:4 Changed 5 years ago by ereitmaier

That helped. I need to say that I am using punchin to connect to SWAN, so that might be related.

comment:5 Changed 5 years ago by gwr

That work-around (change /etc/nwam/llp - as described above) lets "nwam" startup without any problems. Thank-you very much!

comment:6 Changed 5 years ago by ramshankar

Okay, the current behaviour for vboxnet is it doesn't require DHCP on the host as when you use host-only networking and start a VM with VirtualBox, the IP you assign in the global Preferences in VirtualBox would be assigned to vboxnet0 regardless of what IP it vboxnet has. So putting a 1.1.1.1 static IP there for nwam should be fine.

Thank you for the feedback.

comment:7 Changed 5 years ago by gwr

Putting this line in /etc/nwam/llp also works OK:

vboxnet0 static 0.0.0.0

Maybe better than the above suggestion?

Changed 5 years ago by gwr

debug log from nwam

comment:8 Changed 5 years ago by ramshankar

Yes that actually looks better, anything to prevent nwam/dhcpagent from kicking in. Thanks again for trying with 0.0.0.0.

comment:9 Changed 5 years ago by gwr

Oops, posted too soon on this: (doesn't work)

vboxnet0 static 0.0.0.0

It has to be non-zero, or nwam still tries to do dhcp on the i/f. Just need to pick something that can't interfere with any legitimate destination addresses, i.e. 127.1.1.1

comment:10 Changed 5 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to fixed

comment:11 Changed 5 years ago by sandervl73

  • Summary changed from vboxnet0 causes ndp,nwam startup to fail to vboxnet0 causes ndp,nwam startup to fail -> fixed in 2.2.2

comment:12 Changed 4 years ago by Barron123

Resource:  go to my pc

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use