Date: Tue, 22 Nov 2005 17:11:23 -0600 From: Greg Barniskis <nalists@scls.lib.wi.us> To: Mark Andrews <Mark_Andrews@isc.org> Cc: freebsd-stable@freebsd.org, Sebastiaan van Erk <sebster@sebster.com> Subject: Re: DHCP client error: domain_not_set.invalid Message-ID: <4383A59B.1090709@scls.lib.wi.us> In-Reply-To: <200511222248.jAMMmmxk043638@drugs.dv.isc.org> References: <200511222248.jAMMmmxk043638@drugs.dv.isc.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Andrews wrote: > Yes it is reasonable to expect ISP to fix things like this. > You pay the ISP to operate there part of the network within > the operational contraints of the RFCs (Standards track and > BCP). I totally agree. Make sure when calling tech support on things like this that you are *not* asking them to provide FreeBSD support, that you can handle that angle of the connection quite well, thanks. Explain that the evidence shows that their system appears to violate global connectivity standards (if you can name which RFC and exactly how it's violated, great, but don't expect first tier help desk phone operators to understand that as it is probably way, way beyond their troubleshooting script). Then when the help desk staff goes "uhm...", politely ask to be escalated to second tier and clearly and politely state your case there, again making it clear that you are *not* asking for FreeBSD support, but support by them of global connectivity standards that every ISP ought to be respecting. At least you have a chance of getting your trouble ticket marked something like "Unresolved -- Bug" instead of "Resolved -- Unsupported OS". That is to say, the kind of ticket that self-escalates to engineers and managers somewhere away from the help desk proper. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) <gregb at scls.lib.wi.us>, (608) 266-6348
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4383A59B.1090709>