From owner-freebsd-net@FreeBSD.ORG  Thu Mar 17 00:06:09 2005
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E741C16A4CE
	for <freebsd-net@freebsd.org>; Thu, 17 Mar 2005 00:06:09 +0000 (GMT)
Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C60C243D48
	for <freebsd-net@freebsd.org>; Thu, 17 Mar 2005 00:06:06 +0000 (GMT)
	(envelope-from maxim@macomnet.ru)
Received-SPF: pass (mp2.macomnet.net: domain of maxim@macomnet.ru designates
	127.0.0.1 as permitted sender) receiver=mp2.macomnet.net; client_ip=127.0.0.1;
	envelope-from=maxim@macomnet.ru;
Received: from localhost (localhost [127.0.0.1])
	by mp2.macomnet.net (8.12.11/8.12.11) with ESMTP id j2H00sAG070172;
	Thu, 17 Mar 2005 03:00:54 +0300 (MSK)
	(envelope-from maxim@macomnet.ru)
Date: Thu, 17 Mar 2005 03:00:53 +0300 (MSK)
From: Maxim Konovalov <maxim@macomnet.ru>
To: Nerius Landys <nlandys@bioeng.ucsd.edu>
In-Reply-To: <Pine.SGI.4.58.0503161125380.15799222@be-research.ucsd.edu>
Message-ID: <20050317025907.G69637@mp2.macomnet.net>
References: <Pine.SGI.4.58.0503161125380.15799222@be-research.ucsd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-net@freebsd.org
Subject: Re: transparent bridge and ARP proxy confusion
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2005 00:06:10 -0000

[...]
> On host 192.168.0.2, the tcpdump output:
>
>   00:10:53.445868 0:2:b3:da:50:ba Broadcast arp 60:
>                     arp who-has 192.168.0.2 tell 192.168.0.6
>   00:10:53.445888 0:e:c:68:e3:94 0:2:b3:da:50:ba arp 42:
>                     arp reply 192.168.0.2 is-at 0:e:c:68:e3:94
>   00:10:53.446615 0:2:b3:da:50:bb 0:e:c:68:e3:94 ip 98:
>                     192.168.0.6 > 192.168.0.2: icmp: echo request
>   00:10:53.446634 0:e:c:68:e3:94 0:2:b3:da:50:ba ip 98:
>                     192.168.0.2 > 192.168.0.6: icmp: echo reply
>   00:10:58.442471 0:e:c:68:e3:94 0:2:b3:da:50:ba arp 42:
>                     arp who-has 192.168.0.6 tell 192.168.0.2
>   00:10:58.442925 0:2:b3:da:50:bb 0:e:c:68:e3:94 arp 60:
>                     arp reply 192.168.0.6 is-at 0:2:b3:da:50:bb

What's the behaviour is observed with TCP or UDP?  Is it the same?

-- 
Maxim Konovalov