IP's with jitter/packet loss and very far away

Mailman List Mirror (Read Only)
1

Hi,

I am working on a presentation and looking to create samples of what a
trace should not look like? Anyone have IP's that I can trace from the US
or UK that will show
1) jitter
2) packet loss
3) very far away (perhaps an IP on a sat. link). Pref over 2000 ms

TIA.

Dovid

2

Anything on Integra's network.

3

Comcast?

4

Any specific IP? I don't want this to turn into an ISP bashing session......

5

Use probably any coffee shop’s wireless network to anyone any you’ll get that most of the time.

6

There are also plenty of simulators to create what you want. This one looks pretty useful:

http://www.linuxfoundation.org/collaborate/workgroups/networking/netem

7

I was just kidding anyway. This is a 10gig Voxel IP: 80.249.209.187

No loss or anything, but it is in the EU, ~ 155ms latency for me on US West coast.

8

Any hotel wi-fi around 7PM local time.

Chuck

9

Expanding on this a little further, you could use this tool + some virtual
machines and static routes to simulate just about any conditions you
wanted.

10

Tracing from the out side wont show anything as the external IP will be
good. I need something perhaps on a sat link.

11

Any hotel wi-fi around 7PM local time.

Chuck

Hi,

I am working on a presentation and looking to create samples of what a trace should not look like? Anyone have IP's that I can trace from the US or UK that will show
1) jitter
2) packet loss
3) very far away (perhaps an IP on a sat. link). Pref over 2000 ms

https://www.nanog.org/meetings/nanog47/presentations/Sunday/RAS_Traceroute_N47_Sun.pdf

my own experience is the misinterpretation of the above properties in
traceroute is pathological to the point of making it useless in the
hands of novices...

you shouldn't be looking for jitter in traceroute, because it's not
measuring the forwarding plane it's measuring the control plane.

intermediate loss is mostly meaningless, unless it cascades, in which
case it may have meaning but maybe not.

12

Hi,

my own experience is the misinterpretation of the above properties in
traceroute is pathological to the point of making it useless in the
hands of novices...

correct. you should be looking at the output of other data transit systems
such as iperf, bwctl etc - thats why such tools as PerfSONAR exist...allowing
you to find the real problems in your IP path

alan

13

Here is an IP tunneled over a 3G service in the UK: 37.26.225.245

-Bart

14

www.gov.mg shows fairly long ping times (especially with 1kB payload), a fair
amount of jitter, and some loss. It's not like pinging something at the D/E of
a really bad link, but I wouldn't want to push X graphics over it.