I’m beginning to hate nLayer

July 20, 2010 at 12:12 pm | Posted in General | 1 Comment

Update: spoke too soon, they finally got back to me, so maybe it will go somewhere :)

Update the 2nd: now that they finally got to my ticket, they seem to have taken care of it very quickly; the issue has not happened since they tweaked something last night! :)

For the past few weeks I’ve been having constant disconnects between me and a server I’m often connected to. (Up to 20 disconnects a day, often grouped together, getting very annoying)

My debugging leads me to believe it’s an issue with some of nLayer’s routers, but so far their support department has completely ignored my messages…

Here’s my tests:

Dead:

traceroute to [redacted] ([redacted]), 30 hops max, 40 byte packets
1 [redacted] ([redacted]) 1.449 ms 2.548 ms 3.519 ms
2 wsip-24-234-89-129.lv.lv.cox.net (24.234.89.129) 29.241 ms 32.358 ms 33.054 ms
3 24-234-8-141.ptp.lvcm.net (24.234.8.141) 31.627 ms 34.132 ms 34.787 ms
4 24-234-6-245.ptp.lvcm.net (24.234.6.245) 36.012 ms 37.387 ms 38.146 ms
5 langbprj01-ae3.0.rd.la.cox.net (68.1.0.94) 39.451 ms 46.503 ms 45.684 ms
6 ae0-60g.cr1.lax1.us.nlayer.net (69.31.127.137) 47.103 ms
ae0-60g.cr1.lax1.us.nlayer.net (69.31.127.141) 49.818 ms 50.397 ms
7 * * *

traceroute to [redacted] ([redacted]), 30 hops max, 60 byte packets
1 router (192.168.1.1) 0.653 ms 1.602 ms 1.889 ms
2 ip70-173-25-1.lv.lv.cox.net (70.173.25.1) 25.800 ms 25.999 ms 25.965 ms
3 24-234-8-189.ptp.lvcm.net (24.234.8.189) 30.181 ms 30.387 ms 30.464 ms
4 24-234-6-57.ptp.lvcm.net (24.234.6.57) 32.115 ms
24-234-6-49.ptp.lvcm.net (24.234.6.49) 30.804 ms
24-234-6-57.ptp.lvcm.net (24.234.6.57) 32.139 ms
5 langbprj01-ae3.0.rd.la.cox.net (68.1.0.94) 36.867 ms 37.032 ms 37.786 ms
6 ae0-60g.cr1.lax1.us.nlayer.net (69.31.127.141) 37.284 ms 37.163ms
ae0-60g.cr1.lax1.us.nlayer.net (69.31.127.137) 36.291 ms
7 * * *

Working:

traceroute to [redacted] ([redacted]), 30 hops max, 60 byte packets
1 router (192.168.1.1) 0.638 ms 1.553 ms 1.854 ms
2 ip70-173-25-1.lv.lv.cox.net (70.173.25.1) 9.765 ms 9.964 ms 9.956 ms
3 24-234-8-189.ptp.lvcm.net (24.234.8.189) 63.833 ms 64.043 ms 64.132 ms
4 24-234-6-49.ptp.lvcm.net (24.234.6.49) 13.944 ms
24-234-6-57.ptp.lvcm.net (24.234.6.57) 14.713 ms
24-234-6-49.ptp.lvcm.net (24.234.6.49) 14.126 ms
5 langbprj01-ae3.0.rd.la.cox.net (68.1.0.94) 21.099 ms 21.265 ms 20.757 ms
6 ae0-60g.cr1.lax1.us.nlayer.net (69.31.127.137) 21.014 ms 20.608ms 20.562 ms
7 xe-0-2-0.cr1.dfw1.us.nlayer.net (69.22.142.22) 47.992 ms 42.931ms 43.098 ms
8 xe-2-2-0.cr2.ord1.us.nlayer.net (69.22.142.2) 63.567 ms 62.564ms 62.664 ms
9 po6.ar2.ord1.us.scnet.net (69.31.111.6) 63.004 ms 63.956 ms 62.470 ms
10 * * *

Tracepath:

Dead:

$ tracepath [redacted]
1: [redacted] ([redacted]) 0.163ms pmtu 1500
1: [redacted] ([redacted]) 1.809ms
2: wsip-24-234-89-129.lv.lv.cox.net (24.234.89.129) 46.246ms
3: 24-234-8-141.ptp.lvcm.net (24.234.8.141) asymm 4 35.816ms
4: 24-234-6-245.ptp.lvcm.net (24.234.6.245) 14.302ms
5: langbprj01-ae3.0.rd.la.cox.net (68.1.0.94) asymm 6 20.633ms
6: ae0-60g.cr1.lax1.us.nlayer.net (69.31.127.141) asymm 7 19.775ms
7: no reply

Working:

$ tracepath [redacted]
1: [redacted] ([redacted]01) 0.204ms pmtu 1500
1: [redacted] ([redacted]) 1.792ms
2: wsip-24-234-89-129.lv.lv.cox.net (24.234.89.129) 59.494ms
3: 24-234-8-141.ptp.lvcm.net (24.234.8.141) asymm 4 14.367ms
4: 24-234-6-241.ptp.lvcm.net (24.234.6.241) 16.196ms
5: langbprj01-ae3.0.rd.la.cox.net (68.1.0.94) asymm 6 24.259ms
6: ae0-60g.cr1.lax1.us.nlayer.net (69.31.127.137) 18.718ms
7: no reply
8: no reply
9: po6.ar2.ord1.us.scnet.net (69.31.111.6) asymm 8 65.385ms
10: no reply

As you can see, the connection always breaks off at xe-0-2-0.cr1.dfw1.us.nlayer.net (69.22.142.22) and xe-2-2-0.cr2.ord1.us.nlayer.net (69.22.142.2)

Why they can’t fix/replace it is beyond me, or at the very least respond to even say it’s been passed on to the actual network guys – its been weeks since the issue started, and almost a week since I opened the support ticket…

Bleh, just wanted to rant a little – if anyone knows more than I do about networking, am I wrong about what the info indicates? Could an issue outside of nLayer’s network trigger such a consistent disconnect in traceroute/tracepath?

1 Comment

  1. Sorry for the delay, we’re looking into it.


Sorry, the comment form is closed at this time.

Blog at WordPress.com. | The Pool Theme.
Entries and comments feeds.

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: