thank you for the help, this makes sense. when I run "/etc/init.d/networking
restart" I get the message "reconfiguring network interfaces: cat:
/var/run/dhclient.pid: no such file or directory done" What's the
easiest way to tell the system to use "dhclient eth0" at boot, and are there
reasons not to use pump? Thanks!
On Thursday 02 October 2003 10:13 pm, you wrote:
> Some DHCP clients, one of which is dhclient, require certain arcane
> networking options to be enabled in the kernel in order to function. Check
> /var/log/syslog and /var/log/messages for output, or try running `dhclient
> eth0` - failing that, try pump.
>
> Levi
>
> > A tale of two kernels: I have two kernels: one was installed by Debian
> > and one I compiled from a .config file that has previously worked great
> > on my computer for many kernels. lsmod says both kernels have the same
> > eepro100 module loaded when they are running, and DHCP loads on boot for
> > both. When I boot from the one installed by Debian, I can ping out.
> > However when I boot from the one I compiled, I can't ping out.
> > ericdeb:~# ping 68.56.0.5
> > PING 68.56.0.5 (68.56.0.5): 56 data bytes
> > ping: sendto: Network is unreachable
> >
> > For the bad kernel, here's what ifconfig outputs:
> >
> > ericdeb:~# ifconfig
> > eth0 Link encap:Ethernet HWaddr 00:02:B3:9A:40:3B
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:74 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > RX bytes:7234 (7.0 KiB) TX bytes:0 (0.0 b)
> > Interrupt:5 Base address:0x6000
> >
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:64 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:4276 (4.1 KiB) TX bytes:4276 (4.1 KiB)
> >
> > Conversely, here's what the good kernel's ifconfig says:
> >
> > eth0 Link encap:Ethernet HWaddr 00:02:B3:9A:40:3B
> > inet addr:4.8.41.173 Bcast:4.8.63.255 Mask:255.255.224.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:132 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:154 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > RX bytes:28268 (27.6 KiB) TX bytes:15742 (15.3 KiB)
> > Interrupt:19 Base address:0x1000
> >
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:64 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:4276 (4.1 KiB) TX bytes:4276 (4.1 KiB)
> >
> > So I don't get the "inet addr: ..." line with the bad kernel. Any hints
> > on what might be going on that makes one kernel have internet
> > connectivity and the other not? Everything is the same between them as
> > far as I can tell. Oh yeah, back to the tale of two kernels: I want to
> > behead the good kernel, because it has all those extra modules I don't
> > use, but I can't sacrifice the bad one for it because it doen't have
> > internet working, just like the book. Thank you for any ideas you may
> > have. -Eric
>
> -----------------------------------------------------------------------
> This list is provided as an unmoderated internet service by Networked
> Knowledge Systems (NKS). Views and opinions expressed in messages
> posted are those of the author and do not necessarily reflect the
> official policy or position of NKS or any of its employees.
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:49:00 EDT