Re: How have I misconfigured DHCP?
On Monday 13 January 2003 07:21 am, Andrew Perrin wrote:
> I'm moving to a DHCP arrangement for my home network. I've set up the DHCP
> server, and it responds appropriately to requests from two of the three
> other computers on the network (one debian, one WinXP). From the other
> debian computer on the network, it responds if I manually do:
>
> pump -i eth0
>
> but on startup it doesn't obtain an address. Therfore, of course,
> services depending on the address (openAFS, NFS mounts) don't start
> either.
>
> Here's /etc/network/interfaces:
> ---
> # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
>
> # The loopback interface
> auto lo
> iface lo inet loopback
>
> # The first network card - this entry was created during the Debian
> installation
> # (network, broadcast and gateway are optional)
> auto eth0
> iface eth0 inet dhcp
> ---
>
> and here's some more diagnostic information:
>
> joehill:/var/log# /etc/init.d/openafs-client start
> ping: unknown host isis.unc.edu
> joehill:/var/log# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:20:ED:46:5A:E4
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:152 (152.0 b) TX bytes:0 (0.0 b)
> Interrupt:11
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:24 errors:0 dropped:0 overruns:0 frame:0
> TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1648 (1.6 KiB) TX bytes:1648 (1.6 KiB)
>
> joehill:/var/log# pump -i eth0
> joehill:/var/log# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:20:ED:46:5A:E4
> inet addr:192.168.0.14 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:5 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:1181 (1.1 KiB) TX bytes:1522 (1.4 KiB)
> Interrupt:11
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:24 errors:0 dropped:0 overruns:0 frame:0
> TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1648 (1.6 KiB) TX bytes:1648 (1.6 KiB)
>
> joehill:/var/log# /etc/init.d/openafs-client start
> PING isis.unc.edu (152.2.1.99): 56 data bytes
> 64 bytes from 152.2.1.99: icmp_seq=0 ttl=240 time=24.4 ms
> 64 bytes from 152.2.1.99: icmp_seq=1 ttl=240 time=23.5 ms
>
> --- isis.unc.edu ping statistics ---
> 2 packets transmitted, 2 packets received, 0% packet loss
> round-trip min/avg/max = 23.5/23.9/24.4 ms
> Starting AFS services: afsd: All AFS daemons started.
> afsd.
>
>
> ----------------------------------------------------------------------
> Andrew J Perrin - http://www.unc.edu/~aperrin
> Assistant Professor of Sociology, U of North Carolina, Chapel Hill
> clists@perrin.socsci.unc.edu * andrew_perrin (at) unc.edu
You can have this behavior if you do not have the following options enable in
your kernel config file. Pump will work dhclient does not.
# Networking options
#
CONFIG_PACKET=m
snip
CONFIG_FILTER=y
--
Greg Madden
Reply to: