LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 05-28-2009, 02:36 PM   #1
JohanP0
LQ Newbie
 
Registered: Jun 2003
Location: Munich
Posts: 6

Rep: Reputation: 0
Loosing packages


Hi

I am runnung a PC with Mepis7 and having a very instable network connection. I was previosly running 6.5 and the network was running flawlessly. I know that the HW is OK. I have a windows installation where I don't have problems. I also have a Toshiba NB100 standing (Ubuntu 9.04) next to me with no problems.

My problem is that I have an instable network. All of a sudden it just freezes. This is what a ping sequence looks like

PING www.gmx.de (217.72.202.249) 56(84) bytes of data.
64 bytes from www.gmx.de (217.72.202.249): icmp_seq=1 ttl=55 time=49.9 ms
64 bytes from www.gmx.de (217.72.202.249): icmp_seq=2 ttl=55 time=59.4 ms
64 bytes from www.gmx.de (217.72.202.249): icmp_seq=12 ttl=55 time=52.8 ms
64 bytes from www.gmx.de (217.72.202.249): icmp_seq=17 ttl=55 time=51.0 ms
64 bytes from www.gmx.de (217.72.202.249): icmp_seq=18 ttl=55 time=51.3 ms
64 bytes from www.gmx.de (217.72.202.249): icmp_seq=19 ttl=55 time=52.2 ms
64 bytes from www.gmx.de (217.72.202.249): icmp_seq=20 ttl=55 time=49.6 ms
64 bytes from www.gmx.de (217.72.202.249): icmp_seq=21 ttl=55 time=48.3 ms
64 bytes from www.gmx.de (217.72.202.249): icmp_seq=22 ttl=55 time=48.6 ms
64 bytes from www.gmx.de (217.72.202.249): icmp_seq=26 ttl=55 time=51.0 ms
64 bytes from www.gmx.de (217.72.202.249): icmp_seq=29 ttl=55 time=47.3 ms
64 bytes from www.gmx.de (217.72.202.249): icmp_seq=31 ttl=55 time=48.5 ms
C64 bytes from www.gmx.de (217.72.202.249): icmp_seq=36 ttl=55 time=48.7 ms

36 packets transmitted, 13 received, 63% packet loss, time 60261ms
rtt min/avg/max/mdev = 47.321/50.708/59.426/2.988 ms

At the moment I have the system set up with fixed IP but DHCP is giving me the same headache

here the lspci-vv

05:03.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01)
Subsystem: Tekram Technology Co.,Ltd. ALLNET ALL0271 Wireless PCI Adapter
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx+
Latency: 64 (2500ns min, 7000ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at fd9fc000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: prism54pci
Kernel modules: prism54, p54pci

(I have also tried with other cards, but with the same problem...)

wlan0 Link encap:Ethernet HWaddr 00:01:36:0d:cd:bc
inet addr:192.168.0.67 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::201:36ff:fe0d:cdbc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:47108 errors:0 dropped:0 overruns:0 frame:0
TX packets:34951 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:57560087 (54.8 MiB) TX bytes:3844871 (3.6 MiB)


root@johans:/home/johan# iwconfig
lo no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:"Z10"
Mode:Managed Frequency:2.412 GHz Access Point: 00:17:9A:F2:96:71
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thrff Fragment thr=2352 B
Encryption key:CDAC-XXXXXXXXXXXXXX-6A Security modepen
Power Managementff
Link Quality=51/100 Signal level:65/127
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

the relevant part of dmesg

DROPPED IN=wlan0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:1b:77:18:3b:e0:08:00 SRC=192.168.0.168 DST=192.168.0.255 LEN=1348 TOS=0x00 PREC=0x00 TTL=128 ID=368 PROTO=UDP SPT=6646 DPT=6646 LEN=1328
DROPPED IN= OUT=wlan0 SRC=192.168.0.67 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF OPT (94040000) PROTO=2
firmware: requesting isl3886
wlan0: authenticate with AP 00:17:9a:f2:96:71
ADDRCONF(NETDEV_UP): wlan0: link is not ready
DROPPED IN= OUT=wlan0 SRC=192.168.0.67 DST=224.0.0.22 LEN=48 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF OPT (94040000) PROTO=2
wlan0: authenticate with AP 00:17:9a:f2:96:71
wlan0: authenticated
wlan0: associate with AP 00:17:9a:f2:96:71
wlan0: RX AssocResp from 00:17:9a:f2:96:71 (capab=0x431 status=0 aid=5)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
DROPPED IN=wlan0 OUT= MAC= SRC=192.168.0.67 DST=224.0.0.251 LEN=226 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=206
DROPPED IN=wlan0 OUT= MAC= SRC=192.168.0.67 DST=224.0.0.251 LEN=226 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=206


I have been trying to figure out what is going on here by lookig at wireshark. What I can see is that I have packet losses, but I have no idea where that comes from. To me this looks like a configuration error, but I have no idea where that would be. Any hints would be welcome. If I don't get this fixed I guess I will move on to another distro. I really liked MEPIS the last 2 years or so.

Any help would be appreciated
Attached Thumbnails
Click image for larger version

Name:	snapshot1.png
Views:	17
Size:	137.6 KB
ID:	712  
 
Old 06-19-2009, 05:43 AM   #2
archtoad6
Senior Member
 
Registered: Oct 2004
Location: Houston, TX (usa)
Distribution: MEPIS, Debian, Knoppix,
Posts: 4,727
Blog Entries: 15

Rep: Reputation: 234Reputation: 234Reputation: 234
Before you give up on MEPIS, give 8 a try.

I don't know if this is applicable to your situation; but about 2 months ago,
I was asked to help w/ a Dell laptop that had MEPIS 7 installed & wireless wasn't working. After several attempts, I tried a MEPIS 8 LiveCD; when it worked, I installed it.

I'm not sure what changed, maybe new drivers -- 7 wasn't finding the built-in Broadcom chip -- or possibly improvements in the MEPIS Network Assistant.
 
  


Reply



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
Loosing Gnome Abnoba12 Fedora 3 06-10-2007 01:05 PM
Are we loosing SuSE? alfredh SUSE / openSUSE 15 07-24-2006 04:56 AM
Loosing time Mogwa_ Slackware 20 01-30-2005 08:38 AM
loosing connectivity alaios Linux - Networking 1 11-08-2004 10:01 AM
loosing hope Synth218 Linux - Newbie 11 05-26-2003 11:56 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

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

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