Re: network/name resolution problems
<snip>
> Should be fine. (Debian kernel, or custom-built? Which Debian
custom-built
<snip>
> (And if you've built your own kernel, there are a couple of kernel
> options that need to be enabled, namely the CONFIG_PACKET and
> CONFIG_FILTER ("Packet socket" and "socket filtering") options; check
Thanks David. I recompiled the kernel with those two selected and it not
only resulted in a functioning network connection but also agreed to do
the alien --to-deb job that I mentioned in a different post.
Dan
> /usr/share/doc/dhcp3-client/README.gz. But those options should be
> enabled if you're using a prebuilt kernel on unstable or testing.)
>
> > and by the way
> >> ifdown eth0
> > cat: /var/run/dhclient.pid: No such file or directory
> > Does that matter?
>
> Suggests that the DHCP client either didn't start or started and died,
> rather than started successfully but failed to get an IP address.
>
> --
> David Maze dmaze@debian.org http://people.debian.org/~dmaze/
> "Theoretical politics is interesting. Politicking should be illegal."
> -- Abra Mitchell
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Reply to: