From kenta@ezyield.com Tue Oct 19 16:06:16 2004 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 5E1E632A4EC for ; Tue, 19 Oct 2004 17:06:16 +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 46997-02 for ; Tue, 19 Oct 2004 16:06:05 +0000 (GMT) Received: from ezyield.com (unknown [209.164.30.206]) by svr1.postgresql.org (Postfix) with ESMTP id 2EE7832A4AE for ; Tue, 19 Oct 2004 17:06:02 +0100 (BST) Received: from localhost (xolinux73g2 [127.0.0.1]) by ezyield.com (8.12.5/8.11.6) with ESMTP id i9JJ2WH6000360 for ; Tue, 19 Oct 2004 12:02:32 -0700 Received: from ezyield.com ([127.0.0.1]) by localhost (mail.ezyield.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32554-04 for ; Tue, 19 Oct 2004 12:02:24 -0700 (PDT) Received: from KENTA (67.108.170.254.ptr.us.xo.net [67.108.170.254]) by ezyield.com (8.12.5/8.11.6) with SMTP id i9JJ1Nn5032723 for ; Tue, 19 Oct 2004 12:01:25 -0700 From: "Kent Anderson" To: "Pgsql-Admin@Postgresql. Org" Subject: NIC to NIC connection Date: Tue, 19 Oct 2004 12:05:05 -0400 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0008_01C4B5D3.DF202810" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal X-Virus-Scanned: by amavisd-new 20040701 at ezyield.com X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=3.5 tagged_above=0.0 required=5.0 tests=FORGED_MUA_OIMO, HTML_30_40, HTML_MESSAGE X-Spam-Level: *** X-Archive-Number: 200410/233 X-Sequence-Number: 15226 This is a multi-part message in MIME format. ------=_NextPart_000_0008_01C4B5D3.DF202810 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit We are upgrading our servers and have run into an interesting situation. It has been proposed that we have a direct connection from the web servers to the postgres server via extra NICs. Has anyone done this before and how big a project would it be to alter ASP and Java applications to make use of such a connection? Before we even waste time installing the NIC's I would like a sense of how hard it is to get postgres to use that kind of a connection vs over the Internet. We are looking to increase communication speed between the web servers and database server as much as possible. Thanks Kent Anderson ------=_NextPart_000_0008_01C4B5D3.DF202810 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
We are up= grading our=20 servers and have run into an interesting situation.  It has been propo= sed=20 that we have a direct connection from the web servers to the postgres= =20 server via extra NICs. Has anyone done this before and how big a project wo= uld=20 it be to alter ASP and Java applications to make use of such a=20 connection?
 
Before we= even waste=20 time installing the NIC's I would like a sense of how hard it is to get pos= tgres=20 to use that kind of a connection vs over the Internet. We are looking to=20 increase communication speed between the web servers and database=20 server as much as possible.
 
Thanks
Kent Anderson
------=_NextPart_000_0008_01C4B5D3.DF202810-- From ajs@crankycanuck.ca Tue Oct 19 16:28:31 2004 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 798E632A05F for ; Tue, 19 Oct 2004 17:28:31 +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 52382-08 for ; Tue, 19 Oct 2004 16:28:24 +0000 (GMT) Received: from smtp103.rog.mail.re2.yahoo.com (smtp103.rog.mail.re2.yahoo.com [206.190.36.81]) by svr1.postgresql.org (Postfix) with SMTP id 51EFF329EB7 for ; Tue, 19 Oct 2004 17:28:23 +0100 (BST) Received: from unknown (HELO phlogiston.dydns.org) (a.sullivan@rogers.com@65.49.125.184 with login) by smtp103.rog.mail.re2.yahoo.com with SMTP; 19 Oct 2004 16:28:22 -0000 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id 62E6C4055; Tue, 19 Oct 2004 12:28:21 -0400 (EDT) Date: Tue, 19 Oct 2004 12:28:21 -0400 From: Andrew Sullivan To: "Pgsql-Admin@Postgresql. Org" Subject: Re: NIC to NIC connection Message-ID: <20041019162821.GJ3359@phlogiston.dyndns.org> Mail-Followup-To: "Pgsql-Admin@Postgresql. Org" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040722i 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/234 X-Sequence-Number: 15227 On Tue, Oct 19, 2004 at 12:05:05PM -0400, Kent Anderson wrote: > We are upgrading our servers and have run into an interesting situation. It > has been proposed that we have a direct connection from the web servers to > the postgres server via extra NICs. > Before we even waste time installing the NIC's I would like a sense of how > hard it is to get postgres to use that kind of a connection vs over the > Internet. I don't understand. What interface other than a NIC are you now using to go "over the Internet"? Or do you mean that you want an _extra_ IP address so that the web servers don't have to compete for the bandwidth? In that case, sure, you'll probably get a minor performance increase, depending on your current network traffic. A -- Andrew Sullivan | ajs@crankycanuck.ca In the future this spectacle of the middle classes shocking the avant- garde will probably become the textbook definition of Postmodernism. --Brad Holland From matt@ymogen.net Tue Oct 19 16:37:54 2004 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 D257032A35F for ; Tue, 19 Oct 2004 17:37:54 +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 57124-07 for ; Tue, 19 Oct 2004 16:37:47 +0000 (GMT) Received: from bayswater1.ymogen.net (host-154-240-27-217.pobox.net.uk [217.27.240.154]) by svr1.postgresql.org (Postfix) with ESMTP id DC1F732A17C for ; Tue, 19 Oct 2004 17:37:45 +0100 (BST) Received: from solent (unknown [213.165.136.10]) by bayswater1.ymogen.net (Postfix) with ESMTP id 1B2A8A2D51; Tue, 19 Oct 2004 17:37:43 +0100 (BST) Reply-To: From: "Matt Clark" To: "'Kent Anderson'" , "'Pgsql-Admin@Postgresql. Org'" Subject: Re: NIC to NIC connection Date: Tue, 19 Oct 2004 17:37:43 +0100 Organization: Ymogen Ltd Message-ID: <00d001c4b5f9$f4d63660$8300a8c0@solent> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00D1_01C4B602.569A9E60" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 In-Reply-To: Importance: Normal X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.9 tagged_above=0.0 required=5.0 tests=HTML_30_40, HTML_FONTCOLOR_BLUE, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200410/235 X-Sequence-Number: 15228 This is a multi-part message in MIME format. ------=_NextPart_000_00D1_01C4B602.569A9E60 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable You would assign a different subnet to the connection, and then tell the servers to connect to the PG server's address on that subnet. No other changes required. Very odd setup though. If you want a 'private' connection then use a switch, rather than needing umpty NICs in the PG server. -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Kent Anderson Sent: 19 October 2004 17:05 To: Pgsql-Admin@Postgresql. Org Subject: [ADMIN] NIC to NIC connection We are upgrading our servers and have run into an interesting situation. It has been proposed that we have a direct connection from the web servers to the postgres server via extra NICs. Has anyone done this before and how big a project would it be to alter ASP and Java applications to make use of such a connection? =20 Before we even waste time installing the NIC's I would like a sense of how hard it is to get postgres to use that kind of a connection vs over the Internet. We are looking to increase communication speed between the web servers and database server as much as possible.=20 =20 Thanks Kent Anderson ------=_NextPart_000_00D1_01C4B602.569A9E60 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
You=20 would assign a different subnet to the connection, and then tell the server= s to=20 connect to the PG server's address on that subnet.  No other changes= =20 required.  Very odd setup though.  If you want a 'private' connec= tion=20 then use a switch, rather than needing umpty NICs in the PG=20 server.
-----Original Message-----
From:=20 pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org= ]=20 On Behalf Of Kent Anderson
Sent: 19 October 2004=20 17:05
To: Pgsql-Admin@Postgresql. Org
Subject: [ADMIN= ] NIC=20 to NIC connection

