DebianThis forum is for the discussion of Debian Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Last question for today, I swear. If you can fix this one you deserve the nobel prize in networking.
I'm running Debian Woody, bf24 flavor, latest stable release. For the last 2 weeks I was running compact flavor and had the same problem. Thought maybe bf24 would fix it but apparently not. Here's the problem:
My internet connection and connection to the home network is agonizingly slow when connected through a Linksys router (wired connection). When I bypass the router and connect direct to cable modem it's as fast as I could ask for. I've installed and autoconfigured both while connected through the router and direct to cable modem. Same result. While connected through the router web pages will time out befoer completely loaded. Even when ftp'ing to and from a machine in the same room it will time out. One machine works better but it has a different ftp program, but even that one times out and is incredibly slow. I've turned off ipv6, same result. When I bypass the router, I use the same cable. When the Debian machine is connected to the router, the other 2 machines connect and download fine. It doesn't start out slow and speed up. It starts out slow, stays slow, and times out. Occasionally I'll see a burst of speed for a very short period of time.
Here is everything I can think of that might helpful in identifying the problem:
Everything looks fine? How long had it been up - received 91.9 MB, transmitted 21.6 MB, how long did that take?
Anyway, I'd set speed and duplex manually on computer and router-port. (I don't know how to do that, unfortunately.)
You get the IP via DHCP, right? If it's static, add it to /etc/hosts as well as gateway.
It had been up all day. The transmitting seemed to go quick, but in spurts. The receiving took the better part of the day. Yes, I'm using DHCP.
I'll try setting the speed and duplex manually. It's worth a shot if I can figure out how. I'm sure it has something to do with the router since it works fine when I bypass it.
Yes, I tried that and got the same result. Tried shutting down the other 2 machines on the router and that did the same thing. Now I'm in the middle of installing sarge as a last ditch effort and that's doing the same thing. Very frustrating.
I don't know wrat, it was put in there by the DHCP autoconfig.
After installing sarge the \000 is gone but the resolve.conf is identical otherwise. Everything else from my original post is identical also; no errors no drops, no overruns. Works fine when bypassing the router, however the performance is even worse than before when going through the router. I've done quite a bit of googling and the only other thing to try that I've been able to come up with is turning off full duplex. Someting I read said collisions my not be reported. Not sure if that's a via-rhine idiosyncrasy. But I can't find anything that tells me how to turn it off.
I believe the problem is somewhere in the router, not really in Debian - since it works fine if you bypass router.
You can try setting speed and duplex on Debian with mii-tools, try 10 and 100 combined with HD and FD. There's a small chance it might work, very easy to try if you have mii-tool.
The only other thing I can think of is if the router for some reason has two routes to the same network - it shouldn't happen but...
Can you check the routers routing-table? What router is it, and what IP's do the other computers have?
I'm interested, because my computer is now doing the same...
Some days downloading at 3000kbps, other days 3kbps!
And it's only my computer, attached to it's own 100-MB port in router. Doesn't help to switch port either.
Yes, just the other day I stumbled on the solution. Just for the heck of it I tried using the cable from another machine and it worked fine. So the problem was the cable. What threw me off was that it worked fine when I bypassed the router and connected directly to the cable modem, so I didn't suspect the cable. I should have known, it's one of those cheap retractable travel cables. I wasted weeks on that problem. But it also explains why my laptop won't connect over ethernet when I travel.