VirtualBox

Opened 16 years ago

Closed 15 years ago

#1857 closed defect (fixed)

Network not working in OpenSolaris 2008.5 guest

Reported by: DevUrandom Owned by:
Component: network Version: VirtualBox 1.6.2
Keywords: Cc:
Guest type: Solaris Host type: Linux

Description

The network in a freshly setup OpenSolaris 2008.5 guest system, with guest-additions installed (addpkg -d VBox*.pgk), is completely not working. The machine that was setup as nameserver via DHCP (10.0.2.3) does not respond to pings and does not resolve network names, pinging "raw" IP Addresses does not work, etc.

I will attach the config+logs.

$ netstat -nr Routing Table: IPv4

Destination Gateway Flags Ref Use Interface


default 10.0.2.2 UG 1 2 pcn0 10.0.2.0 10.0.2.15 U 1 3 pcn0 127.0.0.1 127.0.0.1 UH 1 43 lo0

$ ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

pcn0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 1500 index 2

inet 10.0.2.15 netmask ffffff00 broadcast 10.0.2.255 ether 8:0:27:a8:fc:c

$ cat /etc/resolv.conf domain local nameserver 10.0.2.3

$ traceroute 10.0.2.3 traceroute to 10.0.2.3 (10.0.2.3), 30 hops max, 40 byte packets

1 10.0.2.2 (10.0.2.2) 1.404 ms 1.492 ms 1.377 ms 2 * * *

...

$ traceroute 64.233.187.99 # google.com traceroute to 64.233.187.99 (64.233.187.99), 30 hops max, 40 byte packets

1 10.0.2.2 (10.0.2.2) 1.459 ms 1.468 ms 1.370 ms 2 * * *

...

Attachments (2)

OpenSolaris 2008.5.xml (2.9 KB ) - added by DevUrandom 16 years ago.
VBox.log (31.7 KB ) - added by DevUrandom 16 years ago.

Download all attachments as: .zip

Change History (7)

by DevUrandom, 16 years ago

Attachment: OpenSolaris 2008.5.xml added

by DevUrandom, 16 years ago

Attachment: VBox.log added

comment:1 by Robert Munteanu, 16 years ago

I have encountered the same problem, and after multiple reboots ( and changing the NAT network to 192.168/16 ) it started working after setting the NIC type to PCnet-PCI II.

in reply to:  1 ; comment:2 by DevUrandom, 16 years ago

Replying to rombert:

I have encountered the same problem, and after multiple reboots ( and changing the NAT network to 192.168/16 ) it started working after setting the NIC type to PCnet-PCI II.

Can you give a more detailed explanation of that process? Where/how I can change the NAT network, etc?

PS: The current SXCE (snv93) seems to work. Maybe it is a snv86 Kernel problem?

in reply to:  2 comment:3 by Robert Munteanu, 16 years ago

Replying to DevUrandom:

Replying to rombert:

I have encountered the same problem, and after multiple reboots ( and changing the NAT network to 192.168/16 ) it started working after setting the NIC type to PCnet-PCI II.

Can you give a more detailed explanation of that process? Where/how I can change the NAT network, etc?

I have changed the NAT network with

VBoxManage modifyvm "<vm_name>" -natnet1 "192.168/16"

However that did not work but I tried it because the 10.x range is also used internally for the local network.

As for the NIC type, I changed that using the VirtualBox GUI.

PS: The current SXCE (snv93) seems to work. Maybe it is a snv86 Kernel problem?

It's a possibility that it is a network driver problem ( since changing the NIC type solved this ).

comment:4 by Frank Mehnert, 16 years ago

Component: othernetwork

comment:5 by Frank Mehnert, 15 years ago

Resolution: fixed
Status: newclosed

Please reopen if this is still an issue with the latest release (2.2.0). Make sure to select an E1000 NIC.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use