Quantcast
Channel: VMware Communities : Discussion List - VMware Fusion® (for Mac)
Viewing all articles
Browse latest Browse all 12061

Bridge mode only not working

$
0
0

I'm running VMware Fusion 6.01 on Mountain Lion (10.8.3). I started off over a year ago with Fusion 4.x on Lion.

 

I tried to install a Linux VM (Xubuntu) from a LiveCD of a product we're using, with the network adapter setup in bridged mode. I could never get that working, so under the assumption that it was an issue with the LiveCD, I moved on to Ubuntu 12.04.

 

I'm still not able to get bridged mode to work completely. The VM can work just fine in NAT mode, with functionality as expected.

 

In bridged mode, the guest (10.1.2.49) can access the host (10.1.2.62), and the host can access the guest, but no one else on the network can see the guest, and the guest can't communicate with anyone else on the network.

 

The host sees the following:

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384

  options=3<RXCSUM,TXCSUM>

  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1

  inet 127.0.0.1 netmask 0xff000000

  inet6 ::1 prefixlen 128

gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280

stf0: flags=0<> mtu 1280

en0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500

  options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4>

  ether 3c:07:54:79:3e:17

  inet6 fe80::3e07:54ff:fe79:3e17%en0 prefixlen 64 scopeid 0x4

  inet 10.1.2.62 netmask 0xffffff00 broadcast 10.1.2.255

  media: autoselect (100baseTX <full-duplex>)

  status: active

en1: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500

  ether 7c:c3:a1:a1:f5:d1

  media: autoselect (<unknown type>)

  status: inactive

p2p0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2304

  ether 0e:c3:a1:a1:f5:d1

  media: autoselect

  status: inactive

fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078

  lladdr 3c:07:54:ff:fe:c1:2a:a6

  media: autoselect <full-duplex>

  status: inactive

utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

  inet6 fe80::7422:8404:8575:f2a4%utun0 prefixlen 64 scopeid 0x8

  inet6 fd29:87fb:70f9:626d:7422:8404:8575:f2a4 prefixlen 64

utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

  inet6 fe80::7422:8404:8575:f2a4%utun1 prefixlen 64 scopeid 0x9

  inet6 fd00:6587:52d7:413:7422:8404:8575:f2a4 prefixlen 64

vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

  ether 00:50:56:c0:00:01

  inet 172.16.247.1 netmask 0xffffff00 broadcast 172.16.247.255

vmnet8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

  ether 00:50:56:c0:00:08

  inet 172.16.117.1 netmask 0xffffff00 broadcast 172.16.117.255

 

On the guest, I tried turning off the first adapter created during the creation of the vm (Network Adapter), disabled it within the guest, rebooted the guest, and then added a new adapter (Network Adapter 2), to no avail. The guest adapter is manually configured (no DHCP). The following is what the interfaces look like on the guest side:

 

eth0      Link encap:Ethernet  HWaddr 00:0c:29:9a:75:09 

          UP BROADCAST MULTICAST  MTU:1500  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:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 

 

eth1      Link encap:Ethernet  HWaddr 00:0c:29:9a:75:13 

          inet addr:10.1.2.49  Bcast:10.1.2.255  Mask:255.255.255.0

          inet6 addr: fe80::20c:29ff:fe9a:7513/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:10667 errors:0 dropped:8 overruns:0 frame:0

          TX packets:2804 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:1042535 (1.0 MB)  TX bytes:254172 (254.1 KB)

 

 

lo        Link encap:Local Loopback 

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:920 errors:0 dropped:0 overruns:0 frame:0

          TX packets:920 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:70352 (70.3 KB)  TX bytes:70352 (70.3 KB)

 

 

I've disabled any unused network adapters on the host (wifi, bluetooth pan); still no connectivity outside of the guest-to-host.

 

I've checked my Console logs and don't see any obvious errors related to VMware in there, though being new to this config, I could easily be missing something.

 

Where do I go from here? This seems like such a simple thing, but I've not been able to find any supporting docu that details the file structure in place for configuring Fusion, nor much in the way of troubleshooting this outside of several posts here in the forums.

 

Thanks for any insight you might be able to shed, in advance!


Viewing all articles
Browse latest Browse all 12061

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>