We are = upgrading=20 our servers and have run into an interesting situation.  It has been= =20 proposed that we have a direct connection from the web servers to=20 the postgres server via extra NICs. Has anyone done this before and = how=20 big a project would it be to alter ASP and Java applications to make use = of=20 such a connection?
 
Before = we even=20 waste time installing the NIC's I would like a sense of how hard it is to= get=20 postgres to use that kind of a connection vs over the Internet. We are lo= oking=20 to increase communication speed between the web servers and database= =20 server as much as possible.
 
Thanks
Kent= =20 Anderson
------=_NextPart_000_00D1_01C4B602.569A9E60-- From smarlowe@qwest.net Tue Oct 19 17:00:24 2004 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 B8B4932A0DD for ; Tue, 19 Oct 2004 18:00:24 +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 65200-03 for ; Tue, 19 Oct 2004 17:00:20 +0000 (GMT) Received: from mpls-qmqp-04.inet.qwest.net (mpls-qmqp-04.inet.qwest.net [63.231.195.115]) by svr1.postgresql.org (Postfix) with SMTP id 90805329EB7 for ; Tue, 19 Oct 2004 18:00:19 +0100 (BST) Received: (qmail 58887 invoked by uid 0); 19 Oct 2004 17:00:18 -0000 Received: from mpls-pop-08.inet.qwest.net (63.231.195.8) by mpls-qmqp-04.inet.qwest.net with QMQP; 19 Oct 2004 17:00:18 -0000 Received: from 63-227-127-37.dnvr.qwest.net (HELO ?10.0.0.2?) (63.227.127.37) by mpls-pop-08.inet.qwest.net with SMTP; 19 Oct 2004 17:00:18 -0000 Date: Tue, 19 Oct 2004 11:02:31 -0600 Message-Id: <1098205351.21035.33.camel@localhost.localdomain> From: "Scott Marlowe" To: "Kent Anderson" Cc: "Pgsql-Admin@Postgresql. Org" Subject: Re: NIC to NIC connection In-Reply-To: References: Content-Type: text/plain Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) 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/237 X-Sequence-Number: 15230 This is more a networking issue than a PostgreSQL one. What you'll like want to do is to set up a nic in each box and use a "rolled" cable directly between them. Assign an IP to each machine like 10.0.0.1 and 10.0.0.2 and edit your route tables to make each machine use those IPs respectively to talk to each other. I'm a unix guy, so explaining exactly how to do this in windows is a mystery to me. I'm guessing windows because of the ASP you mention. The basic theory stays the same though. On Tue, 2004-10-19 at 10:05, Kent Anderson wrote: > We are upgrading our servers and have run into an interesting > situation. It has been proposed that we have a direct connection from > the web servers to the postgres server via extra NICs. Has anyone done > this before and how big a project would it be to alter ASP and Java > applications to make use of such a connection? > > Before we even waste time installing the NIC's I would like a sense of > how hard it is to get postgres to use that kind of a connection vs > over the Internet. We are looking to increase communication speed > between the web servers and database server as much as possible. > > Thanks > Kent Anderson From Richard_D_Levine@raytheon.com Tue Oct 19 17:12:15 2004 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 5A0B8329EC2; Tue, 19 Oct 2004 18:12:15 +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 67319-10; Tue, 19 Oct 2004 17:12:05 +0000 (GMT) Received: from dfw-gate3.raytheon.com (dfw-gate3.raytheon.com [199.46.199.232]) by svr1.postgresql.org (Postfix) with ESMTP id B9AB1329E39; Tue, 19 Oct 2004 18:12:05 +0100 (BST) Received: from ds02c00.directory.ray.com (ds02c00.directory.ray.com [147.25.138.118]) by dfw-gate3.raytheon.com (8.12.10/8.12.10) with ESMTP id i9JHC03w004351; Tue, 19 Oct 2004 12:12:01 -0500 (CDT) Received: from ds02c00 (localhost [127.0.0.1]) by ds02c00.directory.ray.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id i9JHBqxx008287; Tue, 19 Oct 2004 17:11:52 GMT Received: from ds02c00.directory.ray.com with LMTP by ds02c00 (2.0.6/sieved-2-0-build-559); Tue, 19 Oct 2004 17:11:52 +0000 Received: from notesserver5.ftw.us.ray.com (notesserver5.ftw.us.ray.com [151.168.145.35]) by ds02c00.directory.ray.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id i9JHBPuE008084 sender Richard_D_Levine@raytheon.com; Tue, 19 Oct 2004 17:11:25 GMT Subject: Re: NIC to NIC connection To: Andrew Sullivan Cc: "Pgsql-Admin@Postgresql. Org" , pgsql-admin-owner@postgresql.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Richard_D_Levine@raytheon.com Date: Tue, 19 Oct 2004 12:11:20 -0500 X-MIMETrack: Serialize by Router on NotesServer5/HDC(Release 5.0.13a |April 8, 2004) at 10/19/2004 12:11:26 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-SPAM: 0.00 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.3 tagged_above=0.0 required=5.0 tests=NO_REAL_NAME X-Spam-Level: X-Archive-Number: 200410/238 X-Sequence-Number: 15231 Depends on the NIC. If your running 100MBS Ether and put in 1GBS Ether or fiber, it would make a difference. Rick Andrew Sullivan To: "Pgsql-Admin@Postgresql. Org" Sent by: cc: pgsql-admin-owner@pos Subject: Re: [ADMIN] NIC to NIC connection tgresql.org 10/19/2004 11:28 AM On Tue, Oct 19, 2004 at 12:05:05PM -0400, Kent Anderson wrote: > We are upgrading our servers and have run into an interesting situation. It > has been proposed that we have a direct connection from the web servers to > the postgres server via extra NICs. > Before we even waste time installing the NIC's I would like a sense of how > hard it is to get postgres to use that kind of a connection vs over the > Internet. I don't understand. What interface other than a NIC are you now using to go "over the Internet"? Or do you mean that you want an _extra_ IP address so that the web servers don't have to compete for the bandwidth? In that case, sure, you'll probably get a minor performance increase, depending on your current network traffic. A -- Andrew Sullivan | ajs@crankycanuck.ca In the future this spectacle of the middle classes shocking the avant- garde will probably become the textbook definition of Postmodernism. --Brad Holland ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html From jak@uiuc.edu Tue Oct 19 17:19:07 2004 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 716E932A0F7 for ; Tue, 19 Oct 2004 18:19:07 +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 71465-04 for ; Tue, 19 Oct 2004 17:19:05 +0000 (GMT) Received: from expredir3.cites.uiuc.edu (expredir3.cites.uiuc.edu [128.174.5.186]) by svr1.postgresql.org (Postfix) with ESMTP id 8C07532A02F for ; Tue, 19 Oct 2004 18:19:04 +0100 (BST) Received: from firefox.cites.uiuc.edu (firefox.ci.uiuc.edu [192.17.25.8]) by expredir3.cites.uiuc.edu (8.12.11/8.12.11) with ESMTP id i9JHJ03h020188; Tue, 19 Oct 2004 12:19:00 -0500 (CDT) Received: by firefox.cites.uiuc.edu (Postfix, from userid 79964) id 010532B5D77; Tue, 19 Oct 2004 12:18:57 -0500 (CDT) Date: Tue, 19 Oct 2004 12:18:57 -0500 From: "Jay A. Kreibich" To: Scott Marlowe Cc: Kent Anderson , "Pgsql-Admin@Postgresql. Org" Subject: Re: NIC to NIC connection Message-ID: <20041019171857.GB17857@uiuc.edu> Reply-To: jak@uiuc.edu References: <1098205351.21035.33.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1098205351.21035.33.camel@localhost.localdomain> User-Agent: Mutt/1.4.1i X-URL: http://www.uiuc.edu/~jak (includes PGP key) 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/239 X-Sequence-Number: 15232 On Tue, Oct 19, 2004 at 11:02:31AM -0600, Scott Marlowe scratched on the wall: > This is more a networking issue than a PostgreSQL one. What you'll like > want to do is to set up a nic in each box and use a "rolled" cable > directly between them Actually, you want a "cross-over" cable, not a "roll" cable. There is a difference. With many newer, high quality NICs, you don't even need that. Many modern NICs do auto MDI/MDI-X detection, so any standard cable will do. -j -- Jay A. Kreibich | Comm. Technologies, R&D jak@uiuc.edu | Campus IT & Edu. Svcs. | University of Illinois at U/C From ajs@crankycanuck.ca Tue Oct 19 17:58:27 2004 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 C367532AC91 for ; Tue, 19 Oct 2004 18:58:27 +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 86388-03 for ; Tue, 19 Oct 2004 17:58:25 +0000 (GMT) Received: from smtp100.rog.mail.re2.yahoo.com (smtp100.rog.mail.re2.yahoo.com [206.190.36.78]) by svr1.postgresql.org (Postfix) with SMTP id E0D3432AD8D for ; Tue, 19 Oct 2004 18:58:25 +0100 (BST) Received: from unknown (HELO phlogiston.dydns.org) (a.sullivan@rogers.com@65.49.125.184 with login) by smtp100.rog.mail.re2.yahoo.com with SMTP; 19 Oct 2004 17:58:24 -0000 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id 262734054; Tue, 19 Oct 2004 13:58:23 -0400 (EDT) Date: Tue, 19 Oct 2004 13:58:23 -0400 From: Andrew Sullivan To: "Pgsql-Admin@Postgresql. Org" , pgsql-admin-owner@postgresql.org Subject: Re: NIC to NIC connection Message-ID: <20041019175823.GL3359@phlogiston.dyndns.org> Mail-Followup-To: "Pgsql-Admin@Postgresql. Org" , pgsql-admin-owner@postgresql.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040722i 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/241 X-Sequence-Number: 15234 On Tue, Oct 19, 2004 at 12:11:20PM -0500, Richard_D_Levine@raytheon.com wrote: > > Depends on the NIC. If your running 100MBS Ether and put in 1GBS Ether or > fiber, it would make a difference. Not if you're not using 100 megs in the first place :) A -- Andrew Sullivan | ajs@crankycanuck.ca I remember when computers were frustrating because they *did* exactly what you told them to. That actually seems sort of quaint now. --J.D. Baldwin From bkim@coe.tamu.edu Tue Oct 19 18:51:14 2004 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 D4CFC329ED3 for ; Tue, 19 Oct 2004 19:51:14 +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 01504-10 for ; Tue, 19 Oct 2004 18:51:12 +0000 (GMT) Received: from edsun.coe.tamu.edu (edsun.coe.tamu.edu [165.91.232.6]) by svr1.postgresql.org (Postfix) with ESMTP id 013C332A084 for ; Tue, 19 Oct 2004 19:51:11 +0100 (BST) Received: (from root@localhost) by edsun.coe.tamu.edu (8.12.11/8.12.11) id i9JIp7vq006654 for pgsql-admin@postgresql.org; Tue, 19 Oct 2004 13:51:07 -0500 (CDT) Received: from edsun (edsun [165.91.232.6]) by edsun.coe.tamu.edu (8.12.11/8.12.11) with ESMTP id i9JIoeCk006565; Tue, 19 Oct 2004 13:50:40 -0500 (CDT) Date: Tue, 19 Oct 2004 13:50:40 -0500 (CDT) From: Ben Kim To: Kent Anderson Cc: "Pgsql-Admin@Postgresql. Org" Subject: Re: NIC to NIC connection In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS 0.3.12 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/242 X-Sequence-Number: 15235 My 2 pence. I think it's not a big task. If the servers are located nearby, all you need is. Connect the two machines: =========================== - get a crossover patch cable (Should be crossover - you can buy or make one by googling instructions.) - install one extra NIC on each machine and connect the two NICs using the crossover cable - give a private address to each NIC so that they share the same internal network, like 192.168.0.3 and 192.168.0.4. Change connection string: =========================== - change the database host in your ASP or JSP database connection file(s) to this internal address. (For example, jdbc:postgresql://db.some.com/mydb to jdbc:postgresql://192.168.0.4/mydb.) If you are using dreamweaver, etc., if you will need to change the connection setting there too. In my network a bulk transfer speed through the internal link is not much better than that of the external link. But the former is significantly better during a busy day. (But then, the database sessions are more likely to be interactive type of traffic...) You also get security as a side benefit. (Data can't be snooped.) Regards, Ben Kim Database Developer/Systems Administrator College of Education Texas A&M University On Tue, 19 Oct 2004, Kent Anderson wrote: > We are upgrading our servers and have run into an interesting situation. It > has been proposed that we have a direct connection from the web servers to > the postgres server via extra NICs. Has anyone done this before and how big > a project would it be to alter ASP and Java applications to make use of such > a connection? > > Before we even waste time installing the NIC's I would like a sense of how > hard it is to get postgres to use that kind of a connection vs over the > Internet. We are looking to increase communication speed between the web > servers and database server as much as possible. > > Thanks > Kent Anderson > From Richard_D_Levine@Raytheon.com Tue Oct 19 18:52:54 2004 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 DB80032A10D; Tue, 19 Oct 2004 19:52:54 +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 06323-01; Tue, 19 Oct 2004 18:52:44 +0000 (GMT) Received: from dfw-gate2.raytheon.com (dfw-gate2.raytheon.com [199.46.199.231]) by svr1.postgresql.org (Postfix) with ESMTP id B6C4D32A015; Tue, 19 Oct 2004 19:52:43 +0100 (BST) Received: from ds02c00.directory.ray.com (ds02c00.directory.ray.com [147.25.138.118]) by dfw-gate2.raytheon.com (8.12.10/8.12.10) with ESMTP id i9JIqe0S010361; Tue, 19 Oct 2004 13:52:40 -0500 (CDT) Received: from ds02c00 (localhost [127.0.0.1]) by ds02c00.directory.ray.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id i9JIqY5C013578; Tue, 19 Oct 2004 18:52:34 GMT Received: from ds02c00.directory.ray.com with LMTP by ds02c00 (2.0.6/sieved-2-0-build-559); Tue, 19 Oct 2004 18:52:33 +0000 Received: from notesserver5.ftw.us.ray.com (notesserver5.ftw.us.ray.com [151.168.145.35]) by ds02c00.directory.ray.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id i9JIpxRR013393 sender Richard_D_Levine@raytheon.com; Tue, 19 Oct 2004 18:52:02 GMT Subject: Re: NIC to NIC connection To: Andrew Sullivan Cc: "Pgsql-Admin@Postgresql. Org" , pgsql-admin-owner@postgresql.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Richard_D_Levine@Raytheon.com Date: Tue, 19 Oct 2004 13:51:58 -0500 X-MIMETrack: Serialize by Router on NotesServer5/HDC(Release 5.0.13a |April 8, 2004) at 10/19/2004 01:52:02 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-SPAM: 0.00 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.3 tagged_above=0.0 required=5.0 tests=NO_REAL_NAME X-Spam-Level: X-Archive-Number: 200410/243 X-Sequence-Number: 15236 True. I can't imagine a modern server room, even running windows, that doesn't have a gigabit or fiber backbone for the servers. Rick Andrew Sullivan To: "Pgsql-Admin@Postgresql. Org" , Sent by: pgsql-admin-owner@postgresql.org pgsql-admin-owner@pos cc: tgresql.org Subject: Re: [ADMIN] NIC to NIC connection 10/19/2004 12:58 PM On Tue, Oct 19, 2004 at 12:11:20PM -0500, Richard_D_Levine@raytheon.com wrote: > > Depends on the NIC. If your running 100MBS Ether and put in 1GBS Ether or > fiber, it would make a difference. Not if you're not using 100 megs in the first place :) A -- Andrew Sullivan | ajs@crankycanuck.ca I remember when computers were frustrating because they *did* exactly what you told them to. That actually seems sort of quaint now. --J.D. Baldwin ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend From bruno@wolff.to Tue Oct 19 21:51:08 2004 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 D076F329E4F for ; Tue, 19 Oct 2004 22:51:08 +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 12817-04 for ; Tue, 19 Oct 2004 21:50:56 +0000 (GMT) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id 3D67C329D27 for ; Tue, 19 Oct 2004 22:50:54 +0100 (BST) Received: (qmail 3474 invoked by uid 500); 19 Oct 2004 22:01:33 -0000 Date: Tue, 19 Oct 2004 17:01:33 -0500 From: Bruno Wolff III To: Matt Clark Cc: 'Kent Anderson' , "'Pgsql-Admin@Postgresql. Org'" Subject: Re: NIC to NIC connection Message-ID: <20041019220133.GA2957@wolff.to> Mail-Followup-To: Matt Clark , 'Kent Anderson' , "'Pgsql-Admin@Postgresql. Org'" References: <00d001c4b5f9$f4d63660$8300a8c0@solent> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00d001c4b5f9$f4d63660$8300a8c0@solent> User-Agent: Mutt/1.5.6i 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/249 X-Sequence-Number: 15242 On Tue, Oct 19, 2004 at 17:37:43 +0100, Matt Clark wrote: > You would assign a different subnet to the connection, and then tell the > servers to connect to the PG server's address on that subnet. No other > changes required. Very odd setup though. If you want a 'private' > connection then use a switch, rather than needing umpty NICs in the PG > server. Switches are not security devices. While it is harder to sniff packets on switches, you can't count on them to prevent hostile machines on the switch from playing games with the arp protocol. Also I believe that if a switch doesn't remember where a particular mac address is it will send the packet to all of the attached ports. From matt@ymogen.net Tue Oct 19 22:13:52 2004 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 E5AF9329F30 for ; Tue, 19 Oct 2004 23:13:52 +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 31286-10 for ; Tue, 19 Oct 2004 22:13:45 +0000 (GMT) Received: from bayswater1.ymogen.net (host-154-240-27-217.pobox.net.uk [217.27.240.154]) by svr1.postgresql.org (Postfix) with ESMTP id C9406329F4C for ; Tue, 19 Oct 2004 23:13:46 +0100 (BST) Received: from [82.68.132.233] (82-68-132-233.dsl.in-addr.zen.co.uk [82.68.132.233]) by bayswater1.ymogen.net (Postfix) with ESMTP id 04570A3D18; Tue, 19 Oct 2004 23:13:44 +0100 (BST) Message-ID: <41759198.4070505@ymogen.net> Date: Tue, 19 Oct 2004 23:13:44 +0100 From: Matt Clark User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruno Wolff III Cc: 'Kent Anderson' , "'Pgsql-Admin@Postgresql. Org'" Subject: Re: NIC to NIC connection References: <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> In-Reply-To: <20041019220133.GA2957@wolff.to> 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/250 X-Sequence-Number: 15243 >Switches are not security devices. While it is harder to sniff packets on >switches, you can't count on them to prevent hostile machines on the >switch from playing games with the arp protocol. Also I believe that if >a switch doesn't remember where a particular mac address is it will send >the packet to all of the attached ports. > > If you have 6 app servers it's just daft to stick 6 NICs in your DB server. If absolute privacy is a concern (not mentioned by the OP), then use a dedicated switch (or switches) for the 'private' subnet. Even better, use SSH. But all this is over the top for 99.9% of uses anyway. A VLAN is as private as anything else, so you can just create a VLAN on your current switch fabric and use that. No kind of traffic on a VLAN will hit any other VLAN. Unless of course someone has hacked your switch, set up a mirror port, attached a sniffer or other hacked machine to it, and is assiduously reading your traffic, in which case you have bigger problems.... M From bruno@wolff.to Tue Oct 19 22:23:13 2004 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 F1B2032A85F for ; Tue, 19 Oct 2004 23:23:13 +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 37884-05 for ; Tue, 19 Oct 2004 22:23:04 +0000 (GMT) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id B8D1D32A6DC for ; Tue, 19 Oct 2004 23:23:05 +0100 (BST) Received: (qmail 3994 invoked by uid 500); 19 Oct 2004 22:33:45 -0000 Date: Tue, 19 Oct 2004 17:33:45 -0500 From: Bruno Wolff III To: Matt Clark Cc: 'Kent Anderson' , "'Pgsql-Admin@Postgresql. Org'" Subject: Re: NIC to NIC connection Message-ID: <20041019223345.GA3753@wolff.to> Mail-Followup-To: Matt Clark , 'Kent Anderson' , "'Pgsql-Admin@Postgresql. Org'" References: <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> <41759198.4070505@ymogen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41759198.4070505@ymogen.net> User-Agent: Mutt/1.5.6i 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/251 X-Sequence-Number: 15244 On Tue, Oct 19, 2004 at 23:13:44 +0100, Matt Clark wrote: > > If you have 6 app servers it's just daft to stick 6 NICs in your DB > server. While there might be some cases where that makes sense most likely it isn't something you would want to do. I believe the original motivation was to solve bandwidth congestion rather than security. Most likely the systems were already connected to switches. If the nic to the web server(s) were really swamped (which seems unlikely, but could be the case), then adding a second nic and connecting to another port on the switch they are already using would probably work as well as running cables directly from the web server(s) to the database. They would need to adjust the routing tables so that some traffic went over each nic. An easy change would be to specify that traffic destined for the database server IP address is to go over the new nic and all other traffic is to go over the old nic. From spider@viovio.com Tue Oct 19 23:22:26 2004 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 C9D29329E73 for ; Wed, 20 Oct 2004 00:22:26 +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 60747-09 for ; Tue, 19 Oct 2004 23:22:22 +0000 (GMT) Received: from leda.steelsun.com (dsl093-240-204.ral1.dsl.speakeasy.net [66.93.240.204]) by svr1.postgresql.org (Postfix) with ESMTP id 20AB4329D9E for ; Wed, 20 Oct 2004 00:22:23 +0100 (BST) Received: from leda.steelsun.com (localhost [127.0.0.1]) by leda.steelsun.com (8.12.11/8.12.8) with ESMTP id i9JNMJkv022722; Tue, 19 Oct 2004 19:22:19 -0400 Received: from localhost (cfowler@localhost) by leda.steelsun.com (8.12.11/8.12.11/Submit) with ESMTP id i9JNMJX9022719; Tue, 19 Oct 2004 19:22:19 -0400 X-Authentication-Warning: leda.steelsun.com: cfowler owned process doing -bs Date: Tue, 19 Oct 2004 19:22:19 -0400 (EDT) From: Christian Fowler X-X-Sender: cfowler@leda.steelsun.com To: Kent Anderson Cc: "Pgsql-Admin@Postgresql. Org" Subject: Re: NIC to NIC connection In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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/252 X-Sequence-Number: 15245 There have been many comments about this already Kent. My $.02: The most common practice I am aware of is to install 2 NIC's in each appserver - one to your load balancer, and one to your private network (192.168.*) where your database server sites. In fact, ideally your database machine has no publically addressable nic at all. I have personally dealt with such a setup in several installs, some doing of millions of page views per *day*, and it has always been very reliable, secure, and fast. Use gigabit everywhere on your 192.168 "database" network. If you are concernced about bandwidth, wire up http://www.mrtg.org and look at the traffic for yourself. getting postgres to use this setup should be a piece of cake. Just make sure your settings in pg_hba.conf are setup right. Good luck. On Tue, 19 Oct 2004, Kent Anderson wrote: > We are upgrading our servers and have run into an interesting situation. It > has been proposed that we have a direct connection from the web servers to > the postgres server via extra NICs. Has anyone done this before and how big > a project would it be to alter ASP and Java applications to make use of such > a connection? > > Before we even waste time installing the NIC's I would like a sense of how > hard it is to get postgres to use that kind of a connection vs over the > Internet. We are looking to increase communication speed between the web > servers and database server as much as possible. > > Thanks > Kent Anderson > [ \ / [ >X< Christian Fowler | spider@viovio.com [ / \ http://www.viovio.com | http://www.tikipro.org From matt@ymogen.net Wed Oct 20 05:54:38 2004 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 B9C0A32A93D for ; Wed, 20 Oct 2004 06:54:38 +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 98038-05 for ; Wed, 20 Oct 2004 05:54:35 +0000 (GMT) Received: from bayswater1.ymogen.net (host-154-240-27-217.pobox.net.uk [217.27.240.154]) by svr1.postgresql.org (Postfix) with ESMTP id 07BFA32A8EB for ; Wed, 20 Oct 2004 06:54:34 +0100 (BST) Received: from [82.68.132.233] (82-68-132-233.dsl.in-addr.zen.co.uk [82.68.132.233]) by bayswater1.ymogen.net (Postfix) with ESMTP id 53CB7A3D2F; Wed, 20 Oct 2004 06:54:31 +0100 (BST) Message-ID: <4175FD97.4080500@ymogen.net> Date: Wed, 20 Oct 2004 06:54:31 +0100 From: Matt Clark User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruno Wolff III Cc: 'Kent Anderson' , "'Pgsql-Admin@Postgresql. Org'" Subject: Re: NIC to NIC connection References: <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> <41759198.4070505@ymogen.net> <20041019223345.GA3753@wolff.to> In-Reply-To: <20041019223345.GA3753@wolff.to> Content-Type: multipart/alternative; boundary="------------060109020209050809020806" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.0 tagged_above=0.0 required=5.0 tests=HTML_20_30, HTML_MESSAGE, HTML_TITLE_EMPTY X-Spam-Level: * X-Archive-Number: 200410/254 X-Sequence-Number: 15247 This is a multi-part message in MIME format. --------------060109020209050809020806 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit >>If you have 6 app servers it's just daft to stick 6 NICs in your DB >>server. >> >> > >While there might be some cases where that makes sense most likely it >isn't something you would want to do. I believe the original motivation >was to solve bandwidth congestion rather than security. > > > If the NICs are saturated then channel bonding is the answer. Any modern switch and OS will let you bind together multiple NICs so they appear as one. You can get an 4Gbps link this way. --------------060109020209050809020806 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit
If you have 6 app servers it's just daft to stick 6 NICs in your DB 
server.
    

