LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page 40-75% packet loss on average with wireless networking Slackware 13.0
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-26-2010, 06:19 PM   #1
linux32
LQ Newbie
 
Registered: Jan 2010
Posts: 6

Rep: Reputation: 0
40-75% packet loss on average with wireless networking Slackware 13.0

Hello all

I am running Slackware 13.0 on a old dell dimension 4500.
The install went fine. sound worked, graphics where good.
Everything was going perfect. until i worked on wireless.
i have a realtek rtl8185 wireless chipset card. I got the wireless
Linux wireless driver. It worked on both Mint 5.0 and backtrack 4.0.
so I untar the file. cd to the dir and type make then make install
and reboot. like I have always done.

I was having to fight with wpa_gui and finally got it working but then it would go in and out on the connect and disconnect feature. so I tried using iwconfig. did not get muc luck with that either so i installed wicd and finally got a ip address after fighting with it would give me in a ping like 75% packet loss. so I read a lot of post and try to find stuff before I post. and while reading I learned that you guys normally ask for info on the hardware and software so here you go.
but I will say first that I read about adjusting the mtu to fix packet loss, I showed some of the changes I made in it around the pings I know it is a mess I am sorry I tried to make it readable. if you need more information let me know. I cant get online using a web browser or if I can only for one or two pages. any help would be great. thank you.

Code:
bash-3.1# 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:22 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1226 (1.1 KiB)  TX bytes:1226 (1.1 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:14:d1:41:93:6e  
          inet addr:192.168.1.105  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::214:d1ff:fe41:936e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1300  Metric:1
          RX packets:179 errors:2103 dropped:218 overruns:0 frame:0
          TX packets:1482 errors:259 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:19438 (18.9 KiB)  TX bytes:95530 (93.2 KiB)
          Interrupt:17 Memory:f8822c00-f8822d00 

bash-3.1# ping 64.113.186.194 (a server that i run)
PING 64.113.186.194 (64.113.186.194) 56(84) bytes of data.
64 bytes from 64.113.186.194: icmp_seq=1 ttl=44 time=93.0 ms
64 bytes from 64.113.186.194: icmp_seq=3 ttl=44 time=8041 ms
64 bytes from 64.113.186.194: icmp_seq=4 ttl=44 time=7139 ms
64 bytes from 64.113.186.194: icmp_seq=5 ttl=44 time=6143 ms
64 bytes from 64.113.186.194: icmp_seq=6 ttl=44 time=5150 ms
64 bytes from 64.113.186.194: icmp_seq=7 ttl=44 time=4153 ms
64 bytes from 64.113.186.194: icmp_seq=8 ttl=44 time=3172 ms
64 bytes from 64.113.186.194: icmp_seq=9 ttl=44 time=2179 ms
64 bytes from 64.113.186.194: icmp_seq=10 ttl=44 time=1191 ms
64 bytes from 64.113.186.194: icmp_seq=11 ttl=44 time=193 ms
64 bytes from 64.113.186.194: icmp_seq=13 ttl=44 time=1999 ms
64 bytes from 64.113.186.194: icmp_seq=14 ttl=44 time=1096 ms
64 bytes from 64.113.186.194: icmp_seq=15 ttl=44 time=106 ms
^C
--- 64.113.186.194 ping statistics ---
16 packets transmitted, 13 received, 18% packet loss, time 15002ms
rtt min/avg/max/mdev = 93.070/3127.711/8041.094/2652.599 ms, pipe 9

bash-3.1# ip link set dev wlan0 mtu 2000

bash-3.1# ping 64.113.186.194
PING 64.113.186.194 (64.113.186.194) 56(84) bytes of data.
64 bytes from 64.113.186.194: icmp_seq=4 ttl=44 time=7480 ms
64 bytes from 64.113.186.194: icmp_seq=5 ttl=44 time=6584 ms
64 bytes from 64.113.186.194: icmp_seq=6 ttl=44 time=5588 ms
64 bytes from 64.113.186.194: icmp_seq=7 ttl=44 time=4592 ms
64 bytes from 64.113.186.194: icmp_seq=8 ttl=44 time=3595 ms
64 bytes from 64.113.186.194: icmp_seq=9 ttl=44 time=2599 ms
64 bytes from 64.113.186.194: icmp_seq=10 ttl=44 time=1604 ms
64 bytes from 64.113.186.194: icmp_seq=11 ttl=44 time=610 ms
64 bytes from 64.113.186.194: icmp_seq=12 ttl=44 time=1694 ms
64 bytes from 64.113.186.194: icmp_seq=13 ttl=44 time=802 ms
^C
--- 64.113.186.194 ping statistics ---
18 packets transmitted, 10 received, 44% packet loss, time 16998ms
rtt min/avg/max/mdev = 610.616/3515.277/7480.057/2328.057 ms, pipe 8

