Packet loss with 1000BaseT since 10.5

Hi there!
Rarely, I connect my MacBook to my PC using an Ethernet Cable. As my PC has two ethernet interfaces, I use the 100mbit one for internet and the gigabit one to connect my macbook.
To make a long story short: last time I connected it, everything worked fine. At that time 10.4 was still installed on the MacBook. Yesterday I encountered packet loss of about 30% and a net transfer rate below AirPort. For testing purposes, I switched back to 100BaseTX and behold! Everything was back to normal (on 100 mbit, though).
The only thing I've changed was the OS installed on my MacBook (installed new and "fresh"), the cable used and software on my PC (like ethernet drivers and so on) are still the same.
Are there any known issues with the ethernet drivers of 10.5(.1)?
Bye
Steffen

Here is what I did to solve the problem:
1. Open iCal and export every calendar to desktop.
2. Delete every calendar in iCal including the birthday calendar and all subscriptions.
3. Open Finder and go to User/Library/Calendars and delete everything in the folder.
4. Go to User/Library/Application Support/iCal and delete this whole folder.
5. Go to User/Library/Application Support/iSync and delete everything in this folder.
6. Open iCal and import each of your calendars one at a time. Re-subscribe to subscription calendars.
7. Open iSync and hopefully it works for you because it worked for me.

Similar Messages

  • E-51 Packet loss with Linksys WAP4400N Access Poin...

    I have two Nokia E-51 that connect fine with multiple Access Points but seem to have trouble with the Linksys WAP4400N device.
    The phones connect fine and are ping-able but experience random and heavy packet loss intermittently. Since I am using this WLAN for SIP services its almost impossible to have a SIP conversation using this setup.
    I have setup multiple other access points and they work fine with this phone. The linksys also works fine with other phones (Windows CE Imate, numerous laptops) so I am unable to figure out where the problem is.
    Anybody else with similar issues?

    This happened in two more ports during the following month. Again, resetting the port and applying the macro solved the issue. In the last month we haven't had any problems
    Well Tiago, you're in a dilemma.  Cisco recently announced the EoS for the 2960S.  This means that the 2960X cannot run a more stable IOS, like 12.2(55)SE9 or 15.0(2)SE4, but I do know is that there's a move within Cisco to significantly improve the performance of the 2960X IOS.  This means that the developers have "opened their doors" to any (violent) comments/reactions.  
    Contact your SE and, as Americans like to say, "let them have it".  All of it.  
    I know what I'm saying because some 2960X-related team has been listen to my complaint about the lack of performance of TDR for the 2960X.  The supporting documents about this topic were quickly knocked up by Cisco and move is underway.  If my issue is that small, your issue is bigger and will get more attention.

  • Intel 5100-5300 getting packet loss with a wrt 310n

    Hi All
    I have found a fix for this and it seems to work for me. Intel 5100 worked fine with a dlink but I always recieved packet loss with my wrt 310n
    http://www.intel.com/support/wireless/wlan/sb/cs-006205.htm
    Just though I would Hare it with the Community
    Regards
    Wall

    I have an ASUS UX32VD-DB71 which has the Intel Centrino 6235 wifi card. I've been having this laptop for more than 6 months and I've tried different solutions to fix the issue with Wireless-N but none of them were stable other than disabling N completely using 11n_disable=1
    I've tried different kernels all the way from 3.2 to the latest 3.7 series of kernels (both in the openSUSE tree as well as mainline) with no luck whasoever. I also tried installing the compat-drivers from 2013-01-23-1-u version onto my 3.6 kernel which provided the same results too. I see packet loss with N and the G speeds are just too slow. I have a workstation in my network and I can only transfer effectively at 1.5 MB /s max over G whereas an old laptop from 2007 which has an 1x1 MIMO antenna (again Intel though) can connect at 144 Mbps to my router and transfer files at least 3-4 times faster (if not more).
    It is totally unacceptable for Intel to not just fix this issue for Linux.
    Last edited by Tuxdude (2013-02-17 01:38:59)

  • Packet losses with Atheros AR2413 and ath5k

    Hi,
    i just switched to ath5k because madwifi got removed and i'm now facing massive packet losses. One can't really use the internet anymore. I haven't done any configuration, ath5k is not in MODULES and nothing is blacklisted.
    Previously i had ath5k blacklisted and happily used ath_pci.
    So, i don't know how to proceed. Should i file a bug report? Or did i just forgot to config something? dmesg looks clean. I really would like to have madwifi back...
    Regards

    Yggdrasil wrote:
    Hi,
    i just switched to ath5k because madwifi got removed and i'm now facing massive packet losses. One can't really use the internet anymore. I haven't done any configuration, ath5k is not in MODULES and nothing is blacklisted.
    Previously i had ath5k blacklisted and happily used ath_pci.
    So, i don't know how to proceed. Should i file a bug report? Or did i just forgot to config something? dmesg looks clean. I really would like to have madwifi back...
    Regards
    I also was using ath_pci, and had both ath9k and ath5k blacklisted.
    I had to un-blacklist them, and removed ath_pci off the modules.
    It seems to be using ath5k now.  I haven't noticed any packet loss though (but next time I get the laptop out - I'll do some double checking).
    Last edited by Kilzool (2011-06-11 22:24:57)

  • Home Hub 3.0 vs Home Hub 2.0 packet loss

    So I upgraded the BT package that our family is on today, and with it came the Home Hub 3.0. Happy right? Better wireless, less connection problems etc... No.
    For some reason, since upgrading, I get random moments of massive packet loss. Up to 50% packets are lost for periods of up to 5 minutes. I've tried resetting the router, tried turning it off for ten minutes etc but still get regular moments of packet loss.
    My internet is not interleaved at the moment so that could be a problem, however before switching to the 3.0 i never had any packet loss with non-interleaved internet (on the 2.0 homehub).
    Could anyone help me?!
    Thanks
    Solved!
    Go to Solution.

    ADSL Line Status
    Connection Information
    Line state:
    Connected
    Connection time:
    0 days, 03:12:19
    Downstream:
    7.813 Mbps
    Upstream:
    448 Kbps
    ADSL Settings
    VPI/VCI:
    0/38
    Type:
    PPPoA
    Modulation:
    G.992.1 Annex A
    Latency type:
    Fast
    Noise margin (Down/Up):
    9.1 dB / 24.0 dB
    Line attenuation (Down/Up):
    35.5 dB / 19.5 dB
    Output power (Down/Up):
    19.9 dBm / 12.1 dBm
    FEC Events (Down/Up):
    0 / 202
    CRC Events (Down/Up):
    91236 / 426
    Loss of Framing (Local/Remote):
    0 / 0
    Loss of Signal (Local/Remote):
    0 / 0
    Loss of Power (Local/Remote):
    0 / 0
    HEC Events (Down/Up):
    619777 / 655
    Error Seconds (Local/Remote):
    2173 / 506
    est1 comprises of Best Effort Test:  -provides background information.
    Download  Speed
    4095 Kbps
    0 Kbps
    7150 Kbps
    Max Achievable Speed
     Download speedachieved during the test was - 4095 Kbps
     For your connection, the acceptable range of speeds is 600-7150 Kbps.
     Additional Information:
     Your DSL Connection Rate :8000 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
     IP Profile for your line is - 4500 Kbps
    I did a quiet line test and it sounded quiet.
    Thanks for your answer, just hope someone can help me resolve it now

  • Packet loss / pausing when using 802.11N (Intel 6300)

    Hi,
    Previously, I had posted a thread involving the Intel 6250, and lack of detection of N WiFi on that card. Some time later, I bit the bullet and got an Intel 6300 card off eBay. After receiving it today, I popped it into my Thinkpad X220, and it worked.... sort of. I can definitely see wireless N support, and can associate with my 2.4 GHz mixed-mode B/G/N network at 130 Mbps, and my 5 GHz N-only router at around 243 - 270 Mbps. However, right off the bat, it seems the number of "Tx Excessive Retries" in iwconfig climb up to several thousand within ~ 15 - 20 minutes of connecting. Also right off the bat, pings are rather inconsistent (typically at least 2 ms greater than when the card is forced to work in G-only mode, and with pauses and spikes up to 800 - 2000 ms, and packet loss from 5 - 10%)
    From what I have gathered so far, there has been a bug in the iwlwifi kernel tree that affects N wireless users, and this bug has been around since around 2010 or even earlier. However, I was under the impression that some sort of fix has been merged into the mainline Kernel at this point (I'm on 3.5.3-1-ARCH BTW), and my symptoms are somewhat less aggressive than the ones others described (basic web browsing works reasonably well, though there is often noticeable lag in the response times, but anything latency/packet loss-sensitive will suffer in a major way.) Has anyone managed to get wireless N to actually work reasonably well on Arch (or for that matter, ANY linux distro)? As I understand it, the matter is one of relation to the kernel module itself, so distro-distro variations of userspace apps shouldn't be as much a factor anyway. I am using WICD for my network manager, and am happy to say that it does its job admirably well (assuming the card is set to G-only mode, but the connection itself is actually maintained quite stably even in N mode.)
    While I understand that the 11n_disable=1 "fix" allows most people to get on with their lives, I am rather alarmed that this is being considered a long-term solution. Many laptop owners (ThinkPad owners like myself for example) are essentially locked into Intel WiFi cards, unless we are willing to take an expensive risk and flash our BIOS to one that that doesn't have a "whitelist" of approved cards (something that can void the warranty or worse, brick a laptop.) All the while, Intel is still claiming Linux support for a card whose major capabilities are essentially neutered purely based on the OS a user chooses to run (yes, I do consider N to be a major capability, considering 300 Mbps N WiFi is basically old news, with many manufacturers coming out with full 450 Mbps routers. Also, chipsets like Atheros seem to have no problems with offering both performance and stability under Linux... my desktop rig using an Atheros card manages perfectly fine on a full-rate wireless-N network with essentially no packet loss or latency spikes.)
    Below is some information that might be useful:
    iwconfig (802.11g, ~ 1 hour after connection and running a few speedtests, browsing, ping testing):
    wlan0 IEEE 802.11abg ESSID:"dd-wrt"
    Mode:Managed Frequency:2.437 GHz Access Point: XXXXXX
    Bit Rate=54 Mb/s Tx-Power=15 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=69/70 Signal level=-41 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:359 Missed beacon:0
    iwconfig (802.11n, 5GHz after ~10 minutes browsing/ping testing):
    wlan0 IEEE 802.11abgn ESSID:"net2"
    Mode:Managed Frequency:5.745 GHz Access Point: XXXXXX
    Bit Rate=243 Mb/s Tx-Power=15 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=55/70 Signal level=-55 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:860 Invalid misc:50 Missed beacon:0
    iwconfig (802.11n, 2.4 GHz after connecting and running a speedtest):
    wlan0 IEEE 802.11abgn ESSID:"dd-wrt"
    Mode:Managed Frequency:2.437 GHz Access Point: XXXXXX
    Bit Rate=117 Mb/s Tx-Power=15 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=66/70 Signal level=-44 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:974 Invalid misc:59 Missed beacon:0
    dmesg | grep iwl :
    [12011.488089] iwlwifi: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
    [12011.488092] iwlwifi: Copyright(c) 2003-2012 Intel Corporation
    [12011.488269] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
    [12011.488271] iwlwifi 0000:03:00.0: pci_resource_base = ffffc900050f8000
    [12011.488273] iwlwifi 0000:03:00.0: HW Revision ID = 0x35
    [12011.488585] iwlwifi 0000:03:00.0: irq 50 for MSI/MSI-X
    [12011.491862] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532
    [12011.492112] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
    [12011.492114] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
    [12011.492116] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
    [12011.492117] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE enabled
    [12011.492119] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_P2P disabled
    [12011.492121] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
    [12011.492206] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12011.502925] iwlwifi 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
    [12011.502928] iwlwifi 0000:03:00.0: Device SKU: 0x1F0
    [12011.502930] iwlwifi 0000:03:00.0: Valid Tx ant: 0x7, Valid Rx ant: 0x7
    [12011.502946] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
    [12011.503105] ieee80211 phy8: Selected rate control algorithm 'iwl-agn-rs'
    [12011.503456] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12011.503661] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12011.745631] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12011.745868] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12073.651471] iwlwifi: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
    [12073.651474] iwlwifi: Copyright(c) 2003-2012 Intel Corporation
    [12073.651660] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
    [12073.651661] iwlwifi 0000:03:00.0: pci_resource_base = ffffc900050b8000
    [12073.651663] iwlwifi 0000:03:00.0: HW Revision ID = 0x35
    [12073.652241] iwlwifi 0000:03:00.0: irq 50 for MSI/MSI-X
    [12073.655662] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532
    [12073.655887] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
    [12073.655890] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
    [12073.655891] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
    [12073.655891] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE enabled
    [12073.655892] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_P2P disabled
    [12073.655894] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
    [12073.655975] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12073.666587] iwlwifi 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
    [12073.666593] iwlwifi 0000:03:00.0: Device SKU: 0x1F0
    [12073.666595] iwlwifi 0000:03:00.0: Valid Tx ant: 0x7, Valid Rx ant: 0x7
    [12073.666618] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
    [12073.667056] ieee80211 phy9: Selected rate control algorithm 'iwl-agn-rs'
    [12073.667456] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12073.667659] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12073.908411] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12073.908632] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12087.261869] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12087.262090] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12087.487757] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12087.488010] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12087.699574] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12087.699781] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12087.837322] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12087.837526] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12097.329577] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12097.329832] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12097.797748] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12097.797970] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12098.016220] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12098.016458] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12100.458762] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12100.459006] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12100.608769] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12100.609021] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12100.764093] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12100.764341] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12100.979029] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12100.979228] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12101.159987] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12101.160208] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    lshw | less :
    *-network
    description: Wireless interface
    product: Centrino Ultimate-N 6300
    vendor: Intel Corporation
    physical id: 0
    bus info: pci@0000:03:00.0
    logical name: wlan0
    version: 35
    serial: 00:24:d7:be:9e:74
    width: 64 bits
    clock: 33MHz
    capabilities: pm msi pciexpress bus_master cap_list ethernet phy
    sical wireless
    configuration: broadcast=yes driver=iwlwifi driverversion=3.5.3-
    1-ARCH firmware=9.221.4.1 build 25532 ip=192.168.1.145 latency=0 link=yes multic
    ast=yes wireless=IEEE 802.11abgn
    resources: irq:50 memory:f2500000-f2501fff
    Thanks,
    - A.G.

    I have an ASUS UX32VD-DB71 which has the Intel Centrino 6235 wifi card. I've been having this laptop for more than 6 months and I've tried different solutions to fix the issue with Wireless-N but none of them were stable other than disabling N completely using 11n_disable=1
    I've tried different kernels all the way from 3.2 to the latest 3.7 series of kernels (both in the openSUSE tree as well as mainline) with no luck whasoever. I also tried installing the compat-drivers from 2013-01-23-1-u version onto my 3.6 kernel which provided the same results too. I see packet loss with N and the G speeds are just too slow. I have a workstation in my network and I can only transfer effectively at 1.5 MB /s max over G whereas an old laptop from 2007 which has an 1x1 MIMO antenna (again Intel though) can connect at 144 Mbps to my router and transfer files at least 3-4 times faster (if not more).
    It is totally unacceptable for Intel to not just fix this issue for Linux.
    Last edited by Tuxdude (2013-02-17 01:38:59)

  • E4200 V2 Packet Loss?

    I seem to be having packet loss with the E4200V2 which is upgraded to the latest firmware as of today, 1/18/12
    The application is accessing a security DVR which uses a RTSP / RTP stream.  Of course this requires certian ports to be forwarded in order for this to work.  This works flawlessly with a WRT310N or a Cisco 871 Router so I know the port forwarding is correct.
    With the E4200V2 it works intermittently, I can replace EV4200V2 with either the Cisco 871 or the WRT310N and there are no issues.
    Can someone from support contact me to work through and resolve this issue?
    Thanks,
    Jeff

    HenrikGugstavsson wrote:
    I made the following video of the packet loss.  Note that when connected directly to the modem, I had no packet loss.  When connected to my old router, no packet loss.
    Cisco e4200 Packet Loss
    You can set MTU size to manual. Update the router's firmware if needed. If it's already updated, reset and reconfigure the router. Did you try these steps?

  • White noise, sort of packet loss when talking with...

    Hi,
    For some unknown reason when I talk with one specific person the call doesn't exactly drop out it sort of cuts the audio and gives me white noise (sort of like when you get packet loss when transferring files or gaming), I have 0 idea why it does it. Does it the reverse as well, but only for me and this person. Everyone else thats in the call doesn't get effected and its frustrating me.

    When in a call goto call > Technical info. This will show you various info about the call connection (and a lot of useless info aswell). Amongst the info is packet loss, and relays (if relays = more than 0 you are not directly connected).
    Being on the same Skype, version might help.

  • Help- WDS with Extreme-N & 2x Airport Express with ~ 40% packet loss

    So this problem is driving me crazy. I recently moved into a house that has enough metal in the walls (don't ask) to prevent me from using a single base station so I expanded my network as a WDS utilizing an Airport Extreme (mixed NGB mode) and two Airport Express (one as a relay and one as remote). The configuration appears to work normally some times but other times (especially evenings) I get a very high rate of dropped packets between the client notes (which are connected through the WDS-enabled Expresses) and the base station (using a simple ping 10.0.1.1 to check connectivity to the APBS-N). The problem manifests itself from a users' perspective as very long DNS lookups which causes slow page loads in a browser but it's very reproducible via ping.
    So far I've tried changing the channels on the network but I haven't seen a huge payoff there. iStumbler reports no additional networks on channel 2 which I'm using, there are some on channel 1, 5, and 13. I've also tried channels 7 and 11. We have no microwave in the house and our cordless phone (5.8ghz) never interrupted with our simpler Express-based network at our old house, n/m the fact that the phone is never in use when we have this problem.
    I don't seem to see the problem when I'm local to (in the same room as) the AEBS; it really seems to happen only when I'm on the WDS-enabled remote and/or relay.
    Other data points that may help are that the AEBS-N drops out of the Airport utility at the same time. Sometimes isn't gone for 30 seconds, other times for > 30 minutes. The other base stations continue to report "Green" in that they are not having any WDS problems. If I disconnect the remote node the relay will correctly reflect a status of yellow, so I know it somewhat works.
    It's an open network (no encryption, open SSID) so it's unlikely that there's an issue there.
    Clients include an Apple TV, iBook G4, MacBook, Tivo Series 3, Intel Mini and Dell Latitude D810. Because of the diversity of clients I don't think it's a driver or NIC adapter issue on any of the clients.
    Does anyone have any experience working in a similar environment? Suggestions on troubleshooting packet loss (or other performance issues) in a WDS network?
    Thanks,
    Mike

    Hello errorsupply. Welcome to the Apple Discussions!
    I suggest downloading a copy of iStumbler. Use iStumbler's Inspector feature (select Edit > Inspector from iStumbler's menu) to determine the Signal-to-Noise Ratio (SNR) at different points around your house, by performing a simple RF site survey. Within the Inspector, note the values for "signal" & "noise" at these locations. Start with your MacBook near the main base station, note the readings, and then, choose the locations where you have the relay and remote base stations.
    SNR is the signal level (in dBm) minus the noise level (in dBm). For example, a signal level of -53dBm measured near an access point and typical noise level of -90dBm yields a SNR of 37dB, a healthy value for wireless LANs.
    The SNR, as measured from the MacBook, decreases as the range to the base station increases because of applicable free space loss. Also an increase in RF interference from microwave ovens and cordless phones, which increases the noise level, also decreases SNR.
    SNR Guideline
    o 40dB+ SNR = Excellent signal
    o 25dB to 40dB SNR = Very good signal
    o 15dB to 25dB SNR = Low signal
    o 10dB to 15dB SNR = Very low signal
    o 5dB to 10dB SNR = No signal
    If the SNR is 20dB+ at each of these locations, then you should be getting reasonable performance from your AirPorts. If less, either try to locate/eliminate the source of the Wi-Fi interference or try relocating the relay and/or remote base station until they are within a 20dB SNR range of the main (and for the remote, of the relay).

  • EEM- Email alert with IP SLA Based on Packet Loss

    hi joseph,
    i need your advise, i want to get alert email based on IP SLA Packet loss
    the scenarion as below :
    1. If the traffic hit threshold packet loss greater than 20% as long 15 minutes --> send email
    2. If reset condition packet loss eq 0% as long 15 minutes --> send email again
     I don't know how to configure it condition. could you help me to verify my configuration below?
    ip sla logging traps
    ip sla 1 
     icmp-jitter 10.216.0.105 source-ip 10.216.0.107 num-packets 100 interval 40
     frequency 50
    ip sla schedule 1 life forever start-time now
    ip sla reaction-configuration 1 react Packetloss threshold-value 3 1 threshold-type immediate action-type trapOnly
    ip sla enable reaction-alerts
    event manager applet TEST 
     event syslog pattern "IP SLAs\(1\): Threshold exceeded"
     action 2.0 mail server "10.240.0.10" to "[email protected]" from "[email protected]" subject "Alert for Intermittent Link" body "link intermittent in x %"
    thank you

    What's you have could work with a few modifications.  First, increase that threshold-value of 3 to 20.  You can leave the falling threshold value of 1.  You'll need to add another applet to match the falling threshold syslog message.  Not sure exactly what that one will look like.
    The first applet will look like this:
    event manager environment q "
    event manager applet ipsla-threshold-exceeded
     event syslog pattern "IP SLAs\(1\): Threshold exceeded"
     action 001 cli command "enable"
     action 002 cli command "config t"
     action 003 cli command "no event manager applet ipsla-healthy"
     action 004 cli command "event manager applet ipsla-unhealthy"
     action 005 cli command "event timer countdown time 900"
     action 006 cli command "action 1.0 mail server $q 10.240.0.10$q to $q [email protected]$q from $q [email protected]$q subject $q Alert for Intermittent Link$q body $q link intermittent in 20 %$q"
     action 007 cli command "action 2.0 cli command enable"
     action 008 cli command "action 3.0 cli command $q config t$q"
     action 009 cli command "action 4.0 cli command $q no event manager applet ipsla-unhealthy$q"
     action 010 cli command "action 5.0 cli command end"
     action 011 cli command "end"
    And the second applet (the one where you'll need to fill in the appropriate syslog pattern) will look like:
    event manager applet ipsla-threshold-normal
     event syslog pattern "FALLING THRESHOLD PATTERN HERE"
     action 001 cli command "enable"
     action 002 cli command "config t"
     action 003 cli command "no event manager applet ipsla-unhealthy"
     action 004 cli command "event manager applet ipsla-healthy"
     action 005 cli command "event timer countdown time 900"
     action 006 cli command "action 1.0 mail server $q 10.240.0.10$q to $q [email protected]$q from $q [email protected]$q subject $q Link is stable$q body $q Link has been stable for 15 minutes$q"
     action 007 cli command "action 2.0 cli command enable"
     action 008 cli command "action 3.0 cli command $q config t$q"
     action 009 cli command "action 4.0 cli command $q no event manager applet ipsla-healthy$q"
     action 010 cli command "action 5.0 cli command end"
     action 011 cli command "end"

  • PB G4 to WRT54G Ping Times with Packet Loss!!???

    This morning when I woke up my PB G4, my Airport couldn't find my network. Found out that my father had turned off the modem and router because his Dell, which is wired to the router, had slow connection to the network (10 MB/ps or less, I think). I tried using Internet Connect using the assigned Network name and entering the WPA Personal password with no luck. So I then reset the router, configured to it's original settings and my fathers Dell got a better connection but my PB has gotten slower in connecting to sites and the page loading is considerably slower. Looked at iStumbler and it shows a lower signal and now it's showing noise, where before there was none. I ran a ping test to the router and got this.
    --- 192.168.1.1 ping statistics ---
    100 packets transmitted, 98 packets received, 2% packet loss
    round-trip min/avg/max/stddev = 1.536/2.495/26.476/3.414 ms
    The router is a WRT54G v5 with the latest firmware that I had just reflashed.

    I reset my router, changed the channel to 11 and disabled the SSID. That setting got a better but still iffy ping time with no noise.
    I tried your suggestion and got this, along with some noise.
    --- 192.168.1.1 ping statistics ---
    100 packets transmitted, 99 packets received, 1% packet loss
    round-trip min/avg/max/stddev = 1.596/4.201/33.784/6.652 ms
    Any other ideas?

  • 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

  • Photo has packet loss.  Can I improve the image with Aperature?

    I received a poor quality family photo (hard copy). Almost like "packet loss" on TV whereby the image edges are muted and/or missing. I wanted to enlarge the 3 X 5 inch photo but if the quality is poor at this resolution, I know enlarging will just make it worse.
    Can Aperature improve the photo quality? Compression or rendering or ??
    OR is this a photoshop opportunity?
    Please advise.
    Thanks

    Hi labratinaz;
    While I will admit I am now learning to use Aperture, IMHO this sounds like if it can be solve it will take Photoshop to do it. I don't think the adjustments in Aperture are powerful enough.
    Allan

  • 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.

  • Verizon FIOS Intermitte​nt Packet Loss Problem - How to Convince Verizon Support it's NOT ME

    Hi,
    I have been having a problem with Verizon FIOS Internet AND Phone since Thursday afternoon.
    Basically I have intermittent outages several times a day of 15-40 seconds where my download doesn't work, but upload still does. This happens on BOTH my phone and internet. Therefore it's not my router or computer equipment causing the problem.
    Here's what happens:
    - On the internet: I have a periodic download problem where I can receive no data for about 15 - 40 seconds. After that it returns to normal
    - On the phone: If I'm on the phone at the same time then during that period of internet loss I also can not hear anything that the person I am talking to says. However they can hear me just fine (ie. download only problem)
    I have been talking to Verizon technical support and they have blamed my router and ONT. I have tried switching off the router, and using a different one. Also they have replaced the ONT twice.
    * This problem occurs on BOTH the phone and internet at the same time. This clearly suggests the problem is not in my own house.
    In fact I know exactly where the problem lies. I did a traceroute to google below:
    Tracing route to google.com [74.125.113.106]
    over a maximum of 30 hops:
      1     4 ms     1 ms    <1 ms  192.168.1.1
      2     5 ms     4 ms     4 ms  L300.NWRKNJ-VFTTP-122.verizon-gni.net [74.105.157.1]
      3     9 ms     8 ms     7 ms  G2-0-0-1822.NWRKNJ-LCR-08.verizon-gni.net [130.81.133.156]
      4    11 ms     8 ms     7 ms  P15-0.NWRKNJ-LCR-07.verizon-gni.net [130.81.30.148]
      5     9 ms     6 ms     7 ms  so-5-0-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.29.8]
      6     7 ms     6 ms     7 ms  0.so-7-0-0.XL3.EWR6.ALTER.NET [152.63.19.177]
      7     9 ms    10 ms     9 ms  0.so-1-0-1.XL3.NYC4.ALTER.NET [152.63.0.213]
      8     9 ms     9 ms     9 ms  TenGigE0-6-0-0.GW8.NYC4.ALTER.NET [152.63.22.41]
      9    33 ms    31 ms    35 ms  google-gw.customer.alter.net [152.179.72.62]
     10     8 ms    11 ms    10 ms  209.85.252.215
     11    18 ms    17 ms    16 ms  209.85.249.11
     12    31 ms    29 ms    29 ms  209.85.241.222
     13    30 ms    29 ms    29 ms  209.85.241.207
     14    41 ms    39 ms    34 ms  209.85.243.1
     15    27 ms    27 ms    29 ms  vw-in-f106.1e100.net [74.125.113.106]
    Trace complete.
    Then I pinged each device for hops 2-4. When the problem occurs the first one in the hop - 74.105.157.1 - runs fine. The second device - 130.81.133.156 - times out, and all other devices further down the chain time out. This clearly suggest that the device:
    130.81.133.156 has major problems.
    I have mentioned this to tech support, but they have no way for me to send them logs. Apparently the support technicians at Verizon can not be trusted with even the most basic of tools like email and the web. They also shield me from the NT (Network technician), who is so special that even the tech support guys are only allowed to text chat with him, not actually talk to him. I have enough logs here to clearly show what the problem is.
    The latest from tech support is that they are sending yet another guy by my house tomorrow to witness this problem firsthand. Then he will call support that will text chat with the NT, and MAYBE they'll start thinking it's not me.
    My main question here is: "How do I get Verizon to believe it really could be a problem in their own network?"
    Here are some threads from last year that explain exactly the same problem I'm having. So it wasn't just me:
    http://forums.verizon.com/t5/FiOS-TV-Technical-Ass​istance/Verizon-FIOS-intermittent-connection-drops​...
    http://forums.verizon.com/t5/FiOS-Internet/Intermi​ttent-Network-Timeouts/m-p/28138
    One person said Verizon finally fixed it by replacing a PON card. I'm not sure if this is the same problem as that though.
    I am an avid Starcraft player and this is driving me crazy because I am getting dropped from my games all the time. Also phone conversations suck when there's these big lags where I can't hear who I'm talking to.
    I have had Verizon FIOS internet for 3 years now and this is the first problem I've ever had with it. But I'm starting to get majorly frustrated at how long it's taking to resolve the problem.
    Here is a sample of the ping logs I was talking about for different devices all at the same time.
    Device 2 in the Trace Route:
    Reply from 74.105.157.1: bytes=32 time=78ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=57ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=41ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=35ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=34ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=41ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=43ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=59ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=24ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=48ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=5ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=5ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=5ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=4ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=3ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=20ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=19ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=18ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=17ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=17ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=17ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=17ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=37ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=17ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=16ms TTL=126
    Device 3 in the Trace Route:
    Reply from 130.81.133.156: bytes=32 time=7ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=7ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=10ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=9ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=10ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=13ms TTL=253
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=7ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=6ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=14ms TTL=253
    Device 4 in the Trace Route:
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=7ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=6ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=7ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=7ms TTL=252
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=7ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=6ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=7ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=6ms TTL=252
    Any help, thoughts, suggestions, etc would be great appreciated!
    ~David

    I understand your logic, but you have not eliminated 74.105.157.1 as the problem.  It could be allowing packets out, like outside callers hearing you, but not allow them back in. Since you have results pinging out, trying ping back in. Use this packet loss tool.  You do not need to catch it when it's not working because this tool will ping your IP address (and all the hops in between) for up to 7 days. You will easily see when packet loss is occurring.
    If it can successfully ping 74.105.157.1 when the problem occurrs, then 130.81.133.156 is not the issue. This may not help dealing with the personalities at Verizon, but it will help definitively knowing which device is the issue.

