From owner-freebsd-stable@FreeBSD.ORG Wed Oct 29 04:32:33 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 460B21065675 for ; Wed, 29 Oct 2008 04:32:33 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (bitblocks.com [64.142.15.60]) by mx1.freebsd.org (Postfix) with ESMTP id 211AC8FC1C for ; Wed, 29 Oct 2008 04:32:33 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id DC80C5B46; Tue, 28 Oct 2008 21:14:28 -0700 (PDT) To: "Marc G. Fournier" In-reply-to: Your message of "Wed, 29 Oct 2008 00:35:35 -0300." References: Comments: In-reply-to "Marc G. Fournier" message dated "Wed, 29 Oct 2008 00:35:35 -0300." Date: Tue, 28 Oct 2008 21:14:28 -0700 From: Bakul Shah Message-Id: <20081029041428.DC80C5B46@mail.bitblocks.com> Cc: Michael Proto , freebsd-stable@freebsd.org, freebsd-net@freebsd.org Subject: Re: Problem with Bridging ... and bge devices under FreeBSD 7.x? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2008 04:32:33 -0000 On Wed, 29 Oct 2008 00:35:35 -0300 "Marc G. Fournier" wrote: > netstat -nr on the 192 server shows the IP to be at: > > > netstat -nr | grep 168.1.100 > 192.168.1.100 52:54:00:12:34:56 UHLW 1 1 fxp0 1128 > > which is very odd, as that MAC address is not found via ifconfig -a: > > > ifconfig -a | grep 52 > > > > while arp -a also shows the 52:54 MAC, although MACs for the ifconfig -a are, > > in fact: > > > ifconfig -a | grep ether > ether 00:02:b3:ee:da:3e > ether 5e:d1:e6:8b:55:50 > ether 00:bd:25:18:6d:00 The setup you get with a tap device talking to qemu is this: [host]-tap0----qemu---ed0-[VM] Each end has its own mac address. The VM's NIC (ed0 or rl0 or whatever) gets addresses like 52:54:00:12:34:56. The host will have an arp entry for it once the VM sends an arp packet. But tap0 will have an address assigned by the tap driver, something like 00:bd:xx:xx:xx. If you have two VMs running at the same time on two different machines and they both have identical MAC addresses, that could be part of your problem. But your network topolgy is still not clear. What would help is something like this: You have: machine A (runs VM A1). machine B (runs VM B1). machine C (runs windows). Can you ping from A to C? Can you ping from B to C? Can you ping from A to A1? Can you ping from B to B1? Can you ping from A1 to C? Can you ping from B1 to C? Can you ping from C to A1? Can you ping from C to B1? All of the above should work. Next you can try tcpdump on tap devices to see what is going on. If you are still stumped provide ifconfig -a output on A, B, C, A1 and B1. On windows machine you can do ipconfig/all to get at this information (IIRC).