![]() ![]() ![]() |
|
dimsim:DonGould: pffft.... if you're going to keep all the info confo then it just becomes totally meaningless.
That latency is shocking for 5km.
I've got 3ms on that distance.
D
i dont know why the specifics matter much, they just show a first hop (local router), second hop gateway and then a series of other non-descript devices inbetween the source and the host.
DonGould:dimsim:DonGould: pffft.... if you're going to keep all the info confo then it just becomes totally meaningless.
That latency is shocking for 5km.
I've got 3ms on that distance.
D
i dont know why the specifics matter much, they just show a first hop (local router), second hop gateway and then a series of other non-descript devices inbetween the source and the host.
Because seeing the IP info and the PTR info in the MTR you sent me told me a lot more about the set up than what you've written.
It's also possible that the BRAS is over loaded and it's nothing to do with the radio link at all, which is why the provider is telling you what they're telling you.
What you were saying wasn't making any sense to me based on what I know about how we set up wireless networks sorry, but the IP info had tell tale info in it that made a few suggestions about what the problem is.
DonGould: Ok the OP just msged me a proper mtr and things are making a bit more sense.
In this case I'd be shooting this mtr info at the ISP and asking them to comment. The latency on that link is crap and I suspect that it's heading over way more than one link.
The first hop is on the providers BRAS.
What you can't see is the number of layer 2 hops.
I can't really tell you whats going on from what you've provided... but I can tell you a little story...
I had a link that had great latency but really slow thoughput. Turned out to be a duplex issue caused by a faulty cat5 cable on a switch in the link.
The link is only 7ms long (30km), but travels over half a dozen layer 2 hops before getting to the first layer 3 hop.
Same link had latency go though the roof. Turned out to be a failed radio two layer 2 hops away from me. Then we had local freq interference.
You really do need to talk to the provider as you just can't see the layer 2 switching.
HTH
D
dimsim: understood - thanks for clearing that up.
dimsim: I will not question again
dimsim:
Great to hear from a "Wireless Guy" that as I suspected things are not as rosey they should be, thanks for your input Don. I think I'll point them to this thread and ask them to explain themselves under a little peer review.
And as for not naming the provider... I really don't see any issue with not publishing the info you sent me. I very much doubt that provider would see any shame in a user having a service issue. It happens to all of us.
Slingshot:
And as for not naming the provider... I really don't see any issue with not publishing the info you sent me. I very much doubt that provider would see any shame in a user having a service issue. It happens to all of us.
That's what people like me are here for.
DonGould:Slingshot:
And as for not naming the provider... I really don't see any issue with not publishing the info you sent me. I very much doubt that provider would see any shame in a user having a service issue. It happens to all of us.
That's what people like me are here for.
Yes it is... and being open and honest that your service has an issue, when it does [1], saves so many of us so much time stuffing about trying to find a fault that's not in our end, so we love to have you in the public space! :)
[1] Slingshot is not the provider in this instance (well not the bit I was looking at anyway).
dimsim:
I've tried to work with them but with the answers I've been getting lately they are either incapable of fixing the problem or the problem is unable to be fixed - both particularly worrying. Apart from this, the frequent outages (mainly UPS/power related) the 4mb/4mb circuit when its working well suit me fine. More bandwidth would always be good but not at the cost of reliability.
Slingshot: If that is to your modem....then no, this is not good :)
|
![]() ![]() ![]() |