Hi all,
Michael Tross wrote:
Am Samstag, den 22.11.2008, 10:04 -0800 schrieb William Tracy:
On Sat, Nov 22, 2008 at 2:16 AM, Adam Stirk <[EMAIL PROTECTED]> wrote:
You can try 'modprobe ipv6' then 'dhclient eth0'.
I tried that, and that time it complained that it couldn't find
'/sbin/dhclient-script'; so I copied /etc/dhclient-script into /sbin,
and got the following output:
Internet Systems Consortium DHCP Client 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
/sbin/dhclient-script: line 230: [: =: unary operator expected
/sbin/dhclient-script: line 240: [: =: unary operator expected
/sbin/dhclient-script: line 254: [: =: unary operator expected
/sbin/dhclient-script: line 254: [: =: unary operator expected
/sbin/dhclient-script: line 266: [: =: unary operator expected
/sbin/dhclient-script: line 279: [: too many arguments
No broadcast interfaces found - exiting.
BTW, I said before that this was a 7.0 install. I confused
myself--this is actually a build from Trunk earlier this week. I
remember now that the 7.0 rc 2 wasn't wanting to talk to my flash
drive for whatever reason.
On trunk there are known problems with the dhcp package since the 4.0.x
update, this was discussed earlier this year:
http://www.nabble.com/forum/ViewPost.jtp?post=18650084&framed=y
You have to setup dhcp client on a target system:
- edit and create a valid /etc/dhclient.conf with at least the single
line:
script "/etc/dhclient-script";
- you may have to preload the IPv6 module in /etc/conf/kernel, depending
on your kernel configuration:
modprobe ipv6
Somehow the ipv6 module is not automatically loaded, even with
alias net-pf-10 ipv6
in /etc/modprobe.conf
I like to stress that if this is still lthe case in trunk:HEAD that it's
a bug - not
a feature.
DHCP must work with just the dhcp keyword in Netconf (formerly known
as ROCK Net :-) without poking kernel modules or creating another
config file such as /etc/dhcpd.conf<whatever> manually.
Guess I should give it a try soonish.
Actually I personally find it quite sad how much regressions ^W random
changes the DHCP 4.0 package had and how much of our time it
already wasted :-(
Btw. We have several alternative, saner and tinier DHCP clients in T2,
on which I'll probably going to explore more in projects:
dhcpclient
It's a modern client which also monitors the NIC for link changes and
thus intelligently and instantly issues a DHCP request when the
cable is plugged in (and not like the classic ISC one 20 minutes later,
etc.).
Yours,
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of: unsubscribe t2
