X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9D9C232A06A for ; Thu, 21 Oct 2004 18:43:01 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 02092-05 for ; Thu, 21 Oct 2004 17:42:51 +0000 (GMT) Received: from pns.mm.eutelsat.org (pns.mm.eutelsat.org [194.214.173.227]) by svr1.postgresql.org (Postfix) with ESMTP id 6696C329E76 for ; Thu, 21 Oct 2004 18:42:49 +0100 (BST) Received: from nts-03.mm.eutelsat.org (localhost [127.0.0.1]) by pns.mm.eutelsat.org (8.11.6/linuxconf) with ESMTP id i9LHeip17786; Thu, 21 Oct 2004 19:40:44 +0200 Received: from [127.0.0.1] (accesspoint.mm.eutelsat.org [194.214.173.4]) by nts-03.mm.eutelsat.org (8.11.6/linuxconf) with ESMTP id i9LHgmf30530; Thu, 21 Oct 2004 19:42:48 +0200 Message-ID: <4177F50F.8040904@mbigroup.it> Date: Thu, 21 Oct 2004 19:42:39 +0200 From: Gaetano Mendola User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: jak@uiuc.edu Cc: Gaetano Mendola , Bruno Wolff III , pgsql-admin@postgresql.org Subject: Re: NIC to NIC connection References: <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> <41776E45.2070109@bigfoot.com> <20041021151015.GA21697@uiuc.edu> <4177EC64.30009@mbigroup.it> <20041021171412.GK21697@uiuc.edu> In-Reply-To: <20041021171412.GK21697@uiuc.edu> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/295 X-Sequence-Number: 15288 Jay A. Kreibich wrote: > On Thu, Oct 21, 2004 at 07:05:40PM +0200, Gaetano Mendola scratched on the wall: > > >>We have some switches that are able to do ip routing too... :-( > > > So called "layer-three switches" are a whole different game. Ok that's explain all, I was able to create two different VLAN's with a cable between two ports ( in order to simulate two different switches), each port was appartaining to a different VLAN and I was seeing ARPREQUEST passing by the cable in order to detect the address in the other side, just for fun I replaced the cable with a traffic shaper and all was working very fine... However I wasn't curious enough to see who was the arp request source, may be was not the "router/switcher" but a client that was doing it. Regards Gaetano Mendola