I’m running SUSE 11.0 on a WMP54GS. Everything works great, but I get a 1 second lag in games every 20-30 seconds or so I think. Is there any way of stopping zero conf from doing this? I am using the default software for networking btw. I mean my ping is perfect, it’s just that 1 second of lag every now and then, without fail.
Thanks!
Tkk32 wrote:
> I’m running SUSE 11.0 on a WMP54GS. Everything works great, but I get a
> 1 second lag in games every 20-30 seconds or so I think. Is there any
> way of stopping zero conf from doing this? I am using the default
> software for networking btw. I mean my ping is perfect, it’s just that 1
> second of lag every now and then, without fail.
Zero conf is a Windows concept that has nothing to do with your delay.
Open a terminal and run the command ‘dmesg’ to see if anything is being logged
when the delays occur. If you don’t see any such information, then run the
command ‘top’. When you get the delay, see if some process is grabbing the CPU.
Larry
Thanks, guess I didn’t know much about zero conf. 
Here are a few of what I think are errors:
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=260 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=240
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=374 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=354
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=374 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=354
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=374 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=354
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=344 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=324
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=386 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=366
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=344 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=324
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=01:00:5e:00:00:01:00:18:39:a2:7f:f0:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:1c:10:60:ab:fa:00:18:39:a2:7f:f0:08:00 SRC=192.168.1.1 DST=192.168.1.100 LEN=413 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=2053 DPT=1900 LEN=393
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:1c:10:60:ab:fa:00:18:39:a2:7f:f0:08:00 SRC=192.168.1.1 DST=192.168.1.100 LEN=413 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=2053 DPT=1900 LEN=393
SFW2-INext-ACC-TCP IN=wlan0 OUT= MAC=00:1c:10:60:ab:fa:00:18:39:a2:7f:f0:08:00 SRC=85.17.40.166 DST=192.168.1.100 LEN=52 TOS=0x00 PREC=0x00 TTL=45 ID=60519 DF PROTO=TCP SPT=35041 DPT=10001 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40101040201030308)
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=01:00:5e:00:00:01:00:18:39:a2:7f:f0:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=01:00:5e:7f:ff:fa:00:18:39:a2:7f:f0:08:00 SRC=192.168.1.1 DST=239.255.255.250 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF OPT (94040000) PROTO=2
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=01:00:5e:00:00:01:00:18:39:a2:7f:f0:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
“SFW2-INext-DROP-DEFLT” surely can’t be a good thing.
Edit: This is without even starting the game. It’s just generally browsing the web for 5~ mins.
More relevant info, can’t seem to edit my last post.
martian source 192.168.1.100 from 80.239.179.19, on dev wlan0
ll header: 00:1c:10:60:ab:fa:00:18:39:a2:7f:f0:08:00
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=374 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=354
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=260 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=240
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=374 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=354
martian source 192.168.1.100 from 80.239.179.19, on dev wlan0
ll header: 00:1c:10:60:ab:fa:00:18:39:a2:7f:f0:08:00
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=374 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=354
martian source 192.168.1.100 from 80.239.179.19, on dev wlan0
ll header: 00:1c:10:60:ab:fa:00:18:39:a2:7f:f0:08:00
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=01:00:5e:00:00:01:00:18:39:a2:7f:f0:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
This is in WoW.
Tkk32 wrote:
> More relevant info, can’t seem to edit my last post.
>
> Code:
> --------------------
>
> martian source 192.168.1.100 from 80.239.179.19, on dev wlan0
> ll header: 00:1c:10:60:ab:fa:00:18:39:a2:7f:f0:08:00
> SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
> SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=374 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=354
> SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=260 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=240
> SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=374 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=354
> martian source 192.168.1.100 from 80.239.179.19, on dev wlan0
> ll header: 00:1c:10:60:ab:fa:00:18:39:a2:7f:f0:08:00
> SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=374 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=354
> martian source 192.168.1.100 from 80.239.179.19, on dev wlan0
> ll header: 00:1c:10:60:ab:fa:00:18:39:a2:7f:f0:08:00
> SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
> SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
> SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=01:00:5e:00:00:01:00:18:39:a2:7f:f0:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
> SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
> --------------------
Those are firewall messages concerning dropped packets. I leave it an an
exercise for the reader to figure out what they mean, but in general “not to worry”.
Larry
Thanks.
Any pointers on what I should do next? “top” didn’t help me identify the problem.
Tkk32 wrote:
> Thanks.
>
> Any pointers on what I should do next? “top” didn’t help me identify
> the problem.
The other cause of network delays is a IPV6 DNS timeout. If you don’t need IPV6
(If you don’t know what it is, then you don’t need it.), get rid of it. With
YaST, select “Network Devices”, “Network Settings”, choose the “Global Options”
tab, and uncheck “Enable IPV6”.
Larry
I had already done that, read it in a thread in Google, didn’t help.
I think I’ve identified the problem:
--- www.l.google.com ping statistics ---
137 packets transmitted, 131 received, 4% packet loss, time 136539ms
rtt min/avg/max/mdev = 39.838/42.577/75.403/3.619 ms
4% packet loss!
Oh dear. Any ideas? Using a fairly new Linksys router and WMP54GS NIC with proper native drivers.
Tkk32 wrote:
> 4% packet loss!
> Oh dear. Any ideas? Using a fairly new Linksys router and WMP54GS NIC
> with proper native drivers.
That loss rate is high. The next step is to isolate the problem.
Use the command
sudo traceroute www.google.com
You will see output that looks like the following:
traceroute to www.google.com (74.125.95.104), 30 hops max, 40 byte packets
1 router (192.168.1.1) 0.826 ms 0.451 ms 0.481 ms
…
13 iw-in-f104.google.com (74.125.95.104) 38.932 ms 43.007 ms 41.559 ms
For each of the steps, locate the IP number and ping each in turn with a command
like
ping -c 100 xxx.yyy.zzz.www
Keep going until you find the hop with the errors. If it is to your router (the
first hop), then it is your problem. Any further along the chain, it is your
ISP. In any case, report back. I’m intrigued by this one.
Larry
--- 192.168.1.1 ping statistics ---
100 packets transmitted, 99 received, 1% packet loss, time 99424ms
rtt min/avg/max/mdev = 1.165/5.244/393.850/39.255 ms
Looks like it’s my router. I’m guessing this one is going to be complicated. It worked fine when I used XP/Vista btw.
Tkk32 wrote:
> Code:
> --------------------
> — 192.168.1.1 ping statistics —
> 100 packets transmitted, 99 received, 1% packet loss, time 99424ms
> rtt min/avg/max/mdev = 1.165/5.244/393.850/39.255 ms
Something got in the way of networking - see the max rtt was 393 ms. It may be a
driver problem. I looked at the thread and saw what model you have, but not what
driver it is using.
I also checked the firewall output that you posted. Reverse DNS using nslookup
shows the “martian source” at 80.239.179.19 to be 80.239.179.19. The site with
IP of 224.0.0.251 is not found in any name tables. Try turning off the firewall
temporarily to see if that helps.
There still could be some process running at high priority. While you are
running ‘ping -s 1400 192.168.1.1’ in one window, run ‘top’ in another. Check
what shows up in the various samples.
Larry
Every massive ping time to my router counts as a packet loss. I’m starting to understand this a bit more.
Found this in dmesg:
b43-phy0 ERROR: PHY transmission error
I am using the newest install_b43xx_firmware driver. Updated it a few hours ago.
Whilst I’m doing this, I’ve noticed that knetworkmanager appears and disappears every now and then. Most of the time it’s not even in the list. But I’m guessing that’s normal since if I understand correctly it means it’s idle?
There is also one called NetworkManager that pops up every now and then.
8234 speng 20 0 140m 15m 10m S 1 0.4 0:04.56 knetworkmanager
Ping -c 1400 returned
--- 192.168.1.1 ping statistics ---
213 packets transmitted, 211 received, 0% packet loss, time 212865ms
rtt min/avg/max/mdev = 1.941/4.409/414.416/28.365 ms
That was when I was watching it.
Tkk32 wrote:
>
> Every massive ping time to my router counts as a packet loss. I’m
> starting to understand this a bit more.
>
> Found this in dmesg:
>
> Code:
> --------------------
> b43-phy0 ERROR: PHY transmission error
> --------------------
Do you get lots of these? We don’t know where they come from - it looks like a
firmware error, but they are so random. The latest drivers are better. You might
try the stuff from compat-wireless.
Larry
I think I’m already using them.
b43 - Linux Wireless
That’s what you mean right?
Anyways, that error only came up once, I think it was a one-off. I’m absolutely stumped, I really want to get this to work. Thanks for helping me so much btw.
I’ve updated knetworkmanager and NetworkManager, didn’t really help. 
This might explain what driver it’s using:
02:09.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
Subsystem: Linksys WMP54GS version 1.1 [Wireless-G PCI Adapter] 802.11g w/SpeedBooster
Flags: bus master, fast devsel, latency 32, IRQ 17
Memory at cfefc000 (32-bit, non-prefetchable) [size=8]
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
[/size]
Signal level=-54 dBm Noise level=-68 dBm
Is this bad? I used iwlist scan.
looks fine to me,probably around the 75% signal mark
Andy
I mean it’s doing it kind of in a pattern. Couldn’t it be that it’s searching for more SSID’s? And if it is, is there any way of stopping it?
I really want to get rid of the nasty 700ms network lag spikes, not acceptable in online games. Hmm.