On Sun, 2003-11-02 at 03:20, Ron Johnson wrote: > On Sun, 2003-11-02 at 05:03, Marshal Wong wrote: > > On Sun, 2003-11-02 at 01:41, Ron Johnson wrote: > > > On Sun, 2003-11-02 at 03:28, Marshal Wong wrote: > > > > On Sat, 2003-11-01 at 20:21, Jeffrey Barish wrote: > > > > > When I use the kernel that I built from the source for 2.4.18-686, I get > > > > > the message: > > > > > > > > > > sendto: Network is unreachable > > > > > > > > > > when I try to ping another machine on my network. Using ifconfig, I > > > > > noticed that eth0 had no IP address assigned. So I did > > > > > > > > > > ifconfig eth0 down > > > > > > > > > > and then > > > > > > > > > > ifconfig eth0 192.168.0.8 netmask 255.255.255.0 up > > > > > > > > > > At that point, ping worked. So it seems as if dhcp is not working. Is > > > > > there something in the kernel configuration that is required to make > > > > > dhcp work? > > > > > > > > > > I am still not able to browse the web. I get the message "Could not > > > > > connect to host ..." no matter what URL I use. > > > > > > > > > > > > > I've noticed that dhcp doesn't change any configurations. If I run > > > > dhclient, it spews out the information for the dhcp, but that's it. It > > > > doesn't change any network settings. It's been that way for a long time > > > > now, but I've just worked around it... Good to know that someone else > > > > is having the problem... > > > > > > > > Anyways, to help you with the "Could no connect to host..." problem, you > > > > probably need to add a default gateway to your routing table. > > > > > > > > Check if the default gateway is reasonable using > > > > > > > > # route (as root. Haha!) > > > > > > > > If not, then > > > > > > > > # route add default gw <ip.address.of.gateway> > > > > > > That should not be necessary. ifup should do that for you, if your > > > /etc/network/interfaces has this in it: > > > auto eth0 > > > iface eth0 inet dhcp > > > > > > > Right, it should. But it doesn't on my computer, for some reason. At > > least it didn't when I was using DHCP. I haven't tested it recently. > > > > It could be a powerpc thing though... > > Which dhcp client are you using? > I'm using dhcp3-client. Actually, this is what happens, now that I've had to try it again. I have my network card driver as a module (sungem.o). I modprobe it. No problem. Of course, then, there is no eth1 in ifconfig. If I try to run "ifup eth1" with /etc/network/interface having the line iface eth1 inet dhcp I get errors such as masee@aldur:~$ sudo ifup eth1 Internet Software Consortium DHCP Client V3.0.1rc11 Copyright 1995-2002 Internet Software Consortium. All rights reserved. For info, please visit http://www.isc.org/products/DHCP Listening on LPF/eth1/00:30:65:69:de:84 Sending on LPF/eth1/00:30:65:69:de:84 Sending on Socket/fallback receive_packet failed on eth1: Network is down DHCPREQUEST on eth1 to 255.255.255.255 port 67 send_packet: Network is down So the only way that I've been able to make it work is: ifconfig eth1 up dhclient eth1 <manually read the given ip addresses ifconfig eth1 <ip.address> route add default gw <ip.address.of.gateway> Running ifconfig eth1 up ifup eth1 doesn't affect the routing tables. Any help would be appreciated. Marshal
Attachment:
signature.asc
Description: This is a digitally signed message part