BEFW11s4 and Mac IP packet loss

I have had a Linksys Wireless BEFW11s4 wireless router. It has worked fine with my Windows boxes. I just got an iMAC and with some minor problems I got it connected to the wireless network. I am using WEP and not broadcasting the SSID. I have the iMAC connected with full signal strength. I obtained a DHCP address from my DHCP server. However, when I try to ping items both on my wireless network and on the Internet I am having a lot of packet loss. Any ideas? I did not see a firmware upgrade for this model.........
Thanks!

Hi, connect one of your Pc to the router and log into the setup page of the router by http://192.168.1.1 the username is blank and the password is admin. You will see an advanced tab on the right hand side top.
Under the Advanced tab you will the wireless tab. On this screen lower the Beacon to 75 > Rts Threshold to 2392 and the Fragmentation Threshold to 2306.
If this still does not works then on the setup page under the Help tab you will find an option to upgrade the Firmware for the router. And you can find the firmware on the www.linksys.com/download site.

Similar Messages

Traceroute timeouts and lots of packet loss when a...

I host various site via the above, and since late last night and today, I am having connection timeout issues on all of them (but sites like bbc, bt etc are fine). I contacted them and performed a traceroute to my default site southee.co.uk which timed out. Below are the results:
traceroute to southee.co.uk (37.61.236.12), 64 hops max, 52 byte packets
1 bthomehub (192.168.1.254) 2.733 ms 2.414 ms 2.415 ms
2 esr5.manchester5.broadband.bt.net (217.47.67.144) 72.412 ms 29.705 ms 131.735 ms
3 217.47.67.13 (217.47.67.13) 31.390 ms 29.680 ms 103.936 ms
4 213.1.69.226 (213.1.69.226) 41.172 ms 32.700 ms 129.323 ms
5 31.55.165.103 (31.55.165.103) 30.791 ms 31.639 ms 130.306 ms
6 213.120.162.69 (213.120.162.69) 31.248 ms 59.138 ms 30.657 ms
7 31.55.165.109 (31.55.165.109) 32.159 ms 31.507 ms 31.513 ms
8 acc2-10gige-9-2-0.mr.21cn-ipp.bt.net (109.159.250.228) 31.499 ms 31.325 ms
acc2-10gige-0-2-0.mr.21cn-ipp.bt.net (109.159.250.194) 31.197 ms
9 core2-te0-12-0-1.ealing.ukcore.bt.net (109.159.250.147) 41.744 ms
core2-te0-13-0-0.ealing.ukcore.bt.net (109.159.250.139) 41.346 ms
core2-te0-5-0-1.ealing.ukcore.bt.net (109.159.250.145) 41.744 ms
10 peer1-xe3-3-1.telehouse.ukcore.bt.net (109.159.254.211) 39.527 ms
peer1-xe10-0-0.telehouse.ukcore.bt.net (109.159.254.122) 38.791 ms 38.910 ms
11 te2-3.sov-edge1.uk.timico.net (195.66.224.111) 54.032 ms 37.941 ms 38.642 ms
12 78-25-201-30.static.dsl.as8607.net (78.25.201.30) 45.830 ms 46.413 ms 42.448 ms
13 * * *
They then performed a traceroute from the server and got the following, again with timeouts and packet loss. See below:
1. 37.61.236.1 0.0% 10 0.5 0.7 0.4 2.9 0.8
2. ae0-2061.ndc-core1.uk.timico 0.0% 10 0.3 0.3 0.2 0.5 0.1
3. te2-3.sov-edge1.uk.timico.ne 0.0% 10 10.5 9.7 4.2 30.2 8.7
4. linx1.ukcore.bt.net 0.0% 10 4.1 4.3 4.1 5.9 0.6
5. host213-121-193-153.ukcore.b 0.0% 10 5.5 8.0 4.9 12.7 2.3
6. acc2-10GigE-4-3-1.mr.21cn-ip 0.0% 10 11.4 11.4 11.4 11.6 0.1
7. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
8. 31.55.165.108 0.0% 10 12.1 12.1 11.8 12.4 0.2
9. 213.120.162.68 0.0% 10 12.0 12.1 12.0 12.3 0.1
10. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
I've just spent a fustrating 15 minutes with Bt Support chat who just seemed want to pass me on to the BT Business team, so I thought I'd post here, for a more informed response.

Hi Jane, Thanks for the reply. I have now purchased an AEBS(n) to try to overcome this problem. The Apple site says it is compatible with all versions of Airport card so I thought it would solve the problem. My new problem is to be found here: http://discussions.apple.com/thread.jspa?threadID=1087292&tstart=0
However to answer your questions, The OS is 10.4.10 and I have run every updater I can find for all Macs concerned. hope this helps.

Slow and lots of packet loss

