Opened 16 years ago
Closed 16 years ago
#2980 closed defect (fixed)
Networking not working under Linux 2.1
Reported by: | JJ | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 2.1.0 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
Hello,
I'm running VB under Jeos (ubuntu) 8.04 and have VB 2.1.0 installed. Guest OS is also Jeos.
I'm trying to get bridging working so that I can use a public ip space ip in VB. The VB manual tells me that with VB 2.1.0 that all i need to do i s select 'Host Interface' and simply select one of my active net devices, currently 'eth0', for bridging.
However, when i boot into linux in VB, all i get is the 'lo' device. Attempts to bring up eth0 fail via 'sudo ifup eth0' w/ error message "No such device".
Thoughts?
Thanks! JJ
Attachments (2)
Change History (9)
comment:1 by , 16 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:2 by , 16 years ago
I've already done so and have another person thats replied to my post having the same issue. Can you tell me how to resolve?
http://forums.virtualbox.org/viewtopic.php?t=12926&unwatch=topic
Thanks, JJ
comment:3 by , 16 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
Could you then attach the VBox.log of such a session?
comment:4 by , 16 years ago
I've removed your previous comments and attached your log files. There is an attach button above!
comment:6 by , 16 years ago
I assume that your guest is detecting a different MAC address. Please could you attach the output of dmesg
from your guest when you attached the hostif to eth0? And the output of dmesg
again when you selected NAT?
comment:7 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
No response, closing. Before re-opening please check the latest release 2.2.2.
Could you please visit our forum and ask questions there? When you're sure it's a bug, then you can reopen this defect again.