Don't try to just "run dhcpcd--"!!!
dhcpcd-- run by itself will de-configure your network! It must be run inside 'eval', then use the variables, like this: eval `dhcpcd--` if [ "$IPADDR" != "" ] then ifconfig eth0 $IPADDR netmask $NETMASK up route add default eth0 route add default gw $GATEWAY fi dhcpcd-- just spits out text to set variables, and will *always* zero out the network interface (take a look at /usr/bin/dhcpcd--.lua). There has been some confusion about this program, this is not dhcpcd, and the implication of the "minus-minus" is that it is the opposite of, say, going from C to C++, that is, it is less, not more, capable, than dhcpcd. Given that it worked on boot, your network is working, and you probably just have a routing problem, or the wrong gateway in the dhcp server, what happens if you "ping 192.168.1.1" right after bootup? -Tom On 30 Dec 2001, Christian E. [iso-8859-1] J�rgensen wrote: > Date: 30 Dec 2001 15:32:00 +0100 > From: "Christian E. [iso-8859-1] J�rgensen" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: [tomsrtbt] Tulip-based cardbus NIC and tomsrtbt-1.7.361 > > Gernot Fink <[EMAIL PROTECTED]> writes: > > > This loocks like your interface is ok,but not configurated. > > > > what happens if you type : > > ifconfig eth0 192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0 > > Darn, I've just found out that I've been using a faulty cable to connect > to my DHCP server :-(. > > Anyway, right after boot, "ifconfig" now gives me: > > eth0 Link encap:Ethernet HWaddr 10:80:00:80:00:80 > inet addr:192.168.1.7 Bcast:255.255.255.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:2 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2 errors:1 dropped:0 overruns:1 carrier:0 > collisions:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > Interrupt:9 Base address:0xa00 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0 > UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > However, "ping www.google.com" gives me: > > eth0: 21143 10baseT link beat good. > eth0: The transmitter stopped! CSR5 is fc06c012, CSR6 ff970117. > eth0: 21143 10baseT link beat good. > ping: www.google.com: Host name lookup failure > > Also, if I run "dhcpcd--" again, I get: > > Starting dhcpcd-- > eth0: 21143 10baseT link beat good. > Looking for DHCPOFFER... > Looking for DHCPACK... > IPADDR=192.168.1.7 > GATEWAY=192.168.1.1 > NETMASK=255.255.255.0 > DNS_1=194.239.134.83 > # eth0: The transmitter stopped! CSR5 is fc67c016, CSR6 ff972117. > eth0: 21143 10baseT link beat good. > > If I now run "ifconfig" again, I get: > > eth0 Link encap:Ethernet HWaddr 10:80:00:80:00:80 > inet addr:0.0.0.0 Bcast:255.255.255.255 Mask:0.0.0.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:4 errors:0 dropped:0 overruns:0 frame:0 > TX packets:11 errors:3 dropped:0 overruns:3 carrier:0 > collisions:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > Interrupt:9 Base address:0xa00 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0 > UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1 > RX packets:9 errors:0 dropped:0 overruns:0 frame:0 > TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > Isn't "dhcpcd--" supposed to configure my NIC? >