Hi Folks,
I have a wireless network set up at home with 3 macs on it. I have a G3 iMac (ruby) with an airport card (original), a Dual 1.25GHz G4 MDD also with an original airport card in it and finally a new MacBook Pro with the standard Airport Extreme 802.11N card and firmware.
Both the older machines connect and browse as one would expect them to and are lightning fast at browsing compared to the MBP. Is there some sort of mismatch with the cards?
The router is not Apple. It is a Billion 7402VGP (wireless and VoIP) with the latest firmware. It is not capable of 802.11N but is capable of 802.11g. I have tried the MBP with traceroute with 50% packet loss on wireless but none on ethernet. The G4 on wireless has no packet loss and is further away.
Any advice? What else could I tell you that would help you to help me?
MacBook Pro 15" 2.2Ghz Core 2 Duo Mac OS X (10.4.10) Wireless Card Firmware Version: 1.1.8.5

Hi Jane, Thanks for the reply. I have now purchased an AEBS(n) to try to overcome this problem. The Apple site says it is compatible with all versions of Airport card so I thought it would solve the problem. My new problem is to be found here: http://discussions.apple.com/thread.jspa?threadID=1087292&tstart=0
However to answer your questions, The OS is 10.4.10 and I have run every updater I can find for all Macs concerned. hope this helps.

Extremely slow internet and 20-50% packet loss

This has been happening for at least a week. I've been trying to play online games such as dota 2 where I have up to 50% packet loss at times. I also try to watch streams however it is usually constantly buffering every 5 seconds on any quality over 240p. I have tried restarting both my modem and router. I've also done a ping test to google which came back with:Pinging google.com [216.58.216.110] with 32 bytes o
Reply from 216.58.216.110: bytes=32 time=12ms TTL=5
Reply from 216.58.216.110: bytes=32 time=11ms TTL=5
Reply from 216.58.216.110: bytes=32 time=11ms TTL=5
Reply from 216.58.216.110: bytes=32 time=12ms TTL=5
Ping statistics for 216.58.216.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% l
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11msSometimes I will have no packet loss as shown but other times I will have 50%. It happens randomly. However streams will never work above 240p. I have tried speedtesting my internet when it is slow and it comes back the usual 20 Mbps down and 5 up. Anyone know whats going on or any tests I can try? It is extemely frustrating not knowing what to do

mattsmith927 wrote:
This has been happening for at least a week. I've been trying to play online games such as dota 2 where I have up to 50% packet loss at times. I also try to watch streams however it is usually constantly buffering every 5 seconds on any quality over 240p. I have tried restarting both my modem and router. I've also done a ping test to google which came back with:
Pinging google.com [216.58.216.110] with 32 bytes o
Reply from 216.58.216.110: bytes=32 time=12ms TTL=5
Reply from 216.58.216.110: bytes=32 time=11ms TTL=5
Reply from 216.58.216.110: bytes=32 time=11ms TTL=5
Reply from 216.58.216.110: bytes=32 time=12ms TTL=5
Ping statistics for 216.58.216.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% l
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms
Sometimes I will have no packet loss as shown but other times I will have 50%. It happens randomly. However streams will never work above 240p. I have tried speedtesting my internet when it is slow and it comes back the usual 20 Mbps down and 5 up.
Anyone know whats going on or any tests I can try? It is extemely frustrating not knowing what to do
I am sorry to hear about the trouble you are having with this. Has this happened recently? I was able to check the connection history and it does seem to be much better for the past week. If the issue comes back let me know, we might need to have a tech check this. -FC

Serious packet loss creating roaming network over Ethernet.

Comcast Business Gateway modem/router with static addressing provides one address for an externally accessible web/mail server on one of its four RJ45 LAN ports. The second RJ45 LAN port provides a second external address with NAT & DHCP to an internal private 10.1.10.x network connected to a 24-port Netgear gigabit switch. The Netgear is our home's primary switch, with most of the ports going to different jacks thrpughout our house. We have various PCs and Macs, a home server and other similar devices hardwired through the house jacks back to the Netgear receiving DHCP assignments from the Comcast router.
We've had (1) Airport Extreme base station (last generation, not the tall one) connected to the network, also receiving a DHCP IP address from the Comcast box. It's set to bridging mode, cabled from its WAN port by CAT5e to the Netgear switch and offering a Wi-Fi SSID with WPA2 PSK. NAT/DHCP etc is disabled. IPv6 is set to link-local only. No disks attached. Wireless channels set to Automatically.
At this point we have fairly smooth network performance, everything connects immediately (iOS devices, Android devices, utility boxes, computers, etc) and 0% apparent packet loss.
We have some weak Wi-Fi coverage on the far side of the house and I'd like to establish a roaming network, with a new Airport Express (most recent gen) plugged into a wall jack on that side of the house, cabled by Ehternet back to the Netgear, and set up identically. Same SSID and PSK. But when I activate this, I'm finding the network gets anywhere from 88% to 98% packet loss pinging the Comcast router and going outbound. And none of the iOS devices I tried could establish a functional network connection.
I tried replacing the Airport Express with another similar Airport Express, to same effect. I set the Airport Express to create a second SSID and that seemed to work OK, but then I had two distinct networks instead of a roaming network. I also tried disabling DHCP on the Comcast router and enabling it on the Airport Extreme Base Station, but still had the same packet loss. I also tried setting one, the other, and then both Airport boxes to static addressess bypassing the DHCP for their LAN-side connections (although still bridging) and still too much packet loss. No matter what I do, I can't seem to establish a functional Ethernet-connected roaming network with both Airport boxes.
Any ideas?

Thank you for the reply. The Netgear switch I'm using is a GS724T -- it has management features which I'm working through, but all the ports are set to auto-negotiate and the port the Airport Express is on is lit for 100baseT. I didn't see any way to set the MTU in the Airport Utility menus/buttons.
When I join the Airport Express to the network, it sets up the roaming network as intended. But then performance all across the switch goes downhill -- even when pinging from a PC attached to one of the switch ports to the Comcast router I get 90% packet loss or worse, so that nothing seems to get out or in until I disconnect the Airport Express.. It's that dramatic a difference. It doesn't make sense to me that a wireles roaming network across the two Airport boxes should kill performance through the router...

Different filesize after transmission with packet loss

HI!
I'm simulating packet loss on audio streams which are transferred over a network by using the JMF.
I'm doing the following:
read audio-WAVE file --> transcode into DVI for instance and sending --> generating packet loss --> transmitting over RTP to remote device --> receiving and saving in WAVE-file (linear format)
Now I'm wondering, why the size of the WAVE file on the receiver side is lesser than the size of the file of the sender side (about the amount of created packet loss in percent ). I think they have to be the same. If I play the received files in an audioplayer, the duration is logically the same, too. For each lost packet, JMF has to put a "silence" sample within the audio stream data. So this results in the same amount of samples and WAVE-file size.
Can someony explain me, why do the files have a different size ?
stefan

HI!
I'm simulating packet loss on audio streams which are transferred over a network by using the JMF.
I'm doing the following:
read audio-WAVE file --> transcode into DVI for instance and sending --> generating packet loss --> transmitting over RTP to remote device --> receiving and saving in WAVE-file (linear format)
Now I'm wondering, why the size of the WAVE file on the receiver side is lesser than the size of the file of the sender side (about the amount of created packet loss in percent ). I think they have to be the same. If I play the received files in an audioplayer, the duration is logically the same, too. For each lost packet, JMF has to put a "silence" sample within the audio stream data. So this results in the same amount of samples and WAVE-file size.
Can someony explain me, why do the files have a different size ?
stefan

Homehub & Packet Loss

I noticed over the past week my internet connection seemed glitchy, with pages occasionally not loading, frequent disconnects from programs/games and sporadic packet loss, which I tracked down to my LAN. Pinging the homehub, could be fine for a few minutes or interspersed with 'Request timed out', usually a disconnect from a game/program would coincide with a few of these.
My setup is a little odd but bear with me, but it's been working flawlessly for over a year, as a near free solution to the HH3s lack of roaming support.
FTTP Infinity
Homehub3b (192.168.1.254) connected to Fibre box, DHCP on, Wifi Off
Homehub2a (192.168.1.50) DCHP off, Wifi On
Homehub2b (192.168.1.55) DCHP off, Wifi On
The 3 hubs are connected to eachother over ethernet.
My desktop on HH3 gigE port was where i noticed the problem consistently around 7-8% packet loss to the router. When connected to the HH2a it gets 0% loss to the HH2a it is physically connected to but around 7-8% to the other two hubs. Strangely it started working fine again after being moved back to HH3 - 0% loss to anything, but problems on the HH2a.
My old spare desktop (for testing) gets the same results, 0% loss to all 3 hubs when connected to HH3, but when on the HH2a 0% and 7-8% packet loss to the other 2 hubs.
My second desktop on HH2b sent 3500 pings to each hub, 0% loss.
Laptops on wireless from the HH2a dont experience any packet loss like the wired connections to it get.
I've tried different cables, different ports, different operating systems, so im wondering if anyone has any ideas or information on similar problems with the homehubs.

The HH3/HH2a are near the fibre box and the HH2b is at the other end of the house on a long ethernet cable. It's quite a large house in an L shape with some solid brick internal walls and coverage with the HH3 seemed slightly worse than the old HH2b on its own. The HH3 doesn't allow devices to roam from APs to its wireless, something to do with them moving from it's ethernet ports to its wifi.
The internet connection is incredibly fast and we have a lot of devices attached, we had *several* pages listed on the HH3 before I reset it - desktops, laptops, smartphones, tablets, games consoles etc. The coverage is great too and were really spoilt, almost like those BT adverts
I've thought about replacing the HH3 before with a different router and wired AP, but I'm not sure how they're rated for current and future FTTP speeds and reviews are scarce. That said, the current setup mostly works great and is free.
Thanks

50% Packet loss

Hi,
This is my 1st time using these forums, I hope you can help me.
3 weeks ago I moved house, since then I have reported 2 faults on the line both due to very low IP profiles (0.14).
4 days ago the BT faults team (over the phone) managed to reset my profile and all has been great up until tonight.
My current profile seems fine, however when I ping bbc.co.uk I end up with lots of time outs and around 50% packet loss.
I did a pathping to bt.net and also ping tested Hop 3 and it seems to be here where my problem is (full results below)
Please advise on a course of action, I tried to can BT faults but was on hold for 2hrs and eventually gave up... as you would.
I am also from Western Scotland (Isle of lewis)
Please help
C:\Users\Xoranium>pathping bt.net
Tracing route to bt.net [193.113.211.125]
over a maximum of 30 hops:
0 Xoranium-PC.home [192.168.1.64]
1 BTHomeHub.home [192.168.1.254]
2 217.47.106.122
3 217.47.106.193
4 213.1.69.166
5 31.55.165.102
6 31.55.165.43
7 31.55.165.107
8 * acc1-10GigE-9-2-0.mr.21cn-ipp.bt.net [109.159.250.100]
9 core1-te0-14-0-3.ealing.ukcore.bt.net [109.159.250.5]
10 core1-pos1-0.birmingham.ukcore.bt.net [62.172.103.81]
11 iar1-gig5-4.birmingham.ukcore.bt.net [62.6.196.94]
12 62.172.57.218
13 * * *
Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Xoranium-PC.home [192.168.1.64]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% BTHomeHub.home [192.168.1.254]
0/ 100 = 0% |
2 42ms 0/ 100 = 0% 0/ 100 = 0% 217.47.106.122
20/ 100 = 20% |
3 --- 100/ 100 =100% 80/ 100 = 80% 217.47.106.193
0/ 100 = 0% |
4 54ms 26/ 100 = 26% 6/ 100 = 6% 213.1.69.166
0/ 100 = 0% |
5 54ms 23/ 100 = 23% 3/ 100 = 3% 31.55.165.102
0/ 100 = 0% |
6 --- 100/ 100 =100% 80/ 100 = 80% 31.55.165.43
0/ 100 = 0% |
7 54ms 26/ 100 = 26% 6/ 100 = 6% 31.55.165.107
0/ 100 = 0% |
8 64ms 25/ 100 = 25% 5/ 100 = 5% acc1-10GigE-9-2-0.mr.21cn-ipp.bt.net [109.159.250.100]
0/ 100 = 0% |
9 62ms 20/ 100 = 20% 0/ 100 = 0% core1-te0-14-0-3.ealing.ukcore.bt.net [109.159.250.5]
6/ 100 = 6% |
10 64ms 32/ 100 = 32% 6/ 100 = 6% core1-pos1-0.birmingham.ukcore.bt.net [62.172.103.81]
0/ 100 = 0% |
11 72ms 26/ 100 = 26% 0/ 100 = 0% iar1-gig5-4.birmingham.ukcore.bt.net [62.6.196.94]
8/ 100 = 8% |
12 67ms 34/ 100 = 34% 0/ 100 = 0% 62.172.57.218
Trace complete.
Solved!
Go to Solution.

if you try this link you will see there were problems last night in western Scotland https://www.bt.com/consumerFaultTracking/public/faults/tracking.do?pageId=31
If you want to say thanks for a helpful answer,please click on the Ratings star on the left-hand side If the reply answers your question then please mark as ’Mark as Accepted Solution’

TMS reporting - Network Packet Loss

Hi everyone,
I am trying to see packet loss reports in TMS but there is no info there.
My network is : VCS 7.0.2 with movi, c20 and ex60 registered (SIP) to it and a TMS 13.1.2.
The vcs is a starter pack and the TMS is the demo version. I first registered the endpoint to the vcs and then added the TMS to the network. I the added the endpoints and vcs to TMS. In TMS I see the endpoints and info about them, but unfortunatelly no info in the packet loss report. I made a call between movi and c20 with packet loss but no info was shown in the report.
I am very new to TMS and I wonder if there is something I should do in order to make the endpoints send packet loss info to TMS.
I sshed to the endpoints and I can see the info about packet loss and jitter through the api.
The network described above is my test network on which I can do prety much everything on. I also have the same problem (this time with EX60 endpoints, VCS Control and TMS) on a customer network and on that network I really need to get this working.
Any help would be much appreciated. Form what I read the endpoints should sent this info through HTTP to TMS. Am I right?
Thank you for your help.

Hi Magnus,
Thank you for your reply. I checked the logs and I get some info over there. I have attached the log.
Do you know what doc should I check to see if Ex60 is supported?
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/8/2012 3:58:51 AM
Disconnected
Call id: 3 Port id: 1;
Remote Number: sip:[email protected] Remote Name: 1853;
Direction: Outgoing CallProtocol: SIP;
Bandwidth: 6000 kbps Encryption Mode: Aes128;
Duration: 00:13:33; Cause Code: Normal call clearing
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/8/2012 3:45:19 AM
Connected
Call id: 3 Port id: 1;
Remote Number: sip:[email protected] Remote Name: ;
Direction: Outgoing CallProtocol: SIP;
Bandwidth: 6000 kbps Encryption Mode: Off;
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/7/2012 6:43:15 AM
Disconnected
Call id: 2 Port id: 1;
Remote Number: sip:[email protected] Remote Name: 1853;
Direction: Outgoing CallProtocol: SIP;
Bandwidth: 6000 kbps Encryption Mode: Aes128;
Duration: 00:14:57; Cause Code: CauseCode_Unknown
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/7/2012 6:28:19 AM
Connected
Call id: 2 Port id: 1;
Remote Number: sip:[email protected] Remote Name: ;
Direction: Outgoing CallProtocol: SIP;
Bandwidth: 6000 kbps Encryption Mode: Off;
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/7/2012 6:28:07 AM
Got Response
Got Network Response - TMS will now monitor   the system.;
System: [email protected] -   10.1.x.y ;
System Status: No response;
System Type: TANDBERG C-series   Endpoint;
Software: s52000 TC5.1.0.280662;
Hardware: F1AN19D00469 - ;
System Contact;
No Contact ();
Mobile: ;
Office: ;
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/7/2012 6:28:07 AM
Got Response
Got Network Response - TMS will now monitor   the system.;
System: [email protected] -   10.1.x.y ;
System Status: Idle;
System Type: TANDBERG C-series   Endpoint;
Software: s52000 TC5.1.0.280662;
Hardware: F1AN19D00469 - ;
System Contact;
No Contact ();
Mobile: ;
Office: ;
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/7/2012 6:28:06 AM
Got Response
Got Network Response - TMS will now monitor   the system.;
System: [email protected] -   10.1.x.y ;
System Status: No response;
System Type: TANDBERG C-series   Endpoint;
Software: s52000 TC5.1.0.280662;
Hardware: F1AN19D00469 - ;
System Contact;
No Contact ();
Mobile: ;
Office: ;

Strange packet loss issue

Hi all,
I am having a strange issue with my macbookpro recently. Here is the situation.
I have the TP-LINK wireless router both at home and work. IP address of this unit is 192.168.3.1 at home.
Recently i noticed a very high level of packet loss (60-70%) from my macbook pro when i pinged the default GW wireless router. I first thought its a wireless issue and tried debuging the issue from that end. I used my brother's macbook and he wasnt having this packet loss when i pinged from his terminal.
I then very randomly connected to my remote VPN server and noticed that the packetloss has disappeared when the VPN is connected and ping a remote IP such as 8.8.8.8.
Now i have two terminals running, one with a normal ping to 8.8.8.8 which goes via VPN and has 0% packet loss. Another terminal running a ping via interface en1 outside of the VPN interface using "ping -S 192.168.3.102 192.168.3.1" and this terminal is showing the same 60% packet loss.
Also strangely, this issue is only noticed at home router and not at work. At work the normal connection without VPN works fine.
I am at loss for ideas what could be causing this issue all of the sudden when the same settings were fine for over a year.
Any ideas?
Thanks

No solutions yet... I doubt this is a hardware matter as the packet loss goes away almost instantly when i switch on the VPN or simply move to other networks... The strangest thing is the VPN connection that solves the packet loss.. One thinks if VPN is overlaying on en1 to make its connection, how come the packetloss ceases to exist once there is a peer2peer connecton active to the same interface with the packet loss issue. Very strange indeed.
I thought also this could only be a ICMP issue (ping protocol) however ever the browsing slows down when im normally connected to this network.
In some awkward way im happy someone else is reporting this as I thought this is a weird enough problem for no one to comment on for yearly 10 days...
Im going to run a tcpdump to see if there is anything strange moving abount on my interfaces whilst there is a packet loss... will inform if any interesting results appeared...

Linksys WRT54GSV4 causing packet loss? Wired or Wireless.

Hi. I have been having trouble for months with my connection having packet loss. Up until yesterday my results from www.pingtest.net were between 2%-6% packet loss. Generally at 5% packet loss. A technician came out yesterday and bypassed my DSL modem and ran that test and got 0% packet loss every single time he ran it. So I bought a new Westell DSL modem off him to replace my Speadstream 4100 and away he went.
Now, when I hook up my Linksys WRT54GSV4 router to the Westell 6100 DSL modem, I get between 0%-1% packet loss. It's never higher than 1% but usually is 1%. This happens on my wireless laptops as well as PC's wired directly into the router. The main reason this packet loss was affecting me in the first place was Xbox Live gaming. Gears of War 2 kept thinking I was cheating, and it was host banning me. Last night I got host and did not get host banned but that doesn't mean it won't ban me in the future for the minimal packet loss.
Any suggestions on why the router could be causing this packet loss when the Linksys router is invovled? With a PC directly connected to the DSL modem I get 0% packet loss on that ping test every single time.
Internet Service: AT&T DSL (6.0 Mbps)
DSL Modem: Westell 6100
Router: Linksys WRT54GSV4
Solved!
Go to Solution.

Try reducing the MTU value to 1365 and uncheck Block Anonymous Internet Requests under Security tab on the router's GUI...and check if it makes any difference.
If the above steps doesn't work then,try to upgrade/reflash the router's firmware,reset the router and reconfigure it from the scratch...Download the firmware for your router and save it on the desktop.Now,On the Linksys GUI,click on Administrator tab to upgrade the firmware.

Consistent packet loss just a few hops into Verizon's network

I have had consistent packet loss just a few hops into Verizon's network for some time. I have tried the normal things like rebooting routers and releasing my ip address but none of that helps. Most routes do not have an issue, but there is one particular service in Verizon's network which I have issues with, and it happens to be the server that Verizon routes me through when I am gaming online.
The server is : G0-3-3-6.RCMDVA-LCR-22.verizon-gni.net (130.81.191.80) and I average around 50% packet loss each night. It is just the second hop into my route:
1) My Router Internal IP
2) L100.RCMDVA-VFTTP-16.verizon-gni.net (98.117.88.1) with a ping of 9 and 0 packet loss
3) G0-3-3-6.RCMDVA-LCR-22.verizon-gni.net (130.81.191.80) with a ping of 15 and 50-80% packet loss.
How can I get Verizon to stop routing me through this troublesome server? If I look at the route to goggle.com for example, I don't go through that server and there is no packet loss at all.

mrballcb wrote:
Since it's a congested link, you also should be aware that ICMP (what ping and traceroute use) become nearly useless for determining packet loss. A router backplane assigns a grade to every packet that wants to cross from one network connection to another, and ICMP typically is assigned low grade/value. So when a router is congested and needing to drop packets, ICMP is one of the first ones to get dropped. Less than 1% of your TCP traffic may be having problems, but ICMP failure might be greater than 50%. Find a traceroute program that can use TCP to do the traceroute for more accurate results. I'm not a Windows guy, so I have no clue what programs you have which can do this.
On my Linux/Unix computer, I use tcptraceroute
On a Windows computer, you need to download and install tracetcp.
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

Bouts of packet loss and complete loss of connection

Ok forum, I give up! I need your help.
I have an E1200 and am time out and packet loss issues. The internet connection is fine for 30 seconds to five minuets and then everything times out for 15-20 seconds. Although it’s only a minor incontinence to web browsing, it makes playing games and watching videos a nightmare. “Lost connection to server error.” and the like…
This is what I have done to remedy the problem.
I upgraded to a new router, the e1200 I am currently using, from my Tenda 10/100 N. The problems where the same that I am experience currently and the reason I bought it in the firs place.
When I directly connect to the cable modem, I have no issues and everything is fine.
I have run a trace route and the second hop, (the router to the modem) is the choke point.
I have cloned the MAC address
I have updated the firmware and hard reset
I have throttled my MTU to automatic, 1500, and 1472. None making any difference.
I have disabled NAT and all that does is kill my internet connection
I have disabled all firewalls router and windows, no change.
I replaced the physical wire from the router to the modem.
I have disconnected all devices except one computer, and no difference.
I ran a DNS trace and I have… non routable local internet address 192.168.1.1
DNS-cac-lb-01.rr.com and DNS-cac-lb-02.rr.com
I am using windows 7 and my ISP is time Warner so-cal. Help me obiwan, you’re my only hope.

Sorry friend. I have not had the gaul to load the 1.0 firmware. I am 99% sure I have the 2.0 hardware. I did however unplug my modem for an hour and then try and reconnect. The result was a lossless environment for fifteen to twenty minuets (a long time for me.). But, I am right back still having the same problem. A friend gave me a new netgear router, I am going to try that and I am going to go to Timewarner and have them replace my modem just to make sure there is nothing wrong with the surfboard. I will report back with my findings.

Packet loss when flood pinging a Mac

I had some trouble transferring large files between my iMac and my MBP the other day and so started a bit of investigation. Mistake really - here is what I found:
All mac targets are running up-to-date Leopard and use intel processors.
The home network has a linksys wireless router - all devices connected by copper.
flood ping tests with command 'sudo ping -f <target>:
from iMac to MBP shows 30% packet loss
from MBP tp iMac shows 33% packet loss
from iMac to windows laptop 0% packet loss
from iMac to linksys router 0% packet loss
from iMac to Freecom NAS box 0% packet loss
from MBP to windows laptop 0% packet loss
from MBP to linksys router 0% packet loss
from MBP to Freecom NAS box 0% packet loss
I took the macbook to work and picked targets on another site, several busy switch hops away.
from MBP to windows desktop 0% packet loss
from MBP to another iMac 26% packet loss
from MBP to mac mini 28% packet loss
from MBP to linux server 0% packet loss
from linux server to MBP 32% packet loss
The firewall is off on all the targets.
Seem clear enough - Mac machines can't handle high ping loads. It is no good telling me they don't have to. If they can answer a ping at all, they should be able to handle the load. It is a perfectly acceptable way of stress testing the link. File transfers are generally not an issue but now I want to know...
Why can't the macs handle the ping floods?
Is this indicative of any other weakness in the IP stack?
Pete

I had a suspicion of packet loss on my internet connection but could not be certain it was the ISP at fault. The fact that I had been having trouble transferring large files between my machines led me to look for possible local problems.
Network fault finding should always examine the hardware first so I wanted to see if there was anything about the cabling or the router which might be causing packet loss.
Actually copying data about the network is a pretty poor way to test things because you have several additional layer of complexity that can colour the results.
When I had narrowed down the flood ping packet loss to the macs, I went hunting on the 'net. There were plenty of people who were reporting various kinds of packet loss. Enough of them that I wondered if there was something more to it. Some of them were talking about similar symptoms to mine. The respondents usually answered a question other than the one asked so I thought I would put up some tests and see if there was actually a problem anywhere.
Now I know it is a 'feature' rather than a fault, I can work around it.
Thanks anyway
Pete

VoIP Phones - Testing Latency, Jitter, and Packet Loss

I am having big problems with my VoIP phone connection and I'll try to lay it out clearly here.
The main telephone system resides at Location A (static IP address - see below - xxx.xxx.206.19), which has a network connection of 50MB down/20MB up (i.e., very fast). The VoIP phone configured for that system resides at Location B, which has a network connection of 10MB down/1MB up (i.e., also fast, or at least fast enough "on paper" for a quality VoIP connection). The LAN at Location A uses an Airport Extreme router, which does not have QOS or EF capability. The LAN at Location B uses a D-Link DIR-655 router which does have QOS that is configured properly to direct all traffic to the VoIP phone's IP address.
The VoIP phone at Location B is having intermittent call quality problems with skipping of words, hollowing out noises, jittery conversations, etc. All the inquiries I've made to the ISPs and phone system manufacturer (ESI) suggest that my base Internet speeds are not the problem.
I'm told, instead, that the problem might be latency, jitter, or packet loss between Location A and Location B. This leads to several questions:
(1)     Is there any Mac software that can test latency, jitter, and packet loss? I've looked at Network Utility and it seems to only measure a few things.
(2)     Does anyone see anything in the following Traceroute and Ping results (done twice from Location B to Location A) that looks problematic to VoIP quality?:
Traceroute:
First run: Traceroute has started…
traceroute to xxx.xxx.206.19 (xxx.xxx.206.19), 64 hops max, 72 byte packets
1 alfirving (192.168.0.1) 0.569 ms 0.363 ms 0.302 ms
2 10.72.28.1 (10.72.28.1) 27.567 ms 18.161 ms 22.288 ms
3 70.125.216.150 (70.125.216.150) 9.841 ms 10.346 ms 9.497 ms
4 24.164.209.116 (24.164.209.116) 11.042 ms 8.298 ms 9.433 ms
5 70.125.216.108 (70.125.216.108) 21.068 ms 20.657 ms 12.045 ms
6 te0-8-0-2.dllatxl3-cr01.texas.rr.com (72.179.205.48) 11.154 ms 11.540 ms 24.495 ms
7 107.14.17.136 (107.14.17.136) 11.994 ms 14.217 ms 15.816 ms
8 ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209) 14.566 ms 32.670 ms 15.947 ms
9 ix-0-3-2-0.tcore2.dt8-dallas.as6453.net (209.58.47.105) 11.647 ms 12.260 ms 12.386 ms
10 if-2-2.tcore1.dt8-dallas.as6453.net (66.110.56.5) 10.023 ms 12.285 ms 12.338 ms
11 209.58.47.74 (209.58.47.74) 17.641 ms 16.741 ms 16.372 ms
12 0.ae2.xl3.dfw7.alter.net (152.63.97.57) 11.584 ms 12.315 ms 12.890 ms
13 0.so-6-1-0.dfw01-bb-rtr1.verizon-gni.net (152.63.1.90) 13.812 ms
    0.ge-3-0-0.dfw01-bb-rtr1.verizon-gni.net (152.63.1.17) 18.831 ms
    130.81.23.164 (130.81.23.164) 14.189 ms
