Ubuntu Dapper networking issue

Discussion in 'Parallels Desktop for Mac' started by bobbydigital, Nov 24, 2006.

  1. bobbydigital

    bobbydigital Bit poster

    Messages:
    9
    I have a MBP Core 2 Duo with Ubuntu 6.01 Dapper Drake installed in Parallels. I've followed this installation tutorial and everything went smoothly except that I cannot browse the web in Firefox when connected by the wired ethernet adapter. Airport connectivity worked perfectly out of the box, but no ethernet. On the OS X side however, I can browse the internet fine with the same wired connection.

    I've tried playing around a bit with the Network Adapter settings in Parallels, when I choose Bridged Ethernet with en1: Airport/Wireless Adapter as the default connection setting, and then launch into Ubuntu, the System>Admin>Networking panel shows that my Ethernet connection is working fine, but eth1 is my only Default gateway device option in the pull-down. The same thing happens when I set en0 as the default connection setting in Parallels: in the Ubuntu Networking panel my Ethernet connection is displayed "The interface eth1 is active" but I cannot browse the web. Likewise, eth1 is the only choice for the Default gateway device pull down menu.. in the tutorial above in the Internet Troubleshooting section it seemed like I should be able to choose eth0 or eth1.

    I hope this makes sense, I will obvious clarify any questions and am open to all suggestions. Please help me out as I only have wireless internet access in 25% of the places I typically work at and as a result I am not able to install packages or browse the web for the majority of the time. Thanks!
     
  2. itsdapead

    itsdapead Hunter

    Messages:
    177
    Look at the file /etc/iftab - this associates network interfaces - identified by a hardware address like "00:0C:9F:39:8A:44" - with device names such as "eth0". If this file links eth0 to a hardware address that no longer exists then linux will assign the "real" interface to "eth1".

    Try renaming /etc/iftab to something else then rebooting Linux.
     
  3. bobbydigital

    bobbydigital Bit poster

    Messages:
    9
    I backed up the iftab file and deleted it from /etc. The only difference I noticed that this made was when I pulled up the Networking panel in Ubuntu, the Default gateway device was listed as blank. I can set it as eth0 when I click the menu, but I still only have the one option. Whenever I pull the Networking panel up again that field is blank again. Still no browsing the web. :mad:

    What should my Network Adapter settings be in Parallels? I've had it set at Bridged Ethernet and selected both en1 and en0 from the pull-down menu on different attempts but neither seem to make a difference. I've also left pull-down menu blank. None of this has made a difference so far but if there is a certain setting that is definetly supposed to be selected when trying to connect to the net via ethernet cable in parallels then that's one more variable I can stop playing around and experimenting with.
     
    Last edited: Nov 24, 2006
  4. itsdapead

    itsdapead Hunter

    Messages:
    177
    The bridged network setting in Parallels should be whichever of the MacBook's ports is physically connected to the network (I don't have a MB to hand but I'd guess that en0 is the ethenet port and en1 the airport) - or just "Default Adapter" should work.

    I wonder if "bridged ethernet" networking is what you really need?

    If you're using "bridged" ethernet, then your virtual machine is effectively a separate box with an independent connection to the ethernet (it just happens to be sharing a physical plug with your Mac!) and will need its own IP address - usually automatically via DHCP. That usually sets up the default gateway and DNS server automatically.

    If you're hooked up to a home router that does internet connection sharing that should be fine, but if you are connected to (e.g.) a cable modem (with no router) then it won't work. If you're hooked into a LAN at work/college then your virtual machine may need to be registered with the network admin.

    You may be better off trying "Shared Networking" (on newer versions of Parallels) and making sure that the Linux side is set to get an address automatically via DHCP.
     
  5. bobbydigital

    bobbydigital Bit poster

    Messages:
    9
    Yea that seems like it was it. When I was connected to the cable modem I could not get a connection using the Bridged Ethernet setting whatsoever, but with the same VM settings and a wired connection to my school's LAN I could connect once signing in to the network through its portal. I won't have a chance to reconnect to the modem for a few weeks but I'm betting that changing the network settings to Shared it will work.
     

Share This Page