bash-3.1# ping 64.113.186.194
PING 64.113.186.194 (64.113.186.194) 56(84) bytes of data.
64 bytes from 64.113.186.194: icmp_seq=1 ttl=44 time=104 ms
64 bytes from 64.113.186.194: icmp_seq=4 ttl=44 time=5482 ms
64 bytes from 64.113.186.194: icmp_seq=5 ttl=44 time=4583 ms
64 bytes from 64.113.186.194: icmp_seq=6 ttl=44 time=3586 ms
64 bytes from 64.113.186.194: icmp_seq=7 ttl=44 time=2591 ms
64 bytes from 64.113.186.194: icmp_seq=8 ttl=44 time=1610 ms
64 bytes from 64.113.186.194: icmp_seq=9 ttl=44 time=611 ms
64 bytes from 64.113.186.194: icmp_seq=16 ttl=44 time=4834 ms
64 bytes from 64.113.186.194: icmp_seq=17 ttl=44 time=3940 ms
64 bytes from 64.113.186.194: icmp_seq=18 ttl=44 time=2954 ms
64 bytes from 64.113.186.194: icmp_seq=19 ttl=44 time=1955 ms
64 bytes from 64.113.186.194: icmp_seq=20 ttl=44 time=956 ms
64 bytes from 64.113.186.194: icmp_seq=21 ttl=44 time=55.0 ms
64 bytes from 64.113.186.194: icmp_seq=22 ttl=44 time=1543 ms
64 bytes from 64.113.186.194: icmp_seq=23 ttl=44 time=646 ms
64 bytes from 64.113.186.194: icmp_seq=26 ttl=44 time=2425 ms
64 bytes from 64.113.186.194: icmp_seq=27 ttl=44 time=1531 ms
64 bytes from 64.113.186.194: icmp_seq=28 ttl=44 time=534 ms
64 bytes from 64.113.186.194: icmp_seq=29 ttl=44 time=3563 ms
64 bytes from 64.113.186.194: icmp_seq=30 ttl=44 time=2669 ms
64 bytes from 64.113.186.194: icmp_seq=31 ttl=44 time=1674 ms
64 bytes from 64.113.186.194: icmp_seq=32 ttl=44 time=676 ms
^C
--- 64.113.186.194 ping statistics ---
33 packets transmitted, 22 received, 33% packet loss, time 32006ms
rtt min/avg/max/mdev = 55.056/2206.167/5482.776/1557.010 ms, pipe 6

bash-3.1# 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:23 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1314 (1.2 KiB)  TX bytes:1314 (1.2 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:14:d1:41:93:6e  
          UP BROADCAST MULTICAST  MTU:2000  Metric:1
          RX packets:503 errors:4886 dropped:2235 overruns:0 frame:0
          TX packets:6781 errors:883 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:58467 (57.0 KiB)  TX bytes:409008 (399.4 KiB)
          Interrupt:17 Memory:f8822c00-f8822d00 

(my hardware )

bash-3.1# lspci
00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 11)
00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge (rev 11)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 4000] (rev c1)
02:01.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
02:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller (rev 20)



bash-3.1# iwconfig
lo        no wireless extensions.

wlan0     802.11bg linked  ESSID:"JSKNET"  
          Mode:Managed  Frequency=2.437 GHz  Access Point: 00:1C:10:B4:65:51   
          Bit Rate=54 Mb/s   
          Retry:on   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=70/100  Signal level=-46 dBm  Noise level=-99 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