14 p14-0-0.dllstx-lcr-05.verizon-gni.net (130.81.27.40) 14.561 ms 13.621 ms 15.544 ms
15 * * *
16 static-xxx.xxx.206.19.dllstx.fios.verizon.net (xxx.xxx.206.19) 23.125 ms 24.136 ms 22.411 ms
Second run: Traceroute has started…
traceroute to xxx.xxx.206.19 (xxx.xxx.206.19), 64 hops max, 72 byte packets
1 alfirving (192.168.0.1) 0.603 ms 0.420 ms 0.324 ms
2 10.72.28.1 (10.72.28.1) 40.494 ms 26.625 ms 14.152 ms
3 70.125.216.150 (70.125.216.150) 9.431 ms 9.660 ms 9.018 ms
4 24.164.209.116 (24.164.209.116) 16.293 ms 12.339 ms 19.252 ms
5 70.125.216.108 (70.125.216.108) 15.801 ms 11.438 ms 12.068 ms
6 te0-8-0-2.dllatxl3-cr01.texas.rr.com (72.179.205.48) 23.221 ms 30.459 ms 17.519 ms
7 107.14.17.136 (107.14.17.136) 14.611 ms 15.696 ms 15.775 ms
8 ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209) 17.643 ms 14.812 ms 16.294 ms
9 ix-0-3-2-0.tcore2.dt8-dallas.as6453.net (209.58.47.105) 11.169 ms 12.374 ms 9.849 ms
10 if-2-2.tcore1.dt8-dallas.as6453.net (66.110.56.5) 16.453 ms 12.168 ms 12.384 ms
11 209.58.47.74 (209.58.47.74) 18.015 ms 14.867 ms 16.432 ms
12 0.ae2.xl3.dfw7.alter.net (152.63.97.57) 11.471 ms 11.993 ms 12.395 ms
13 0.ge-6-3-0.dfw01-bb-rtr1.verizon-gni.net (152.63.96.42) 14.077 ms 29.153 ms
    0.ge-3-0-0.dfw01-bb-rtr1.verizon-gni.net (152.63.1.17) 17.962 ms
14 p14-0-0.dllstx-lcr-05.verizon-gni.net (130.81.27.40) 14.629 ms 12.297 ms 12.839 ms
15 * * *
16 static-xxx.xxx.206.19.dllstx.fios.verizon.net (xxx.xxx.206.19) 24.976 ms 22.170 ms 22.376 ms
Ping:
First Run: Ping has started…
PING xxx.xxx.206.19 (xxx.xxx.206.19): 56 data bytes
64 bytes from xxx.xxx.206.19: icmp_seq=0 ttl=242 time=22.814 ms
64 bytes from xxx.xxx.206.19: icmp_seq=1 ttl=242 time=24.621 ms
64 bytes from xxx.xxx.206.19: icmp_seq=2 ttl=242 time=24.711 ms
64 bytes from xxx.xxx.206.19: icmp_seq=3 ttl=242 time=24.109 ms
64 bytes from xxx.xxx.206.19: icmp_seq=4 ttl=242 time=23.336 ms
64 bytes from xxx.xxx.206.19: icmp_seq=5 ttl=242 time=25.644 ms
64 bytes from xxx.xxx.206.19: icmp_seq=6 ttl=242 time=27.755 ms
64 bytes from xxx.xxx.206.19: icmp_seq=7 ttl=242 time=25.135 ms
64 bytes from xxx.xxx.206.19: icmp_seq=8 ttl=242 time=22.443 ms
64 bytes from xxx.xxx.206.19: icmp_seq=9 ttl=242 time=24.635 ms
--- xxx.xxx.206.19 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 22.443/24.520/27.755/1.448 ms
Second Run: Ping has started…
PING xxx.xxx.206.19 (xxx.xxx.206.19): 56 data bytes
64 bytes from xxx.xxx.206.19: icmp_seq=0 ttl=242 time=27.183 ms
64 bytes from xxx.xxx.206.19: icmp_seq=1 ttl=242 time=24.629 ms
64 bytes from xxx.xxx.206.19: icmp_seq=2 ttl=242 time=22.511 ms
64 bytes from xxx.xxx.206.19: icmp_seq=3 ttl=242 time=39.620 ms
64 bytes from xxx.xxx.206.19: icmp_seq=4 ttl=242 time=26.722 ms
64 bytes from xxx.xxx.206.19: icmp_seq=5 ttl=242 time=23.183 ms
64 bytes from xxx.xxx.206.19: icmp_seq=6 ttl=242 time=25.171 ms
64 bytes from xxx.xxx.206.19: icmp_seq=7 ttl=242 time=24.412 ms
64 bytes from xxx.xxx.206.19: icmp_seq=8 ttl=242 time=23.837 ms
64 bytes from xxx.xxx.206.19: icmp_seq=9 ttl=242 time=23.785 ms
--- xxx.xxx.206.19 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 22.511/26.105/39.620/4.713 ms
(3) Any other ideas on what my call quality problem might be, or how I can tweak it? For example, would putting a DIR-655 router at Location A and enabling QOS really make a difference?
Thanks to everyone, and I hope this is not too long or difficult to understand.

Hey thanks for your reply Yeah im only getting 1 ro sometimes 2 bars reception so hopefully the antenna will beef things up but I think it is what it is perhaps.

BEFW11s4 and Mac IP packet loss

Similar Messages

Maybe you are looking for