Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Sep 1999 20:25:05 -0400 (EDT)
From:      Michael9 <mfq@carolina.rr.com>
To:        freebsd-questions@freebsd.org
Subject:   dhclient (was: Network Interface Trouble.)
Message-ID:  <Pine.BSF.4.10.9909272020260.550-100000@gwazi.quigley.com>
In-Reply-To: <Pine.BSF.4.10.9909271415580.8077-100000@gwazi.quigley.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 27 Sep 1999, Michael9 wrote:

> The problem I'm having is that I cannot connect to anything on the ed1
> interface from within the box itself. I get the following error from the
> kernel on my console:
> 
> ---- console message ----
> 
> arplookup 127.0.0.1 failed: could not allocate llinfo
> arpresolve: can't allocate llinfo for 127.0.0.1rt
> 
> ----

I partially solved my own problem, so I'm posting this in the hopes that
it might help someone else.

The reason for the kernel messages was an incorrect route. The route was
added by the /sbin/dhclient-script script, which is invoked from dhclient.
Apparently dhclient-script tries to be smart and add a bunch of static
routes. 

> 24.93.84.28        127.0.0.1          UGHS        0        3      ed1

The above line from 'netstat -nr' was the incorrect route. I removed this
route and everything started functioning normally.

I've read over the dhclient manpages and haven't really found any way to
control what static routes are added by the dhclient-script. In the
interim (until I can find a better solution), I've gone ahead and modified
my copy of dhclient-script to stop it from adding the extra static routes.

Does anyone know what version of dhclient is bundled with 3.3-RELEASE? Is
it the current 2.0 version? 

Any advice would be appreciated..

Michael





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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9909272020260.550-100000>