From: Rumen Yotov <rumen@qrypto.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Upgrade of dhcpcd
Date: Mon, 31 Mar 2008 15:55:43 +0300 [thread overview]
Message-ID: <20080331125543.GA7780@qrypto.org> (raw)
In-Reply-To: <47F0AB70.5020605@alice.it>
[-- Attachment #1: Type: text/plain, Size: 2111 bytes --]
On (31/03/08 11:14) econti wrote:
> Rumen Yotov ha scritto:
>> econti МапОÑ?а:
>>> Hi all, yesterday I upgraded dhcpcd, now at boot time I receive this
>>> message:
>>>
>>> err, eth0: Failed to lookup hostname via DNS: Name or service not known
>>>
>>> Even so, the IP is correctly assigned by the router.
>>>
>>> Could anyone help me to understand? ;-)
>>>
>>> Bye
>>> emilio
>>>
>>>
>> Hi,
>>
>> Look at the new USE-flags, there are two IIRC - zeroconf vram
>> Specially vram in this case.
>> HTH. Rumen
>>
> I tried USE="-zeroconf": no result
> then USE="vram": no result
> then USE="-zeroconf vram": no result
>
> So I dowgraded dhcpcd to the previous version (2.0.5-r1): no more error
> message. ;-(
>
> I'd like to understand.
>
> Bye
> emilio
>
> --
> gentoo-user@lists.gentoo.org mailing list
>
Hi,
Try switching Off both '-zeroconf -vram'.
From the dhcpcd-3.2.3 elog:
elog> * ZeroConf support enabled
elog> * DUID support enabled
elog> * You have installed dhcpcd with zeroconf support.
elog> * This means that it will always obtain an IP address even if no
elog> * DHCP server can be contacted, which will break any existing
elog> * failover support you may have configured in your net
configuration.
elog> * This behaviour can be controlled with the -L flag.
elog> * See the dhcpcd man page for more details.
elog> * You have installed dhcpcd with DUID support.
elog> * This means that we will generate a DUID in
/var/lib/dhcpcd/dhcpcd.duid
elog> * This is generated from a MAC address of the card and a
timestamp.
elog> * It will be used in every subsequent DHCP transaction, along
with a IAID
elog> * in the ClientID option. This is required by RFC 4361.
elog> * Some DHCP server implementations require a MAC address only in
the
elog> * ClientID field. These DHCP servers should be updated to be RFC
elog> * conformant. If you cannot do this, you can revert to the old
elog> * behaviour by using the -I '' option OR building dhcpcd with the
elog> * vram USE flag enabled.
...end...
HTH. Rumen
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-03-31 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-30 13:48 [gentoo-user] Upgrade of dhcpcd econti
2008-03-30 13:16 ` Rumen Yotov
2008-03-31 9:14 ` econti
2008-03-31 12:55 ` Rumen Yotov [this message]
2008-04-05 13:28 ` econti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080331125543.GA7780@qrypto.org \
--to=rumen@qrypto.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox