From owner-freebsd-chat Sat May 18 16:51:53 2002 Delivered-To: freebsd-chat@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 305D437B40B for ; Sat, 18 May 2002 16:51:48 -0700 (PDT) Received: from pool0271.cvx22-bradley.dialup.earthlink.net ([209.179.199.16] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #2) id 179Dz9-0003F6-00; Sat, 18 May 2002 16:51:40 -0700 Message-ID: <3CE6E8ED.84E431F@mindspring.com> Date: Sat, 18 May 2002 16:51:09 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Meyer Cc: Brad Knowles , Giorgos Keramidas , Miguel Mendez , freebsd-chat@FreeBSD.ORG Subject: Re: The road ahead? References: <20020516004909.A9808@daemon.tisys.org> <20020516151801.A47974@energyhq.homeip.net> <20020516172853.A7750@daemon.tisys.org> <3CE40759.7C584101@mindspring.com> <20020516220616.A51305@energyhq.homeip.net> <3CE43D08.1FDBF0A3@mindspring.com> <20020517163624.GB9697@hades.hell.gr> <3CE58F73.1A7F50AF@mindspring.com> <15589.63655.94078.482179@guru.mired.org> <3CE61284.80ADD241@mindspring.com> <15590.58578.811389.223502@guru.mired.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Mike Meyer wrote: > > You just turn it on? > > With a button? > > 8-) 8-). > > Nope - with a power cord. Can't do a graceful shutdown without a button. I actually would be uncomfortable with something that didn't have an activation sequence of some kind that didn't include something that you normally don't do (plugging/unplugging is supposed to be limited to installation and deinstallation, not activation and deactivation). > > The idea that there is a requirement for static addresses for servers > > is a common misconception. So is the idea that your gateway has to > > be at a specific location, etc.. > > Good point. If you control the DNS, the requirement for many such > static IP addresses go away. The linksys doesn't do it's own DNS, > though. > > I guess if all your external serves are on the magic box, you don't > need to deal with nat, either. Actually, you don't have to do the DNS thing, if you can do the DNSUPDAT thing. So: o Find the gateway o Find your IP o Find the name server from the root o Reverse lookup your IP to get the domain name o Use the DNS information based on your role to configure yourself Role selection can be more difficult, but really, SLP can be used to find a "manage me" server. > > > But those options are for geeks. For a small all-MS shop that > > > outsources it's servers, it's a near-perfect solution - unless you > > > want to run netmeeting including someone not on the LAN. I'm waiting > > > for them to announce a firmware upgrade running an OH323 gatekeeper, > > > but expect it to be a new product. > > > > That's actually a protocol design bug. Protocols that require > > application layer proxies have an intrinsically broken design > > (e.g. RealPlayer). These broken designs are usually intentional, > > in order to control the market. > > I don't think that's the case here. There's already an open source > gatekeeper package for OH323. I'm a big fan of ZEROCONF. 8-). > The reason I didn't write the first time was because I realized that > Linksys has done just what Terry was saying FreeBSD has failed to do: > They've identified a target market, and produced a box that that > market can use as a true plug-n-play device. They've provided enough > configuration that geeks in that market segment will probably be > happy, but you don't *have* to do any configuration in the target > market. I think the market is changing on them because of NetMetting > and clones. The question is whether they will adapt to the changing > conditions. Yeah. This is what's called a "whole product". 8-). It means more than just the object itself... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message