bash-3.1# ping 64.113.186.194
PING 64.113.186.194 (64.113.186.194) 56(84) bytes of data.
64 bytes from 64.113.186.194: icmp_seq=1 ttl=44 time=99.4 ms
64 bytes from 64.113.186.194: icmp_seq=8 ttl=44 time=216 ms
64 bytes from 64.113.186.194: icmp_seq=9 ttl=44 time=1019 ms
64 bytes from 64.113.186.194: icmp_seq=10 ttl=44 time=123 ms
64 bytes from 64.113.186.194: icmp_seq=14 ttl=44 time=534 ms
^C
--- 64.113.186.194 ping statistics ---
15 packets transmitted, 5 received, 66% packet loss, time 14005ms
rtt min/avg/max/mdev = 99.484/398.773/1019.104/346.838 ms, pipe 2

bash-3.1# ip link set dev wlan0 mtu 1350

bash-3.1# ping 64.113.186.194
PING 64.113.186.194 (64.113.186.194) 56(84) bytes of data.
64 bytes from 64.113.186.194: icmp_seq=1 ttl=44 time=105 ms
64 bytes from 64.113.186.194: icmp_seq=2 ttl=44 time=153 ms
64 bytes from 64.113.186.194: icmp_seq=4 ttl=44 time=306 ms
64 bytes from 64.113.186.194: icmp_seq=6 ttl=44 time=769 ms
64 bytes from 64.113.186.194: icmp_seq=10 ttl=44 time=250 ms
64 bytes from 64.113.186.194: icmp_seq=11 ttl=44 time=159 ms
^C
--- 64.113.186.194 ping statistics ---
14 packets transmitted, 6 received, 57% packet loss, time 13007ms
rtt min/avg/max/mdev = 105.904/290.836/769.964/224.326 ms

bash-3.1# ip link set dev wlan0 mtu 500 

bash-3.1# ping 64.113.186.194
PING 64.113.186.194 (64.113.186.194) 56(84) bytes of data.
64 bytes from 64.113.186.194: icmp_seq=4 ttl=44 time=226 ms
64 bytes from 64.113.186.194: icmp_seq=5 ttl=44 time=109 ms
64 bytes from 64.113.186.194: icmp_seq=14 ttl=44 time=560 ms
64 bytes from 64.113.186.194: icmp_seq=16 ttl=44 time=359 ms
^C
--- 64.113.186.194 ping statistics ---
17 packets transmitted, 4 received, 76% packet loss, time 16002ms
rtt min/avg/max/mdev = 109.888/313.950/560.199/167.343 ms

bash-3.1# iwlist scan
lo        Interface doesn't support scanning.

wlan0     Scan completed :
          Cell 01 - Address: 00:15:CE:C1:C1:63
                    ESSID:"WOW!346548"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:11
                    Encryption key:on
                    Bit Rates:54 Mb/s
                    Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 
                    Quality=45/100  Signal level=-64 dBm  Noise level=-82 dBm
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    Extra: Last beacon: 21ms ago
          Cell 02 - Address: 00:14:A5:8A:E9:EB
                    ESSID:"Motorola520"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:1
                    Encryption key:on
                    Bit Rates:54 Mb/s
                    Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 
                    Quality=36/100  Signal level=-70 dBm  Noise level=-76 dBm
                    Extra: Last beacon: 158ms ago
          Cell 03 - Address: 00:18:F8:B5:78:72
                    ESSID:"linksys"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:6
                    Encryption key:off
                    Bit Rates:54 Mb/s
                    Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 
                    Quality=49/100  Signal level=-61 dBm  Noise level=-86 dBm
                    Extra: Last beacon: 0ms ago
          Cell 04 - Address: 00:1C:10:B4:65:51
                    ESSID:"JSKNET"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:6
                    Encryption key:on
                    Bit Rates:54 Mb/s
                    Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 
                    Quality=67/100  Signal level=-49 dBm  Noise level=-99 dBm
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    Extra: Last beacon: 79ms ago
          Cell 05 - Address: 94:44:52:32:21:D3
                    ESSID:"woodyh1026"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:6
                    Encryption key:off
                    Bit Rates:54 Mb/s
                    Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 
                    Quality=50/100  Signal level=-60 dBm  Noise level=-86 dBm
                    Extra: Last beacon: 103ms ago

bash-3.1#
again thank you.
 
