Oracle Linux 6.1 guest on Virtualbox 4.1 can't connect to network
Clash Royale CLAN TAG#URR8PPP
up vote
7
down vote
favorite
I just installed VirtualBox 4.1 on my Windows system, and then added a Solaris 11 Express guest and an Oracle Linux 6.1 guest. Both installs went smoothly. But while the Solaris 11 guest has network access, the Oracle Linux box can't connect to the network.
Both guests are using the same default network settings (NAT). I'm at a loss -- not sure what I need to configure on the OL6.1 side.
To test basic network connectivity, I tried: ping www.google.com. No problems with the Solaris guest. On the OL6.1 guest:
# ping www.google.com
ping: unknown host www.google.com
# ping 209.85.175.99
connect: Network is unreachable
Is there some sort of network setup that's required on OL6.1 that wasn't required on Solaris11? Thanks in advance.
output from ifconfig -a:
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 08:00:27:8E:A1:42
inet6 addr: fe80::a00:27ff:fe8e:a142/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:328 (328.0 b)
lo Link encap: Local Loopback
inet addr:127.0.0.1 Mask:255.0.0
inet6addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen: 0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
linux networking rhel virtualbox
edited Jan 23 '12 at 2:17
Kevin
26.7k106198
asked Nov 4 '11 at 22:30
Suzanne
38114
add a comment |
up vote
7
down vote
favorite
I just installed VirtualBox 4.1 on my Windows system, and then added a Solaris 11 Express guest and an Oracle Linux 6.1 guest. Both installs went smoothly. But while the Solaris 11 guest has network access, the Oracle Linux box can't connect to the network.
Both guests are using the same default network settings (NAT). I'm at a loss -- not sure what I need to configure on the OL6.1 side.
To test basic network connectivity, I tried: ping www.google.com. No problems with the Solaris guest. On the OL6.1 guest:
# ping www.google.com
ping: unknown host www.google.com
# ping 209.85.175.99
connect: Network is unreachable
Is there some sort of network setup that's required on OL6.1 that wasn't required on Solaris11? Thanks in advance.
output from ifconfig -a:
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 08:00:27:8E:A1:42
inet6 addr: fe80::a00:27ff:fe8e:a142/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:328 (328.0 b)
lo Link encap: Local Loopback
inet addr:127.0.0.1 Mask:255.0.0
inet6addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen: 0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
linux networking rhel virtualbox
edited Jan 23 '12 at 2:17
Kevin
26.7k106198
asked Nov 4 '11 at 22:30
Suzanne
38114
Please post the output ofifconfig -a. During the installation, did you leave the IPv4 settings on the automatic method (step 10 in the instructions)?
– Gilles
Nov 4 '11 at 22:40
During installation, I was never given the option to configure the network (step 10 in your instructions). I'm running 6.1; maybe I should go back and try 6.0?
– Suzanne
Nov 4 '11 at 22:53
add a comment |
up vote
7
down vote
favorite
up vote
7
down vote
favorite
I just installed VirtualBox 4.1 on my Windows system, and then added a Solaris 11 Express guest and an Oracle Linux 6.1 guest. Both installs went smoothly. But while the Solaris 11 guest has network access, the Oracle Linux box can't connect to the network.
Both guests are using the same default network settings (NAT). I'm at a loss -- not sure what I need to configure on the OL6.1 side.
To test basic network connectivity, I tried: ping www.google.com. No problems with the Solaris guest. On the OL6.1 guest:
# ping www.google.com
ping: unknown host www.google.com
# ping 209.85.175.99
connect: Network is unreachable
Is there some sort of network setup that's required on OL6.1 that wasn't required on Solaris11? Thanks in advance.
output from ifconfig -a:
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 08:00:27:8E:A1:42
inet6 addr: fe80::a00:27ff:fe8e:a142/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:328 (328.0 b)
lo Link encap: Local Loopback
inet addr:127.0.0.1 Mask:255.0.0
inet6addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen: 0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
linux networking rhel virtualbox
edited Jan 23 '12 at 2:17
Kevin
26.7k106198
asked Nov 4 '11 at 22:30
Suzanne
38114
I just installed VirtualBox 4.1 on my Windows system, and then added a Solaris 11 Express guest and an Oracle Linux 6.1 guest. Both installs went smoothly. But while the Solaris 11 guest has network access, the Oracle Linux box can't connect to the network.
Both guests are using the same default network settings (NAT). I'm at a loss -- not sure what I need to configure on the OL6.1 side.
To test basic network connectivity, I tried: ping www.google.com. No problems with the Solaris guest. On the OL6.1 guest:
# ping www.google.com
ping: unknown host www.google.com
# ping 209.85.175.99
connect: Network is unreachable
Is there some sort of network setup that's required on OL6.1 that wasn't required on Solaris11? Thanks in advance.
output from ifconfig -a:
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 08:00:27:8E:A1:42
inet6 addr: fe80::a00:27ff:fe8e:a142/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:328 (328.0 b)
lo Link encap: Local Loopback
inet addr:127.0.0.1 Mask:255.0.0
inet6addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen: 0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
linux networking rhel virtualbox
linux networking rhel virtualbox
edited Jan 23 '12 at 2:17
Kevin
26.7k106198
asked Nov 4 '11 at 22:30
Suzanne
38114
edited Jan 23 '12 at 2:17
Kevin
26.7k106198
asked Nov 4 '11 at 22:30
Suzanne
38114
edited Jan 23 '12 at 2:17
Kevin
26.7k106198
edited Jan 23 '12 at 2:17
Kevin
26.7k106198
edited Jan 23 '12 at 2:17
Kevin
26.7k106198
26.7k106198
asked Nov 4 '11 at 22:30
Suzanne
38114
asked Nov 4 '11 at 22:30
Suzanne
38114
asked Nov 4 '11 at 22:30
Suzanne
38114
38114
Please post the output ofifconfig -a. During the installation, did you leave the IPv4 settings on the automatic method (step 10 in the instructions)?
– Gilles
Nov 4 '11 at 22:40
During installation, I was never given the option to configure the network (step 10 in your instructions). I'm running 6.1; maybe I should go back and try 6.0?
– Suzanne
Nov 4 '11 at 22:53
add a comment |
Please post the output ofifconfig -a. During the installation, did you leave the IPv4 settings on the automatic method (step 10 in the instructions)?
– Gilles
Nov 4 '11 at 22:40
During installation, I was never given the option to configure the network (step 10 in your instructions). I'm running 6.1; maybe I should go back and try 6.0?
– Suzanne
Nov 4 '11 at 22:53
Please post the output of
ifconfig -a. During the installation, did you leave the IPv4 settings on the automatic method (step 10 in the instructions)?– Gilles
Nov 4 '11 at 22:40
Please post the output of
ifconfig -a. During the installation, did you leave the IPv4 settings on the automatic method (step 10 in the instructions)?– Gilles
Nov 4 '11 at 22:40
During installation, I was never given the option to configure the network (step 10 in your instructions). I'm running 6.1; maybe I should go back and try 6.0?
– Suzanne
Nov 4 '11 at 22:53
During installation, I was never given the option to configure the network (step 10 in your instructions). I'm running 6.1; maybe I should go back and try 6.0?
– Suzanne
Nov 4 '11 at 22:53
add a comment |
3 Answers
3
active
oldest
votes
up vote
5
down vote
accepted
Given that Oracle Linux is heavily based on Red Hat Enterprise Linux, the network configuration is probably the same. If you didn't need to enter any network parameters during the installation of Solaris, then you're picking up a network address through DHCP. There isn't much call for doing anything else in a NATted virtual machine anyway.
To configure a DHCP client on RHEL, edit the file /etc/sysconfig/network-scripts/ifcfg-eth0 to contain the following lines:
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
Or you can use Network Manager instead (it'll give you the same kind of network configuration through a desktop icon that Solaris has, and in fact I believe it is more powerful than Solaris's — not that you really need that in a VM).
answered Nov 4 '11 at 23:14
Gilles
522k12610401570
add a comment |
up vote
1
down vote
Probably the specified default router might be incorrect. To find out, do
netstat -r
to see the routing table. Locate the default route (destination 0.0.0.0), and then ping the default router...i.e.
ping 10.0.0.1
answered Nov 4 '11 at 22:39
mdpc
4,90521835
1
on the OL6.1 guest, netstat -r just displays the header as output; no entries in the routing tables. On the Solaris guest, netstat -r displays info about the default router.
– Suzanne
Nov 4 '11 at 22:48
1
Unlikely (and that's confirmed by theifconfigoutput). On simple setups, it's rare that the routing is wrong; here, as usual, the issue is that there's no IP connectivity at all.
– Gilles
Nov 4 '11 at 23:16
add a comment |
up vote
0
down vote
Centos/RHEL
Edit the file /etc/sysconfig/network-scripts/interface
ONBOOT=yes
and restart network
it should work !!
answered Nov 20 at 17:10
Nikhil Babu
12
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
Given that Oracle Linux is heavily based on Red Hat Enterprise Linux, the network configuration is probably the same. If you didn't need to enter any network parameters during the installation of Solaris, then you're picking up a network address through DHCP. There isn't much call for doing anything else in a NATted virtual machine anyway.
To configure a DHCP client on RHEL, edit the file /etc/sysconfig/network-scripts/ifcfg-eth0 to contain the following lines:
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
Or you can use Network Manager instead (it'll give you the same kind of network configuration through a desktop icon that Solaris has, and in fact I believe it is more powerful than Solaris's — not that you really need that in a VM).
answered Nov 4 '11 at 23:14
Gilles
522k12610401570
add a comment |
up vote
5
down vote
accepted
Given that Oracle Linux is heavily based on Red Hat Enterprise Linux, the network configuration is probably the same. If you didn't need to enter any network parameters during the installation of Solaris, then you're picking up a network address through DHCP. There isn't much call for doing anything else in a NATted virtual machine anyway.
To configure a DHCP client on RHEL, edit the file /etc/sysconfig/network-scripts/ifcfg-eth0 to contain the following lines:
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
Or you can use Network Manager instead (it'll give you the same kind of network configuration through a desktop icon that Solaris has, and in fact I believe it is more powerful than Solaris's — not that you really need that in a VM).
answered Nov 4 '11 at 23:14
Gilles
522k12610401570
add a comment |
up vote
5
down vote
accepted
up vote
5
down vote
accepted
Given that Oracle Linux is heavily based on Red Hat Enterprise Linux, the network configuration is probably the same. If you didn't need to enter any network parameters during the installation of Solaris, then you're picking up a network address through DHCP. There isn't much call for doing anything else in a NATted virtual machine anyway.
To configure a DHCP client on RHEL, edit the file /etc/sysconfig/network-scripts/ifcfg-eth0 to contain the following lines:
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
Or you can use Network Manager instead (it'll give you the same kind of network configuration through a desktop icon that Solaris has, and in fact I believe it is more powerful than Solaris's — not that you really need that in a VM).
answered Nov 4 '11 at 23:14
Gilles
522k12610401570
Given that Oracle Linux is heavily based on Red Hat Enterprise Linux, the network configuration is probably the same. If you didn't need to enter any network parameters during the installation of Solaris, then you're picking up a network address through DHCP. There isn't much call for doing anything else in a NATted virtual machine anyway.
To configure a DHCP client on RHEL, edit the file /etc/sysconfig/network-scripts/ifcfg-eth0 to contain the following lines:
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
Or you can use Network Manager instead (it'll give you the same kind of network configuration through a desktop icon that Solaris has, and in fact I believe it is more powerful than Solaris's — not that you really need that in a VM).
answered Nov 4 '11 at 23:14
Gilles
522k12610401570
answered Nov 4 '11 at 23:14
Gilles
522k12610401570
answered Nov 4 '11 at 23:14
Gilles
522k12610401570
answered Nov 4 '11 at 23:14
Gilles
522k12610401570
522k12610401570
add a comment |
add a comment |
up vote
1
down vote
Probably the specified default router might be incorrect. To find out, do
netstat -r
to see the routing table. Locate the default route (destination 0.0.0.0), and then ping the default router...i.e.
ping 10.0.0.1
answered Nov 4 '11 at 22:39
mdpc
4,90521835
1
on the OL6.1 guest, netstat -r just displays the header as output; no entries in the routing tables. On the Solaris guest, netstat -r displays info about the default router.
– Suzanne
Nov 4 '11 at 22:48
1
Unlikely (and that's confirmed by theifconfigoutput). On simple setups, it's rare that the routing is wrong; here, as usual, the issue is that there's no IP connectivity at all.
– Gilles
Nov 4 '11 at 23:16
add a comment |
up vote
1
down vote
Probably the specified default router might be incorrect. To find out, do
netstat -r
to see the routing table. Locate the default route (destination 0.0.0.0), and then ping the default router...i.e.
ping 10.0.0.1
answered Nov 4 '11 at 22:39
mdpc
4,90521835
1
on the OL6.1 guest, netstat -r just displays the header as output; no entries in the routing tables. On the Solaris guest, netstat -r displays info about the default router.
– Suzanne
Nov 4 '11 at 22:48
1
Unlikely (and that's confirmed by theifconfigoutput). On simple setups, it's rare that the routing is wrong; here, as usual, the issue is that there's no IP connectivity at all.
– Gilles
Nov 4 '11 at 23:16
add a comment |
up vote
1
down vote
up vote
1
down vote
Probably the specified default router might be incorrect. To find out, do
netstat -r
to see the routing table. Locate the default route (destination 0.0.0.0), and then ping the default router...i.e.
ping 10.0.0.1
answered Nov 4 '11 at 22:39
mdpc
4,90521835
Probably the specified default router might be incorrect. To find out, do
netstat -r
to see the routing table. Locate the default route (destination 0.0.0.0), and then ping the default router...i.e.
ping 10.0.0.1
answered Nov 4 '11 at 22:39
mdpc
4,90521835
answered Nov 4 '11 at 22:39
mdpc
4,90521835
answered Nov 4 '11 at 22:39
mdpc
4,90521835
answered Nov 4 '11 at 22:39
mdpc
4,90521835
4,90521835
1
on the OL6.1 guest, netstat -r just displays the header as output; no entries in the routing tables. On the Solaris guest, netstat -r displays info about the default router.
– Suzanne
Nov 4 '11 at 22:48
1
Unlikely (and that's confirmed by theifconfigoutput). On simple setups, it's rare that the routing is wrong; here, as usual, the issue is that there's no IP connectivity at all.
– Gilles
Nov 4 '11 at 23:16
add a comment |
1
on the OL6.1 guest, netstat -r just displays the header as output; no entries in the routing tables. On the Solaris guest, netstat -r displays info about the default router.
– Suzanne
Nov 4 '11 at 22:48
1
Unlikely (and that's confirmed by theifconfigoutput). On simple setups, it's rare that the routing is wrong; here, as usual, the issue is that there's no IP connectivity at all.
– Gilles
Nov 4 '11 at 23:16
1
1
on the OL6.1 guest, netstat -r just displays the header as output; no entries in the routing tables. On the Solaris guest, netstat -r displays info about the default router.
– Suzanne
Nov 4 '11 at 22:48
on the OL6.1 guest, netstat -r just displays the header as output; no entries in the routing tables. On the Solaris guest, netstat -r displays info about the default router.
– Suzanne
Nov 4 '11 at 22:48
1
1
Unlikely (and that's confirmed by the
ifconfig output). On simple setups, it's rare that the routing is wrong; here, as usual, the issue is that there's no IP connectivity at all.– Gilles
Nov 4 '11 at 23:16
Unlikely (and that's confirmed by the
ifconfig output). On simple setups, it's rare that the routing is wrong; here, as usual, the issue is that there's no IP connectivity at all.– Gilles
Nov 4 '11 at 23:16
add a comment |
up vote
0
down vote
Centos/RHEL
Edit the file /etc/sysconfig/network-scripts/interface
ONBOOT=yes
and restart network
it should work !!
answered Nov 20 at 17:10
Nikhil Babu
12
add a comment |
up vote
0
down vote
Centos/RHEL
Edit the file /etc/sysconfig/network-scripts/interface
ONBOOT=yes
and restart network
it should work !!
answered Nov 20 at 17:10
Nikhil Babu
12
add a comment |
up vote
0
down vote
up vote
0
down vote
Centos/RHEL
Edit the file /etc/sysconfig/network-scripts/interface
ONBOOT=yes
and restart network
it should work !!
answered Nov 20 at 17:10
Nikhil Babu
12
Centos/RHEL
Edit the file /etc/sysconfig/network-scripts/interface
ONBOOT=yes
and restart network
it should work !!
answered Nov 20 at 17:10
Nikhil Babu
12
answered Nov 20 at 17:10
Nikhil Babu
12
answered Nov 20 at 17:10
Nikhil Babu
12
answered Nov 20 at 17:10
Nikhil Babu
12
12
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f23985%2foracle-linux-6-1-guest-on-virtualbox-4-1-cant-connect-to-network%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Please post the output of
ifconfig -a. During the installation, did you leave the IPv4 settings on the automatic method (step 10 in the instructions)?– Gilles
Nov 4 '11 at 22:40
During installation, I was never given the option to configure the network (step 10 in your instructions). I'm running 6.1; maybe I should go back and try 6.0?
– Suzanne
Nov 4 '11 at 22:53