From owner-freebsd-questions Sun Feb 18 11:30: 9 2001 Delivered-To: freebsd-questions@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id 25FE237B4EC for ; Sun, 18 Feb 2001 11:30:05 -0800 (PST) Received: from horseplay.demonadsltrial.co.uk ([193.195.64.157] helo=horseplay.horseplay.demon.co.uk) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 14UZX2-00003H-0X for questions@freebsd.org; Sun, 18 Feb 2001 19:30:04 +0000 Message-Id: <5.0.2.1.1.20010218192444.032a6b20@pop3.demon.co.uk> X-Sender: horseplay@pop3.demon.co.uk X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Sun, 18 Feb 2001 19:33:10 +0000 To: questions@freebsd.org From: Darren Evans Subject: Re: vmware 2 bridged networking In-Reply-To: <20010218081904.E5280@arrakis.desert-power.org> References: <5.0.2.1.1.20010217224534.00ad41f0@pop3.demon.co.uk> <5.0.2.1.1.20010217224534.00ad41f0@pop3.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark, Hmmm did'nt do the trick. I noticed my IP address is listed on the vmnet1 interface and not xe0, presumably this should not be the case. If it is, how does this work? Maybe someone else could share their "vmware + FreeBSD" network settings. # ifconfig -a lp0: flags=8810 mtu 1500 faith0: flags=8000 mtu 1500 gif0: flags=8010 mtu 1280 gif1: flags=8010 mtu 1280 gif2: flags=8010 mtu 1280 gif3: flags=8010 mtu 1280 lo0: flags=8049 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 ppp0: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 vmnet1: flags=8843 mtu 1500 inet 192.168.254.210 netmask 0xffffff00 broadcast 192.168.254.255 inet6 fe80::2bd:a5ff:fe04:1%vmnet1 prefixlen 64 scopeid 0xa ether 00:bd:a5:04:00:01 xe0: flags=8843 mtu 1500 inet 192.168.254.205 netmask 0xffffff00 broadcast 192.168.254.255 inet6 fe80::210:a4ff:fed2:6cf7%xe0 prefixlen 64 scopeid 0xb ether 00:10:a4:d2:6c:f7 media: autoselect (10baseT/UTP) supported media: autoselect 10baseT/UTP 100baseTX # netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.254.254 UGSc 0 0 vmnet1 127.0.0.1 127.0.0.1 UH 1 42 lo0 192.168.254 link#10 UC 0 0 vmnet1 => 192.168.254.205 link#10 UHLW 0 4 vmnet1 => 192.168.254.254 link#10 UHLW 1 2 vmnet1 => Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%lo0/64 fe80::1%lo0 Uc lo0 fe80::%vmnet1/64 link#10 UC vmnet1 fe80::%xe0/64 link#11 UC xe0 ff01::/32 ::1 U lo0 ff02::%lo0/32 fe80::1%lo0 UC lo0 ff02::%vmnet1/32 link#10 UC vmnet1 ff02::%xe0/32 link#11 UC xe0 At 08:19 18/02/01 -0500, Mark B. Withers wrote: >Darren, > >If you issue an > >ifconfig -a > >command, does it say "noarp" on your xe0 interface? > >If so you can eneble it with > >ifconfig xe0 arp >On Sat, Feb 17, 2001 at 06:01:45PM -0500, Darren Evans wrote: > > > > FreeBSD box 192.168.254.205 xe0 > > vmnet1 192.168.254.210 vmnet1 > > Gateway 192.168.254.254 default > > > > After installing bridged networking within vmware2 I cannot > > access my default gateway. > > > > I can ping vmnet1 but not "xe0" or the "default gateway". > > > > arp -a does nothing. > > > > sudo route add 192.168.254.254 default does nothing either. > > > > I have seen this. > > > http://www.vmware.com/support/reference/linux/networking_linux.html#changemac > > I think the issue is to do with not finding a MAC address for xe0 because > > vmware2 has "clashed?" somehow. > > > > To sum up, vmware no longer runs and has taken apart my networking. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message