I’ve recently installed OpenSuse. I’m a *nix newbie but so far I like it a lot better than Ubuntu. I’m having several problems though and here’s one of them: I have cable and my upload rate is crawling here even though I have 512 kbps. I first realised when trying to upload a file and I saw it was not uploading. Then I tried to upload a video to YouTube and it produced an error. I was just trying to make a connection test but it was going really slow and eventually hanged.
I’m using the 64 bit OpenSuse version with a cable connection using a WiFi router. I would like to post more information about the wireless card but I’m afraid I’m not really sure how to do it.
Go to the following site and report back on your download and upload speeds. In fact, all information you are presented with, on this screen, would be good to know here. No need to include your location though.
Log into your modem and or router and get the following info.Upstream SNR, Upstream Transmit (TX), Upstream Receive (RX).
Also do a traceroute to a few servers.
#traceroute something.com
I would suggest pathping, but there doesn’t seem to be a Linux equivalent to it.
This is weird, I logged on the modem and I can’t access that information. It says: “This feature has not been enabled in your cable modem. Please contact your data services provider for more information about this feature and its availability on the network.”
Here are a couple of results of traceroute:
traceroute to www.google.com (209.85.195.104), 30 hops max, 40 byte packets using UDP
1 GW-239.fibertel.com.ar (24.232.239.1) 67.649 ms 78.408 ms 112.109 ms
2 * * *
3 * * *
4 * * *
5 9-165-89-200.fibertel.com.ar (200.89.165.9) 448.139 ms 13-165-89-200.fibertel.com.ar (200.89.165.13) 473.718 ms 505.836 ms
6 * * *
7 * * *
8 200.49.159.254 (200.49.159.254) 44.259 ms 75.367 ms 106.673 ms
9 209.85.251.28 (209.85.251.28) 137.078 ms 167.742 ms 198.463 ms
10 209.85.251.6 (209.85.251.6) 239.964 ms 259.727 ms 291.439 ms
11 eze03s01-in-f104.1e100.net (209.85.195.104) 319.104 ms 349.232 ms 379.232 ms
traceroute to www.mediafire.com (205.196.120.8), 30 hops max, 40 byte packets using UDP
1 GW-239.fibertel.com.ar (24.232.239.1) 40.037 ms 68.001 ms 97.074 ms
2 * * *
3 * * *
4 * * *
5 13-165-89-200.fibertel.com.ar (200.89.165.13) 387.191 ms 9-165-89-200.fibertel.com.ar (200.89.165.9) 417.164 ms 445.165 ms
6 * * *
7 * * *
8 200-63-151-33.speedy.com.ar (200.63.151.33) 40.192 ms 70.185 ms 97.042 ms
9 So4-0-0-0-grtbueba2.red.telefonica-wholesale.net.10.16.84.in-addr.arpa (84.16.10.141) 124.589 ms 152.981 ms 181.486 ms
10 So4-0-0-0-grtbueba2.red.telefonica-wholesale.net.10.16.84.in-addr.arpa (84.16.10.141) 209.015 ms 236.969 ms 265.801 ms
11 Xe5-1-1-0-grtmiabr7.red.telefonica-wholesale.net.125.142.94.in-addr.arpa (94.142.125.114) 457.537 ms Xe2-1-3-0-grtmiabr8.red.telefonica-wholesale.net.123.142.94.in-addr.arpa (94.142.123.58) 459.983 ms 487.285 ms
12 Xe-0-0-2-0-grtwaseq3.red.telefonica-wholesale.net (94.142.124.109) 204.778 ms Xe0-0-1-0-grtwaseq3.red.telefonica-wholesale.net (94.142.124.105) 232.867 ms 259.948 ms
13 xe-0-5-0-2.r01.asbnva02.us.bb.gin.ntt.net (129.250.8.249) 287.624 ms 302.486 ms 341.422 ms
14 ae-4.r20.asbnva02.us.bb.gin.ntt.net (129.250.3.10) 368.444 ms 383.563 ms 410.453 ms
15 as-1.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.42) 455.917 ms 498.724 ms 523.276 ms
16 ae-2.r07.dllstx09.us.bb.gin.ntt.net (129.250.3.67) 549.659 ms 578.800 ms 602.107 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
traceroute to www.abovetopsecret.com (67.228.0.162), 30 hops max, 40 byte packets using UDP
1 GW-239.fibertel.com.ar (24.232.239.1) 44.693 ms 75.178 ms 106.759 ms
2 * * *
3 * * *
4 * * *
5 13-165-89-200.fibertel.com.ar (200.89.165.13) 407.407 ms 435.803 ms 465.558 ms
6 2-165-89-200.fibertel.com.ar (200.89.165.2) 495.183 ms 524.227 ms 553.554 ms
7 86-165-89-200.fibertel.com.ar (200.89.165.86) 38.475 ms 75.505 ms 101.758 ms
8 200-63-151-65.speedy.com.ar (200.63.151.65) 42.048 ms 71.136 ms 99.258 ms
9 So6-0-0-0-grtbuecu1.red.telefonica-wholesale.net (84.16.6.5) 128.268 ms 156.124 ms 195.122 ms
10 Xe-7-1-0-0-grtmiabr8.red.telefonica-wholesale.net.121.142.94.in-addr.arpa (94.142.121.238) 350.546 ms Xe-4-0-0-0-grtmiabr7.red.telefonica-wholesale.net.121.142.94.in-addr.arpa (94.142.121.222) 369.053 ms 396.589 ms
11 Xe0-0-2-0-grtmiana2.red.telefonica-wholesale.net.121.142.94.in-addr.arpa (94.142.121.145) 434.335 ms 452.213 ms 478.927 ms
12 softlayer-4-0-2-0-grtmiana2.red.telefonica-wholesale.net (213.140.51.190) 516.691 ms 536.194 ms 563.736 ms
13 po1.bbr02.tm01.mia01.networklayer.com (173.192.18.175) 591.353 ms 621.217 ms 644.349 ms
14 * * *
15 * * *
16 po6.dar01.sr01.dal01.networklayer.com (173.192.18.211) 334.776 ms 363.836 ms 387.403 ms
17 po1.fcr03.sr04.dal01.networklayer.com (66.228.118.186) 431.046 ms 444.009 ms 466.751 ms
18 67.228.0.162-static.reverse.softlayer.com (67.228.0.162) 491.542 ms 1475.065 ms 1504.714 ms
Yes you do have an upload problem. IMO its your DNS server that’s causing the delay. You get to your gateway and then it dies when it should be less the 20 ms to the next hop.
Define your DNS nameservers on your router and not on your NICs.
Try OpenDNS or some other fast DNS Server. Free Fast Public DNS Servers List
Hopefully, your ISP has not throttled your upload bandwidth but if you’re sure you are supposed to get 512 vs 384 upload then you should also call your ISP.
Thanks for your suggestions, I changed the DNS servers and the problem persists. I do not believe it’s the ISP’s fault because I’m getting normal rates at my Windows partition.
I’m starting to think it’s a firmware issue. I have a broadcom card and I’ve been reading about the broadcom-wl drivers that supposedly work good, yet I’m haven’t been able to make them work. They’re at packman repositories, I choose the one that’s right for my kernel (default) and then I reboot and I can’t connect to my router via wifi, in fact NetworkManager doesn’t appear to be detecting any networks. So I had to go back to the legacy drivers, so perhaps this is the cause.
I have seen that before but I’m not sure how to build it. If I write “make install” I get this:
install -D -m 755 wl.ko /lib/modules/uname -r/kernel/drivers/net/wireless/wl.ko
install: no se puede efectuar `stat’ sobre «wl.ko»: No existe el fichero o el directorio
make: *** [install] Error 1
It’s in Spanish, it means that it can’t find the wl.ko directory.
First off I did install this on my Dell Laptop and it worked like a champ. Second, you must READ and FOLLOW the instructions as given. If there is a portion of the ACTUAL installation procedure that does not work then ask about it and refer to the README document on that page. Since the term MAKE INSTALL is not in the readme file as something to do, perhaps that is why it does not work. Please read through the document one more time.
Ok, that was my bad, I was looking for instructions inside the tarball, not on the site. I managed to build and install the drivers and it didn’t worked. I uninstalled the ssb ones and I even follow the instructions to blacklist them (even though after I rebooted they were still there, but that’s another subject). I unloaded the drivers and loaded the wl ones, I could see them when using the command lsmod | grep “b43|ssb|wl”. Regardless NetworkManager didn’t scan for networks.
I should mention that this driver appears to be the same on the Packman repository which I have available to install via the “add/remove software” option, because that one didn’t works for me either. I don’t know what I’m doing wrong, I’m removing the legacy drivers and installing the correct one for my kernel (which is default), yet something is not working properly.
You can run this script file and it will create a text file that includes a lot of information about your setup. Why not copy from it any network info you see about your wireless hardware and post it online for us to see.
This is the very same chipset that is in my Laptop that worked. So, I am going to suggest there is a missing step or something else that you are missing. So, I know that no one wants to look silly, but we are trying to help here. What I ask is that you open up a terminal session, do the steps one at a time and capture the output and post it online for us to see. You can blank anything personnel, as we don’t need to see it, but I want to see the system response to your commands. I never say never, but I feel certain that we can get you up and running AND it only takes one missed step, one error message you do not understand and it does not work.
I would run YaST / Network Devices / Network Services and make sure you are set for ifup. You can do a scan while in this editor as well as enter your ssid and password.
Well, after changing to ifup I could choose wl from the drivers’ list but no network was detected. I entered my SSID manually with no results. NetworkManager didn’t show any networks either.
I was thinking in using ndiswrapper on the windows driver but first, I can’t seem to find it on Broadcom’s site, and also I have a question: should I remove the b43 driver before trying the Windows one? Is b43-fwcutter a necessary package?
Ok, I followed a tutorial to use the 64 bit XP version of the driver and that didn’t worked neither with NetworkManager nor ifup. The problem is the same, wlan0 is not present and the other interfaces are not wireless. Perhaps I should reinstall the system and see what happens.
EDIT: Reading the previous log I realise that I do get a wireless interface with broadcom-wl (eth1), the problem appears to be merely that it’s not scanning.
