Tom Oehser <[EMAIL PROTECTED]> writes: > 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.
Fine, then we got that one out of the way :-). > 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? PING 192.168.1.1 (192.168.1.1): 56 data bytes eth0: 21143 10baseT link beat good. eth0: The transmitter stopped! CSR5 is fc67c016, CSR6 ff972117. eth0: 21143 10baseT link beat good. (Some time passes and I hit C-c.) --- 192.168.1.1 ping statistics --- 258 packets transmitted, 0 packets received, 100% packet loss That's it! :-( What now?
