From owner-freebsd-bugs  Tue Nov 30  2:40: 3 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id F03B21586A
	for <freebsd-bugs@FreeBSD.org>; Tue, 30 Nov 1999 02:40:00 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id CAA17628;
	Tue, 30 Nov 1999 02:40:00 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 1E9041514C; Tue, 30 Nov 1999 02:30:55 -0800 (PST)
Message-Id: <19991130103055.1E9041514C@hub.freebsd.org>
Date: Tue, 30 Nov 1999 02:30:55 -0800 (PST)
From: skyhawk@NOSPAM.tempest.yi.org
To: freebsd-gnats-submit@freebsd.org
X-Send-Pr-Version: www-1.0
Subject: misc/15183: DHCP Client problems -- /sbin/dhclient-conf
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         15183
>Category:       misc
>Synopsis:       DHCP Client problems -- /sbin/dhclient-conf
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Nov 30 02:40:00 PST 1999
>Closed-Date:
>Last-Modified:
>Originator:     Andrew Fremantle
>Release:        FreeBSD 3.3-Release to -Stable around Nov.25
>Organization:
>Environment:
FreeBSD chronos.tempest.yi.org 3.3-STABLE FreeBSD 3.3-STABLE #0: Tue Nov 30 00:30:56 PST 1999     skyhawk@chronos.tempest.yi.org:/usr/src/sys/compile/CHRONOS  i386
>Description:
/sbin/dhclient-script bugs that have been there about forever as far as I can tell.

I first had this problem on 3.2-RELEASE, then later on 3.3-RELEASE with this new system, and it still lingers on with 3.3-STABLE. It should be noted that I was not really a FreeBSD user prior to this point. This problem occurs with both a generic isa NE/2000 card and an isa 3c509b.

This has only occured on single-NIC systems. I've never tested with a multi-homed box.

As far as I can tell, the problem is that arp to the external interfaces is hosed. For example, if my machine has 192.168.1.20 as an IP bound to ed0, and I try to ping 192.168.1.20, I get no ping replies and this generated in syslog :

Nov 30 01:42:00 chronos /kernel: arplookup 127.0.0.1 failed: could not allocate llinfo
Nov 30 01:42:00 chronos /kernel: arpresolve: can't allocate llinfo for 127.0.0.1rt

over and over and over again, until I stop trying to ping.

>How-To-Repeat:
As far as I can tell, have a DHCP server on your network, have the following sections in /etc/rc.conf

network_interfaces="ep0 lo0"
#ifconfig_ed0="DHCP"
ifconfig_ep0="DHCP"

As appropriate for your network card, of course.

Try to ping your interface and, unless i'm being an idiot and doing something really wrong, watch /var/log/messages grow! :)


>Fix:
I'm not even going to pretend to understand all the issues, but i've gone through and commented several lines in /sbin/dhclient-script, which seems to correct the problem, *for me*, and in my *one card* setup.

For convenience, I will make the full dhclient-script file downloadable shortly from ftp://ftp.tempest.yi.org/pub/dhclient-script.modified



>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message