Old 06-26-2010, 07:32 PM   #2
davem7
LQ Newbie
 
Registered: Jun 2010
Distribution: OpenSUSE (tumbleweed), Debian (server)
Posts: 19

Rep: Reputation: 0
There's a long standing multi-distribution bug for the rtl8187 chipset. I wouldn't be surprised if it also effects your chipset? For some reason I did not have the issue under Gentoo about four months ago (might be fruitful to see which kernel they used then) but now after recently installing slackware -current I am running into the issue.

The only workaround that worked for me thus far as someone utilizing wpa2 aes psk encryption was to change the rate to be lower (as opposed to 54M auto). I put mine all the way down to "1M" (no auto) and now rarely experience the packet loss or disconnects, albeit with the much lower speeds (at least it is now somewhat useable whereas before it was not for me). Note again that I am using rtl8187 though, not rtl8185.

In my case I'm probably just going to buy another wireless card.
Last edited by davem7; 06-26-2010 at 07:34 PM.
 
Old 06-27-2010, 08:49 AM   #3
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,925
Blog Entries: 44

Rep: Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159
Hi,

You did try the module for the 'rtl8180' for Slackware 13.0 kernel 2.6.29.5? What happened when you boot the system initially with the wireless device installed with the original module?
 
Old 06-28-2010, 03:45 PM   #4
linux32
LQ Newbie
 
Registered: Jan 2010
Posts: 6

Original Poster
Rep: Reputation: 0
@davem7 - That is interesting thank you for the info on the bug i will keep it in mind if i ever go to another distro that it is out there.
I tried uninstalling the rtl8185 linux driver and slapping in the windows driver threw ndiswrapper and it got me a step closer. what i mean is can now get a ip (not easily but i can get one) and keep it (not for very long) and not have a high packet lose like 0-12% packet lose. what i meant about not keeping it, it seems it throws me off after a short period of time. now also my computer will freeze every so many second for like 1 second then unfreeze then refreeze etc... then again it could be the computer it is like 10 years old and came with win98 i think first

@onebuck - hmm.. no i have not tried the rtl8180 but i will. yes that is the kernel and os. when i first booted it wpa_gui said it could not find the wpa supplicant or whatever it is called (got a lot on the mind at the moment so cant think of computer terms real well) so i ran

Code:
# wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B
then wpa_gui went all crazy. I scanned for a network and found my network AP and tried to set it up but it would connect disconnect try to get a handshake the disconnect then connect ... so on and so forth. so i figured hey it is the file maybe i should edit it. I typed in

Code:
nano /etc/wpa_supplicant.conf
so i tried to edit the file but i would get errors around the PSK.. so i gave up on that and said i am going to try manually.

I type in

Code:
iwconfig wlan0 essid JSKNET
iwconfig wlan0 key s: m1a1x1c1a22t34
dhcpcd wlan0
i messed around with more stuff i cant remember right at this second.
so anyway i got feed up and said i am going to wicd... i got it install it is the 1.70 version i think? anyway i got that install and it found my router and i put in my pass-phrase etc nothing worked. it would get to validating and it would give me a bad password error. it was right i made sure it i tried typing it in different ways i tried having it use dhcpcd then dhclient under the settings. i tried using wext driver i tried ndiswrapper driver i tried a lot of combos in the settings and nothing worked. well for like a second i got a ip for a few seconds but then it disconnected or it had such a bad packet lose you could not do anything with it. so i got to thinking what if i change the driver type from linux based to windows. so i removed the linux driver (dont know if i got it off fully but i think so not showing up under lsmod)and used ndiswrapper. it installed everything with out a problem. and right after i did it i got a ip address for like 15 mins then it started acting up again.

so i rebooted and i again was able to connect but it lasted a little longer but then went offline. i am not sure where to go next but i will try the rtl8180 first off

thank you both
 
Old 06-28-2010, 07:10 PM   #5
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,925
Blog Entries: 44

Rep: Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159
Hi,

You should look at 'Configuring your network in Slackware' to setup the network.
 
  


Reply

Tags
linux, networking, slackware



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
70% packet loss bingviini Linux - Networking 5 11-18-2004 11:35 AM
What can cause packet loss? Micah Linux - Hardware 8 03-15-2004 12:31 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:02 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration