From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1J0aSl-0002Qx-FY for garchives@archives.gentoo.org; Fri, 07 Dec 2007 10:29:43 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.2/8.14.0) with SMTP id lB7ASSbH022163; Fri, 7 Dec 2007 10:28:28 GMT Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by robin.gentoo.org (8.14.2/8.14.0) with ESMTP id lB7AOGRQ017310 for ; Fri, 7 Dec 2007 10:24:17 GMT Received: by ug-out-1314.google.com with SMTP id j3so846558ugf for ; Fri, 07 Dec 2007 02:24:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; bh=myQy795t4PYI+YBC8ibUe7lpi3N6MR+O0hpeF1R/9Bw=; b=hB4eJ2SPK0pkccvbt9pn5FV+M2/ntT1s0us1iesgkeUy9psbP4+OFwRWP4tjv12i1IItzTp3q86UyyyfnM9ZLupagvpxBzvpy7I5uiOB2jBUXjKxR+ZYwjHLbgMgWjDUNbJeojiVDxDHqCFbcRj7Q1u8n5iFNOpTQta7Bjn576Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; b=YfBEgTgh16UfkKzdlLVB01Ms3MfrpBjW75w+gH9cePLarUP71jBh2lPmlFE7/Q/Z3yt9bsskIfa5bdzcHhLGfYME1UVz5O0u/QfJWL8t9bfKjGZW+SGuZljwWYrsSafvW15+drooy+mdjEjSogl+o/46sN/UC9a1A5w/Ns7FGhU= Received: by 10.66.221.18 with SMTP id t18mr2307001ugg.1197023056508; Fri, 07 Dec 2007 02:24:16 -0800 (PST) Received: from lappy ( [81.154.142.239]) by mx.google.com with ESMTPS id j1sm847054ugf.2007.12.07.02.24.15 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 07 Dec 2007 02:24:15 -0800 (PST) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Be careful when using dhcp with a LiveCD Date: Fri, 7 Dec 2007 08:59:16 +0000 User-Agent: KMail/1.9.7 References: <49bf44f10712061504k3797c442l98cf42b705cd7f9a@mail.gmail.com> <200712062319.22158.michaelkintzios@gmail.com> <4758A027.2030403@gmail.com> In-Reply-To: <4758A027.2030403@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart6113665.x61j29km49"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200712070859.29195.michaelkintzios@gmail.com> X-Archives-Salt: bbb3293e-9c4c-4ad6-90b9-93ed624c8f60 X-Archives-Hash: 2a0a116c63c87228f5600a76ecfc70c2 --nextPart6113665.x61j29km49 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 07 December 2007, b.n. wrote: > Mick ha scritto: > >> The point is: be careful when using dhcp from a LiveCD. Your system > >> might act differently the next time you boot the hard drive. > > > > The dhcpcd was changed recently and not all dhcp servers take kindly to > > it, when it uses DUID the way it does (some servers depend on DUID > > passing on to them the MAC of the client). The solution I also found w= as > > to set the vram flag. > > I'm really ignorant on networks. What has changed on the dhcp side so > that *client* behaviour alters *server* behaviour? Isn't this horribly > broken (from the server side), or there is some reason to behave that? I am no less ignorant I'm afraid, but this is how I understand it in simple= =20 terms: net-misc/dhcpcd-3.1.5-r1 has introduced a usage of DUID which is compliant= =20 with RFC 4361, and creates a client ID (this can be any string uniquely=20 identifying the client interface). However, a number of DHCP server=20 implementations expect the DUID to contain the MAC of the client and unless= =20 this is in a particular format the server falls over. The vrm flag allows the MAC to be used in the DUID field and then the serve= r=20 is happy to issue an IP address to the client. As an alternative one can t= ry=20 the dhcpcd -I option to specify the MAC of the client, but when I tried it = I=20 couldn't get it to work. I guess eventually all dhcp implementations will catch up with this change,= =20 although for now it is bound to create some problems with particular DHCP=20 servers (cisco being one of them). On the other hand RFC 4361 may be=20 superseded/reversed, dhcpcd will go back to how it was and the world will b= e=20 a simpler place to live and network. :) HTH. =2D-=20 Regards, Mick --nextPart6113665.x61j29km49 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQBHWQtn5Fp0QerLYPcRApAlAKCTG3sWhKzYt2/PqUXTCPoJaRc29gCgiSVY x27kknanLrUbsvF2vDjB1S4= =cHhK -----END PGP SIGNATURE----- --nextPart6113665.x61j29km49-- -- gentoo-user@gentoo.org mailing list