DeatheCore
Senior Member
You seem to have the same second hop packet loss as I do. Which area and FNO?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
You seem to have the same second hop packet loss as I do. Which area and FNO?
You seem to have the same second hop packet loss as I do. Which area and FNO?
That second hop packetloss is probably on the handover router. GPON congestion? It is a Sunday night. Everyone is streaming downloading ect.
can anybody confirm if this is only happening on cool ideas or if this is a vumatel issue or just a South African Issue?
I love cool ideas. but if the problem is with them i would move in a heartbeat
Loss on a particular hop doesn't mean anything if there's no loss on hops after that one. It just means the management plane of the device is busy while the switching backbone, which actually carries your traffic, is fine.
If a router was dropping 10 percent of the traffic through it, you'd see that 10 percent reflected in all hops downstream of said device
can anybody confirm if this is only happening on cool ideas or if this is a vumatel issue or just a South African Issue?
I love cool ideas. but if the problem is with them i would move in a heartbeat
Yeah, I find that Openserve very rarely is the issue. Well when you compare it to the likes of Vumatel xDNot a South Africa or Openserve issue. I'm on another ISP with Openserve and internet is fine.
Not a South Africa or Openserve issue. I'm on another ISP with Openserve and internet is fine.
So it's just a coincidence that when these issues do occur, the second hop (possibly handover router as mentioned before) suffers upwards of 75% PL which clears up to 0% when the issues clear up?

Ping statistics for 8.8.8.8:
Packets: Sent = 3237, Received = 3071, Lost = 166 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 264ms, Average = 6ms
Request timed out.
Reply from 8.8.8.8: bytes=32 time=8ms TTL=118
Reply from 8.8.8.8: bytes=32 time=6ms TTL=118
Reply from 8.8.8.8: bytes=32 time=6ms TTL=118
Reply from 8.8.8.8: bytes=32 time=9ms TTL=118
Request timed out.
Request timed out.
Request timed out.
Reply from 154.0.5.130: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=9ms TTL=118
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=5ms TTL=118
Request timed out.
Reply from 8.8.8.8: bytes=32 time=8ms TTL=118
Reply from 8.8.8.8: bytes=32 time=7ms TTL=118
Request timed out.
Reply from 8.8.8.8: bytes=32 time=4ms TTL=118
Request timed out.