Hi, I've tried it with 2 machines and 2 cables, all have the same issue... a direct connection between my machine and my linksys mini-server works perfectly, so the problem is really the router...
1) powercycled it many times, i've left it cooling down to exclude overheating problems... no change 2) i've restored the router to factory settings... no change 3) i've tried another power supply with the same voltage... no change 4) i've updated the router to the newest firmware yesterday, also didn't solve the problem so, seems that the router is broken then... well, means that i'll have to call the ISP so they exchange the router. Thanks anyway for the help, greetings, vitaminx 2009/7/4 Joe <j...@jretrading.com> > me wrote: > >> hello, >> >> i know, this is not really a debian related problem, nethertheless maybe >> someone could help me with this topic. >> >> I have a D-Link DSL-G624T wireless router which just worked fine... until >> 3 >> weeks before. >> the ethernet connections (all 4 ports) started to loose pings (sometimes >> until 50%), i can't even access the router's web-interface because too >> many >> packets are dropped. this is only a problem with ethernet, wireless works >> perfectly. >> >> The cables are not the problem, my debian config neither (i tried with >> another debian machine, other cables: same problem). >> >> btw. the router is linux based. >> >> That means nothing. Manufacturers can still screw it up with poor > hardware design and/or incompetent scripting. You appear to have a router > problem, confirm this by disconnecting everything but one client computer, > and try it with at least two cables and two computers. You may well have > done this already, if you have nothing else on the wired network. > > 1. Power cycle the router, if you haven't tried that yet, waiting at least > ten seconds before restoring power. I've owned or used five different > low-cost routers, from five different manufacturers, and every one of them > could get into a state where a simple reboot wasn't enough to fix them, they > needed a hard reset. > > 2. Save or write down the configurations, restore the factory defaults, > reboot, reconfigure, reboot. > > 3. Check the voltage of the power brick while under load or substitute > another of suitable ratings. Not easy, but that's the least reliable part of > the router hardware. > > 4. Check the Net for news of firmware upgrades, download from manufacturer > if any seems appropriate. > > If none of this solves or at least alters the problem, you have a faulty > router. If it's out of warranty, buy another one, as it's pretty well > certain to be uneconomic to repair. Keep it for emergency wireless-only use > when your next router breaks... > -- > Joe > -- www ... http://www.callistix.net/ mail ... vitam...@callistix.net irc ... #chezpaeule @ euirc mud ... vitaminx @ aardmud