Maybe you are looking for

  • Safari and also Webkit crashes after opening

    Safari and also Webkit crashes after opening Process: Safari [585] Path: /Applications/Safari.app/Contents/MacOS/Safari Identifier: org.webkit.nightly.WebKit Version: r82096 (82096) Code Type: X86-64 (Native) Parent Process: launchd [101] Date/Time:

  • Accessing Java System - Via SAPRouter

    Hi, Is it possible to access the NetWeaver component via SAPRouter.If yes please provide the settings to be done in saprouter and how to access BI java part in web browser. Thanks, Vignesh P

  • KM Document: edit locally - error occured "Operation Failed"

    Hi everyone! I am runnig SAP NetWeaver Portal 7.0 with MS Internet Explorer 7.0. I am trying to edit documents locally from the KM. Unfortunately it doesn´t work. Error occured "Operation Failed". I think all ActivX settings in the web browser are co

  • File Export is grayed out when Photo Book selected - worked yesterday

    I have been assembling a Photo book from various scanned photos. In order to share a preview before send it of to be printed, I used the File>Export option to produce a Quicktime movie. It worked very well but today I wanted to change some of the mov

  • Lyrics input glitch when melody crosses middle C

    I'm adding lyrics to a score. Everything is cool if all the melody notes are on a single staff. However, if the region has two staves (e.g. bass clef & treble clef) and the melody crosses middle C (i.e. changes staff), the lyrics input won't recogniz