On Tue, 16 Aug 2011 06:18:01 +1000, Heddle Weaver wrote: > On 16 August 2011 05:51, Camaleón <noela...@gmail.com> wrote:
>> How about a simple "wget 192.168.1.254"? >> >> > weaver@Bandit:~$ su > Password: > Bandit:/home/weaver# wget 192.168.1.254 --2011-08-16 06:06:49-- > http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: > Connection timed out. Retrying. > > --2011-08-16 06:07:36-- (try: 2) http://192.168.1.254/ Connecting to > 192.168.1.254:80... failed: Connection timed out. Retrying. > > --2011-08-16 06:08:23-- (try: 3) http://192.168.1.254/ Connecting to > 192.168.1.254:80... failed: Connection timed out. Retrying. Hum... are you sure your router is still at "192.168.1.254"? (...) >> > I think I have messed up my install inadvertently, in a way that the >> > fact that it is SID doesn't account for. >> >> Really, I can't see how your network configuration can be a problem >> here. If you have setup static values for your NIC and you can >> ping/reach your DSL router you should get the same you get when using a >> Windows client. >> >> There is no more magic behind an ethernet device and that's precisely >> its best bet: it works regardless the OS and does not require for >> special drivers :-) >> >> > I'm thinking it must be something under the network config. Something in > the O.S. itself that has come adrift. I'll try a reinstall. > My /home partition is on an external drive, so the data is safe and a > reinstall doesn't represent as much of a problem as it would otherwise. Reinstalling is a "no-no" in the linux ecosphere, is the last resort for the brave and valiants riders (just kidding :-P)... and in this case I'm afraid you won't obtain any gain in doing it. You better hang in there and try to solve the mistery by yourself :-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.08.16.12.12...@gmail.com
