bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debian Gnu/Hurd - Configure Network


From: Thomas Schwinge
Subject: Re: Debian Gnu/Hurd - Configure Network
Date: Fri, 13 Jul 2012 12:35:35 +0200
User-agent: Notmuch/0.9-101-g81dad07 (http://notmuchmail.org) Emacs/23.3.1 (i486-pc-linux-gnu)

Hi!

On Fri, 13 Jul 2012 12:18:44 +0200, I wrote:
> On Fri, 1 Jun 2012 18:36:07 +0200, Samuel Thibault <address@hidden> wrote:
> > zac storer, le Thu 31 May 2012 16:46:55 -0600, a écrit :
> > > I am also following the debian hurd mailing list, namely: http://
> > > lists.debian.org/debian-hurd/2012/05/msg00043.html .
> > > I have updated the hurd, gnumach, netdde, and isc-dhcp-client packages.
> > > Everything seems to be fine.
> > > I then issue a dhclient -v /dev/eth0, and get the following error:
> > > 
> > > ../../../../lib/isc/unix/socket.c:5636: setsockopt(21, IPV6_V6ONLY) 
> > > failed: (?)
> > > (?)
> > > ... Copyright info here ...
> > > 
> > > fsysopts: /servers/socket/2: -i /dev/eth0: (ipc/mig) server died
> > > Error getting hardware address for "/dev/eth0": No such device
> 
> I'm seeing the same.  (The second (?) being a heart symbol, how cute.)
> 
> > Which probably means the DDE driver just didn't find your device.  Or
> > perhaps simply lacks the firmware.
> 
> Nope, if I manually configure with fsysopts, it does work fine (3c905B
> NIC).

In fact, »dhclient -v /dev/eth0« also seems to work fine (but the
setsockopt error remains; not fatal apparently).

To resolve this, apply the following patch:

--- /etc/network/interfaces~    2011-05-20 19:46:45.000000000 +0200
+++ /etc/network/interfaces     2012-07-13 12:34:40.000000000 +0200
@@ -6,5 +6,5 @@
 iface lo inet loopback
 
 # The primary network interface
-auto eth0
-iface eth0 inet dhcp
+auto /dev/eth0
+iface /dev/eth0 inet dhcp

Remaining (likewise non-fatal, as it seems) issue: »can't create
/var/lib/dhcp/dhclient./dev/eth0.leases: No such file or directoy«, which
is only seen during boot, but not when running dhclient manually.
Obviously using /dev/eth0 instead of eth0 is the culprit here.


Grüße,
 Thomas

Attachment: pgp06IinC3xmn.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]