Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

Line Attenuation question

  • 09-07-2012 10:37pm
    #1
    Headshot
    Registered Users, Registered Users 2 Posts: 54,571 ✭✭✭✭


    Sorry for the quick question but I want to know is there a big differences between these attenuation's

    From 2010
    Line Attenuation (Down/Up):
    11 dB /5 dB

    Today
    Line Attenuation (Down/Up): 10 dB /7 dB


Comments

  • #2
    Cork981
    Registered Users, Registered Users 2 Posts: 763 ✭✭✭Cork981


    No pretty much the same, minor changes are expected at different times of day and with any change in conditions such as noise and weather.


  • #3
    PogMoThoin
    Closed Accounts Posts: 13,874 ✭✭✭✭PogMoThoin


    The copper in your line expands and contracts slightly everyday depending on the temperature. You will also notice a difference between averages in summer and winter


  • #4
    [Deleted User]
    Posts: 0 ✭ [Deleted User]


    That's a very good attenuation figure, you must be pretty close to the exchange to have it that low.


  • #5
    Headshot
    Registered Users, Registered Users 2 Posts: 54,571 ✭✭✭✭Headshot


    Karsini wrote: »
    That's a very good attenuation figure, you must be pretty close to the exchange to have it that low.

    I'm right beside the exchange but yet can't get faster than 3mb broadband but that is a discussion for another time.

    My hatred for eircom knows no bounds


  • #6
    PogMoThoin
    Closed Accounts Posts: 13,874 ✭✭✭✭PogMoThoin


    Karsini wrote: »
    That's a very good attenuation figure, you must be pretty close to the exchange to have it that low.

    See mine :pac:

    212502.PNG


  • Advertisement
  • #7
    [Deleted User]
    Posts: 0 ✭ [Deleted User]


    PogMoThoin wrote: »
    See mine :pac:

    My brother had 6dB/3dB in a place he once lived in - the exchange was literally behind his house.


  • #8
    PogMoThoin
    Closed Accounts Posts: 13,874 ✭✭✭✭PogMoThoin


    Karsini wrote: »
    My brother had 6dB/3dB in a place he once lived in - the exchange was literally behind his house.

    It's about 200m from the house.


  • #9
    MiniNukinfuts
    Registered Users, Registered Users 2 Posts: 951 ✭✭✭MiniNukinfuts


    I used to get 65dB/57dB on my old eircom line and we live approx 40m from an exchange. :P UPC all the way now.

    @OP, those levels are near perfect


  • #10
    [Deleted User]
    Posts: 0 ✭ [Deleted User]


    PogMoThoin wrote: »
    It's about 200m from the house.

    Yep, sounds about right.


  • #11
    Mr Cumulonimbus
    Closed Accounts Posts: 1,463 ✭✭✭Mr Cumulonimbus


    Wondering what people think of the following stats. I'm on up to 8 Meg NGB with Eircom.

    Speed : 8160 kbps / 512 kbps
    Line Attenuation (Down/Up) :44 dB / 20.5 dB
    DSL Noise Margin : 7.5 dB / 22 dB


    The noise figure seems a bit borderline. Was down to 6.5db (down) earlier.

    Speedtest:
    2060401955.png

    The line was originally limited to 5 Meg, but Eircom changed it upwards.


  • Advertisement
  • #12
    razor_ryan
    Registered Users Posts: 163 ✭✭razor_ryan


    Eircom DSL Statistics

    Line State Up Modulation DMT Data Path Interleave

    Downstream Max Allowed Speed (kbps) 2048
    Upstream (kbps) 256
    SN Margin (dB) 7.90 12.00
    Line Attenuation (dB) 57.50 31.50
    CRC Errors 3977 272


  • #13
    PogMoThoin
    Closed Accounts Posts: 13,874 ✭✭✭✭PogMoThoin


    Mr Cumulonimbus wrote: »
    Wondering what people think of the following stats. I'm on up to 8 Meg NGB with Eircom.

    Speed : 8160 kbps / 512 kbps
    Line Attenuation (Down/Up) :44 dB / 20.5 dB
    DSL Noise Margin : 7.5 dB / 22 dB


    The noise figure seems a bit borderline. Was down to 6.5db (down) earlier.

    Speedtest:
    2060401955.png

    The line was originally limited to 5 Meg, but Eircom changed it upwards.

    You're getting the max your line can handle
    Check it out here:
    http://www.farina1.com/adsl/


  • #14
    Headshot
    Registered Users, Registered Users 2 Posts: 54,571 ✭✭✭✭Headshot


    Is there a way to monitor a ping for lets say 30mins or somthing

    Somthing like ping test but for 30mins (doesnt have to be 30mins but a longer than ping test)


  • #15
    [Deleted User]
    Posts: 0 ✭ [Deleted User]


    Headshot wrote: »
    Is there a way to monitor a ping for lets say 30mins or somthing

    Somthing like ping test but for 30mins (doesnt have to be 30mins but a longer than ping test)

    You could use ping -t at the command prompt. Keeps going until you stop it.


  • #16
    Headshot
    Registered Users, Registered Users 2 Posts: 54,571 ✭✭✭✭Headshot


    Karsini wrote: »
    You could use ping -t at the command prompt. Keeps going until you stop it.

    Forgot about that, thanks

    Im hoping someone can help

    Why i asked was iv have been having trouble with my ping of late, eircom have told me they repaired it but im just very unsure

    these are my results so far
    ping -t www.eircom.net

    Pinging home.eircom.net [86.43.38.8] with 32 bytes of data:
    Reply from 86.43.38.8: bytes=32 time=34ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=59ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=36ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=35ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=38ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=36ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=37ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=34ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=38ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=37ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=38ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=36ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=36ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=44ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=52ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=36ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=41ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=93ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=38ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=34ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=44ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=42ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=36ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=37ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=35ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=36ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=42ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=33ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=39ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=36ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=35ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=36ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=34ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=36ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=37ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=34ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=37ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=37ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=39ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=36ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=38ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=34ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=39ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=54ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=54ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=38ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=33ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=37ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=81ms TTL=57
    Request timed out.
    Reply from 86.43.38.8: bytes=32 time=60ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=47ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=80ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=68ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=90ms TTL=57
    Request timed out.
    Reply from 86.43.38.8: bytes=32 time=37ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=38ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=37ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=34ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=43ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=34ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=38ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=39ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=35ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=38ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=46ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=38ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=39ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=49ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=39ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=46ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=37ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=68ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=55ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=38ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=55ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=37ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=37ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=37ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=35ms TTL=57
    Reply from 86.43.38.8: bytes=32 time=37ms TTL=57



    As you can see the ping goes well and bang it goes straight up and the request timed out, I think that isnt right at all. Am i over reacting ?


Advertisement