[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dhcp-client uselessness on powerpc



On Mon, Jul 09, 2001 at 04:24:17AM -0800, Ethan Benson wrote:
> On Mon, Jul 09, 2001 at 06:55:01AM -0500, Stephen R Marenka wrote:
> > 
> > Maybe that's the difference, mine's a dhcp server. I don't suppose
> > you're in a position to test that? Are you using the bootp package?
> > Maybe I can scrounge a test system together.
> 
> eb@plato eb$ dlocate -s bootp | grep ^Ver
> Version: 2.4.3-3
> 
> you can see my bootptab if you want, pump, OpenFirmware and MacOS all
> work fine with it so i am not inclined to believe its misconfigured.  
> 
> i have no interest in setting up a dhcp server.  

I didn't mean to imply it was your bootp problem, but rather the problem
with dhcp-client may be specific to your setup. I was considering what
it would take to try to reproduce this.

> > Actually, the reason I put dhcp-client in is that pump wouldn't work on
> > my powerpc. I guess we've gone full circle. :-\
> 
> pump has never failed for me, but all i ever used it for was testing
> that bootp network config in boot-floppies worked, and it does for
> potato which uses pump.  

Pump has repeatedly failed for me on a production dhcp network and on
multiple, different powerpc machines. However, I haven't tried the
latest version with the latest bf.

> > Certainly it's easy enough to control since dbootstrap loads whichever 
> > one it finds, so mess with the extract files to switch back and forth. 
> 
> to what end? pump works, dhcp-client does not. 

pump works for you. 

But the point of the statement was it's easy enough to switch back to pump, 
just change the extract files.

> > The top of the init script on my machine looks like the following.
> > 
> > if [ -f /etc/network/interfaces ]; then
> >         grep -q '^iface.*dhcp' /etc/network/interfaces && exit 0
> > fi
> > 
> > Doesn't this mean that it exits if it encounters a dhcp entry in
> > interfaces?
> 
> yup, and it means it runs if it doesn't find one, which means if your
> network is configured statically in /e/n/interfaces dhcp runs off and
> fucks it up, lets demonstrate shall we?
> 
> root@socrates /root# cat /sbin/dhclient
> #!/bin/sh
> echo "i have now fucked your networking, have a nice day"
> exit 0
> root@socrates /root# cat /etc/network/interfaces
> # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
> 
> # The loopback interface
> iface lo inet loopback
> 
> iface eth0 inet static
>         address 192.168.0.1
>         netmask 255.255.255.0
>         network 192.168.0.0
>         broadcast 192.168.0.255
>         gateway 192.168.0.10
> root@socrates /root# /mnt/etc/init.d/dhcp-client start
> i have now fucked your networking, have a nice day
> root@socrates /root#
> 
> that initscript should have exited without doing anything because my
> network is statically configured.  

Which only proves that the script ran and the daemon is running
needlessly. I agreed it's screwed up, but not that it fucked up your
network. My home network is static and my work is dhcp, I switch back
and forth regularly with dhcp-client managing not to cause problems. I 
would expect that without a dhclient.conf (or whatever) that it doesn't
configure any interfaces.  So, is your complaint substantive? Has 
dhcp-client actually screwed up your static network (when it runs, that 
is ;-)? Just curious.
 
> this is the dhcp-client installed by debootstrap less then a week ago,
> current woody.

It'd be nice if we had a small bootp/dhcp client that didn't have so
many bugs (especially old ones) filed against it. I want a gripping
hand choice.

-- 
Stephen R. Marenka     If life's not fun, you're not doing it right!
<stephen@marenka.net>

Attachment: pgpxntMiWoj4w.pgp
Description: PGP signature


Reply to: