From owner-freebsd-stable@FreeBSD.ORG Tue Nov 22 14:20:18 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B8C216A41F for ; Tue, 22 Nov 2005 14:20:18 +0000 (GMT) (envelope-from sebster@sebster.com) Received: from smtp.profdata.nl (server.profdata.nl [213.196.2.244]) by mx1.FreeBSD.org (Postfix) with SMTP id C9E2443D68 for ; Tue, 22 Nov 2005 14:20:16 +0000 (GMT) (envelope-from sebster@sebster.com) Received: (qmail 22171 invoked from network); 22 Nov 2005 14:20:15 -0000 Received: from unknown (HELO ?10.0.0.6?) (80.126.244.3) by server.profdata.nl with SMTP; 22 Nov 2005 14:20:14 -0000 Message-ID: <4383291D.9020109@sebster.com> Date: Tue, 22 Nov 2005 15:20:13 +0100 From: Sebastiaan van Erk User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051119) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Andrews , freebsd-stable@freebsd.org References: <200511221233.jAMCX7f6092194@drugs.dv.isc.org> In-Reply-To: <200511221233.jAMCX7f6092194@drugs.dv.isc.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: DHCP client error: domain_not_set.invalid X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2005 14:20:18 -0000 Hi, >>I understand the idea that bad values should be rejected, but in >>reality, I have the same DSL modem that these others have and there is >>no way to change the domain search list that it sends. No way that I >>could find at least. This is SBC-Yahoo in California, so there are a lot >>of people out there with this modem. > > > Well ring your ISP and complain. Too many people just > accept crappy service. This is just the attitude that's going to get people to use other software. People are going to laugh at you trying to get a network connection and joke "it works fine with Windows". Then you try and explain that it's not your OS's fault and somebody messed up some setting somewhere else. And then they laugh some more watching you struggle. Furthermore it's really not realistic to expect that ISP's are going to do anything about it either. They have a billion other more important issues other than solving that insignificant problem that "that guy who is using an unsupported OS" has. They really don't care. >>dhcpd should either >> >>1. accept bogus names (warnings are fine) >>2. offer a configuration option or command line switch to allow the >>bogus domain if we wish >>3. offer a configuration option like isc-dhcpd does so that we can >>ignore or override the setting I would have to agree here. I think option 2 is great, because it gets people to be aware of the problem, but it allows them to workaround it if necessary. I really think it's terrible to have the software just reject a lease because of an invalid search domain, without you being able to fix it without hacking code. That's going a bit overboard IMHO and is just going to cause more problems than it's going to solve. Greetings, Sebastiaan