On Thursday 18 July 2002 16:28, Anders Johansson wrote:
After a reboot if it's not started automatically, the dhcpcd command you ran this time should work again as well.
No, it did not. AAARRRGGGHHHH. I write from WinXP. And this command did not work: linux:~ # dhcpcd -d eth0 linux:~ # ping 192.168.1.1 connect: Network is unreachable linux:~ # In fact, I was unable to restore the connection even by deleting the configuration of eth0 and then reinstalling it as I did last time. If I click in Available Hardware, I see that the machine sees it. However after reboot note the output of ifconfig: linux:~ # ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:168 errors:0 dropped:0 overruns:0 frame:0 TX packets:168 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12976 (12.6 Kb) TX bytes:12976 (12.6 Kb) linux:~ #
But it's curious that it won't work on bootup.
Curious? Yeah, I'm pretty curuious myself.
I'm a little at a loss as to why, and without the hardware in front of me to experiment I can't really find out the reason for it.
So am I stuck here? What can I do?? Thanks in advance, nick
//Anders
------- End of forwarded message -------