From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 14:38:27 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3324A1065670 for ; Wed, 7 Jan 2009 14:38:27 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from arcturus.maxiscale.com (arcturus.maxiscale.com [76.231.178.136]) by mx1.freebsd.org (Postfix) with ESMTP id 09C218FC16 for ; Wed, 7 Jan 2009 14:38:24 +0000 (UTC) (envelope-from psteele@maxiscale.com) X-ASG-Debug-ID: 1231339087-49c500000000-QdxwpM X-Barracuda-URL: http://10.100.1.25:8000/cgi-bin/mark.cgi Received: from polaris.maxiscale.com (localhost [127.0.0.1]) by arcturus.maxiscale.com (Spam Firewall) with ESMTP id 39C47360AB for ; Wed, 7 Jan 2009 06:38:07 -0800 (PST) Received: from polaris.maxiscale.com (polaris.maxiscale.com [10.100.1.24]) by arcturus.maxiscale.com with ESMTP id 2JjDLHQpdql6L565 for ; Wed, 07 Jan 2009 06:38:07 -0800 (PST) X-ASG-Whitelist: Client X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 X-ASG-Orig-Subj: RE: Having problems with limited broadcast Date: Wed, 7 Jan 2009 06:38:05 -0800 Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> In-Reply-To: <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Having problems with limited broadcast Thread-Index: Aclwo7FvMTQm45SXQwiffk2PQhMrnQALokpA References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> From: "Peter Steele" To: X-Barracuda-Connect: polaris.maxiscale.com[10.100.1.24] X-Barracuda-Start-Time: 1231339093 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at maxiscale.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RE: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2009 14:38:27 -0000 >We ARE talking about "just a LAN" here, right? Also, these computers >are "not on the internet?" They have absolutely no connectivity? >(Unlikely). When our boxes are initially deployed, they have no IP addresses assigned to them. Their ifconfig entry looks like this: ifconfig_lagg0=3D"laggproto failover laggport nfe0 laggport nfe1" With this config, no IP is assigned to the lagg0 device, so the only way to access the boxes is via a serial console. From there we give one system a static IP, and then proceed to configure our "light DHCP" service on this box via a web app. After this is done, the remaining systems start communicating with this box via a broadcast protocol to obtain their IPs. These will be assigned statically to these boxes, and from there they can get on with launching their applications (JBOSS, etc). And I'll leave it at that. I am quite ready to give this one to Kayven Riese. He clearly knows a lot more about the subject than I do, and I apologize for the testiness of my posting (deadline pressures). We are proceeding with using raw sockets to implement our broadcast based light DHCP service. =20