While there might be some cases where that makes sense most likely it
isn't something you would want to do. I believe the original motivation
was to solve bandwidth congestion rather than security.

  
If the NICs are saturated then channel bonding is the answer.  Any modern switch and OS will let you bind together multiple NICs so they appear as one.  You can get an 4Gbps link this way.
--------------060109020209050809020806-- From mendola@bigfoot.com Thu Oct 21 08:20:44 2004 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 ED8CD32B30D for ; Thu, 21 Oct 2004 09:20:44 +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 21624-04 for ; Thu, 21 Oct 2004 08:20:41 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id A935C32B2E8 for ; Thu, 21 Oct 2004 09:20:41 +0100 (BST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i9L8KdJ7023897 for ; Thu, 21 Oct 2004 08:20:39 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i9L87bix020109 for pgsql-admin@postgresql.org; Thu, 21 Oct 2004 08:07:37 GMT From: Gaetano Mendola X-Newsgroups: comp.databases.postgresql.admin Subject: Re: NIC to NIC connection Date: Thu, 21 Oct 2004 10:07:33 +0200 Organization: PYRENET Midi-pyrenees Provider Lines: 18 Message-ID: <41776E45.2070109@bigfoot.com> References: <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@pyrenet.fr To: Bruno Wolff III User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en In-Reply-To: <20041019220133.GA2957@wolff.to> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime To: pgsql-admin@postgresql.org 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/274 X-Sequence-Number: 15267 Bruno Wolff III wrote: > Also I believe that if > a switch doesn't remember where a particular mac address is it will send > the packet to all of the attached ports. I don't think so, I guess the switch perform a sort of arpping in order to detect who have a macaddress assigned, even the multicast is not sent to all ports but only to that ports where "someone" sent an arp packet saying the he was registered to a multicast address. However I don't think exist a standard. Regards Gaetano Mendola From bruno@wolff.to Thu Oct 21 10:08:54 2004 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 48ABE32A124 for ; Thu, 21 Oct 2004 11:08:54 +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 51565-04 for ; Thu, 21 Oct 2004 10:08:42 +0000 (GMT) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id EEB8032A11A for ; Thu, 21 Oct 2004 11:08:42 +0100 (BST) Received: (qmail 31740 invoked by uid 500); 21 Oct 2004 10:19:23 -0000 Date: Thu, 21 Oct 2004 05:19:23 -0500 From: Bruno Wolff III To: Gaetano Mendola Cc: pgsql-admin@postgresql.org Subject: Re: NIC to NIC connection Message-ID: <20041021101923.GA31585@wolff.to> Mail-Followup-To: Gaetano Mendola , pgsql-admin@postgresql.org References: <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> <41776E45.2070109@bigfoot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41776E45.2070109@bigfoot.com> User-Agent: Mutt/1.5.6i 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/275 X-Sequence-Number: 15268 On Thu, Oct 21, 2004 at 10:07:33 +0200, Gaetano Mendola wrote: > Bruno Wolff III wrote: > >Also I believe that if > >a switch doesn't remember where a particular mac address is it will send > >the packet to all of the attached ports. > > I don't think so, I guess the switch perform a sort of arpping in order to > detect who have a macaddress assigned, even the multicast is not sent > to all ports but only to that ports where "someone" sent an arp packet > saying > the he was registered to a multicast address. Switches don't do arps; they are a layer 2 device (and hence don't know about IP addresses. They cache mac address port bindings. If their cache expires before the cached IP mac address bindings in some attached device then they can get requests to send to mac addresses for which they don't have a cached port. In that case they are supposed to do a port flood of the packet. I actually had a problem with a switch that was misconfigured and didn't do a port flood in these circumstances. That combined with a linux box that wasn't chatty enough to stay in the switch's cache and that the router cached IP address - mac address bindings for hours while the switch kept mac address - port bindings for minutes caused my machine to be unreachable to other hosts for periods of time. From jak@uiuc.edu Thu Oct 21 15:10:28 2004 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 D2F6E32AE63 for ; Thu, 21 Oct 2004 16:10:28 +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 52279-06 for ; Thu, 21 Oct 2004 15:10:23 +0000 (GMT) Received: from expredir4.cites.uiuc.edu (expredir4.cites.uiuc.edu [128.174.5.187]) by svr1.postgresql.org (Postfix) with ESMTP id F1C3E32ABF5 for ; Thu, 21 Oct 2004 16:10:21 +0100 (BST) Received: from firefox.cites.uiuc.edu (firefox.ci.uiuc.edu [192.17.25.8]) by expredir4.cites.uiuc.edu (8.12.11/8.12.11) with ESMTP id i9LFAGNU007339; Thu, 21 Oct 2004 10:10:16 -0500 (CDT) Received: by firefox.cites.uiuc.edu (Postfix, from userid 79964) id A47AC2B7354; Thu, 21 Oct 2004 10:10:15 -0500 (CDT) Date: Thu, 21 Oct 2004 10:10:15 -0500 From: "Jay A. Kreibich" To: Gaetano Mendola Cc: Bruno Wolff III , pgsql-admin@postgresql.org Subject: Re: NIC to NIC connection Message-ID: <20041021151015.GA21697@uiuc.edu> Reply-To: jak@uiuc.edu References: <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> <41776E45.2070109@bigfoot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41776E45.2070109@bigfoot.com> User-Agent: Mutt/1.4.1i X-URL: http://www.uiuc.edu/~jak (includes PGP key) 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/279 X-Sequence-Number: 15272 On Thu, Oct 21, 2004 at 10:07:33AM +0200, Gaetano Mendola scratched on the wall: > Bruno Wolff III wrote: > >Also I believe that if > >a switch doesn't remember where a particular mac address is it will send > >the packet to all of the attached ports. > > I don't think so, I guess the switch perform a sort of arpping in order to > detect who have a macaddress assigned, No, he's right. If the MAC to port mapping has not been learned by the switch, the packet is flooded to all ports or (for really bad switches) dropped. A switch is a pure layer-two device and ARP involves layer-three addresses and concepts. The only part of a switch that will ARP is the management system, assuming it has an IP address of its own. This is actually a standard test we run when evaluating switches for deployment on campus. We hook about ten devices up to a switch and send them tons of traffic. The systems count incoming packets but they do not generate any traffic, so the switch is forced to flood all the traffic. The vast majority of low-cost switches roll over and die at that point. > even the multicast is not sent > to all ports but only to that ports where "someone" sent an arp packet > saying the he was registered to a multicast address. Not ARP, IGMP (Internet Group Management Protocol). It's part of the IP suite, and is much higher up in the protocol stack. And again, this isn't true unless the switch does IGMP snooping or has multicast assist from the router. IGMP snooping is becoming more common on higher-end switches, but there are some companies that prefer the router assist design. The problem with that is that the switches and routers need to be from the same company. IGMP snooping is also really tricky to do right, and there are still some situations where you are forced to flood traffic. -j -- Jay A. Kreibich | Comm. Technologies, R&D jak@uiuc.edu | Campus IT & Edu. Svcs. | University of Illinois at U/C From gmendola@mbigroup.it Thu Oct 21 17:06:09 2004 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 21F8232AB8E for ; Thu, 21 Oct 2004 18:06:09 +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 90534-04 for ; Thu, 21 Oct 2004 17:06:05 +0000 (GMT) Received: from pns.mm.eutelsat.org (pns.mm.eutelsat.org [194.214.173.227]) by svr1.postgresql.org (Postfix) with ESMTP id 46A2132AE4B for ; Thu, 21 Oct 2004 18:05:55 +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 i9LH3k217624; Thu, 21 Oct 2004 19:03:47 +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 i9LH5of30333; Thu, 21 Oct 2004 19:05:50 +0200 Message-ID: <4177EC64.30009@mbigroup.it> Date: Thu, 21 Oct 2004 19:05:40 +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> In-Reply-To: <20041021151015.GA21697@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/294 X-Sequence-Number: 15287 Jay A. Kreibich wrote: > On Thu, Oct 21, 2004 at 10:07:33AM +0200, Gaetano Mendola scratched on the wall: > >>Bruno Wolff III wrote: >> >>>Also I believe that if >>>a switch doesn't remember where a particular mac address is it will send >>>the packet to all of the attached ports. >> >>I don't think so, I guess the switch perform a sort of arpping in order to >>detect who have a macaddress assigned, > > > No, he's right. If the MAC to port mapping has not been learned by > the switch, the packet is flooded to all ports or (for really bad > switches) dropped. A switch is a pure layer-two device and ARP > involves layer-three addresses and concepts. We have some switches that are able to do ip routing too... :-( I have to admint that I'm not a switch specialist but given the ability to do routing I was imagine the arpping trich... Regards Gaetano Mendola From jak@uiuc.edu Thu Oct 21 17:14:29 2004 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 D540032A095 for ; Thu, 21 Oct 2004 18:14:29 +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 92123-10 for ; Thu, 21 Oct 2004 17:14:20 +0000 (GMT) Received: from expredir4.cites.uiuc.edu (expredir4.cites.uiuc.edu [128.174.5.187]) by svr1.postgresql.org (Postfix) with ESMTP id 662D5329E7D for ; Thu, 21 Oct 2004 18:14:19 +0100 (BST) Received: from firefox.cites.uiuc.edu (firefox.ci.uiuc.edu [192.17.25.8]) by expredir4.cites.uiuc.edu (8.12.11/8.12.11) with ESMTP id i9LHEDtv026201; Thu, 21 Oct 2004 12:14:13 -0500 (CDT) Received: by firefox.cites.uiuc.edu (Postfix, from userid 79964) id DFB0E2B7977; Thu, 21 Oct 2004 12:14:12 -0500 (CDT) Date: Thu, 21 Oct 2004 12:14:12 -0500 From: "Jay A. Kreibich" To: Gaetano Mendola Cc: Gaetano Mendola , Bruno Wolff III , pgsql-admin@postgresql.org Subject: Re: NIC to NIC connection Message-ID: <20041021171412.GK21697@uiuc.edu> Reply-To: jak@uiuc.edu References: <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> <41776E45.2070109@bigfoot.com> <20041021151015.GA21697@uiuc.edu> <4177EC64.30009@mbigroup.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4177EC64.30009@mbigroup.it> User-Agent: Mutt/1.4.1i X-URL: http://www.uiuc.edu/~jak (includes PGP key) 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/281 X-Sequence-Number: 15274 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. Essentualy, they are just routers where the "routing" interfaces and the physical interfaces are abstracted from each other with a layer-two switching engine. The term "layer-three swtich" is really more of a marketing term, however, and is not a very accurate description of what the device is or how it works. > I have to admint that I'm not a switch specialist but given the ability > to do routing I was imagine the arpping trich... Yes, but such systems are generally routers first and switches second. -j -- Jay A. Kreibich | Comm. Technologies, R&D jak@uiuc.edu | Campus IT & Edu. Svcs. | University of Illinois at U/C From gmendola@mbigroup.it Thu Oct 21 17:43:01 2004 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