- ripe-atlas - mailman.ripe.net

Outdated documentation to delete
by Stephane Bortzmeyer 30 Jul '13

30 Jul '13

IMHO, the "mechanize" example in <https://atlas.ripe.net/doc/code#access_from_scripts> is useless now that we have an API and should be deleted.

1 0

Spoofing the source IP address from a probe?
by Stephane Bortzmeyer 30 Jul '13

30 Jul '13

I read in the interesting <http://www.internetsociety.org/blog/2013/06/can-we-stop-ip-spoofing-internet> about BCP38 (anti-spoofing): > Another possibility that was suggested is using RIPE Atlas probes to > probe network capabilities (or shall we say incapabilities?). AFAIK, Atlas probes cannot currently perform these tests, am I correct?

9 11

Re: [atlas] Spoofing the source IP address from a probe?
by Alex Saroyan 30 Jul '13

30 Jul '13

Hi, Probably we don't need to spoof all address space, instead only if spoofing enabled just spoof to some predefined address range. Regards. /Alex Sanjeev Gupta <ghane0(a)gmail.com> wrote: >On Tue, Jul 30, 2013 at 11:22 AM, Randy Bush <randy(a)psg.com> wrote: > >> I support this point of view. I think controlled (anti-)spoofing >> measurements performed by the RIPE NCC with the consent of >> participating probes would be a good service to the community. > >perhaps the probe owners are not the only parties with skin in the game >and whose consent would be relevant? > > >Exactly. I host probes, and since you are spoofing others, we need to ask them. > >How you do this is left as an exercise to the reader. > >-- >Sanjeev Gupta >+65 98551208 http://www.linkedin.com/in/ghane > > >

1 0

Re: [atlas] Outdated for more than one day?
by Fred Grayson 28 Jul '13

28 Jul '13

Hello, The probe ID is 10156. It is attached to a third interface on my router. The graphs have been stalled for the last four days. The probe went online on June 26 and all was well until this happened on July 24. Thanks for looking. FG On 7/28/2013 6:35 AM, Iñigo Ortiz de Urbina wrote: > Good morning Fred, > > I just took a minute to check what you shared with the list. > > My two probes and built-in measurements look just fine (i.e they are > up to date). Your issue may be a temporary error. However, if you'd > like more details on your particular probe/problem pair, I've found it > to be helpful to provide details, such as probe ID or which controller > it is attached to. > > Are you still seeing the same stalled graphs? > > Regards, > > On Sat, Jul 27, 2013 at 8:53 PM, Fred Grayson <fred_grayson(a)yahoo.com> wrote: >> Hello, >> >> Recently, all Built-in-Measurments for my probe began showing "Outdated for >> more than one day" and none of the graphs are current, most show some white >> space at the far right hand side. >> >> My Total Uptime: 99.56% (31d, 22h, 30m) and I have power cycled the device >> twice trying to solve the problem. >> >> Any ideas on how to fix this will be appreciated. >> >> Thanks, >> >> FG >> > > >

1 0

Outdated for more than one day?
by Fred Grayson 27 Jul '13

27 Jul '13

Hello, Recently, all Built-in-Measurments for my probe began showing "Outdated for more than one day" and none of the graphs are current, most show some white space at the far right hand side. My Total Uptime: 99.56% (31d, 22h, 30m) and I have power cycled the device twice trying to solve the problem. Any ideas on how to fix this will be appreciated. Thanks, FG

1 0

Ping Fails (ns.ripe.net)
by AlbyVA 23 Jul '13

23 Jul '13

In reviewing My Probe stats, it appears that (ns.ripe.net) was once able to ping the server, but now it appears to be failing. All my other ping stats under My Probe show successful pings to other servers, but for some reason ns.ripe.net is failing. Does anybody have a suggestion of what might be going on, since ping is working to all the other servers. -Alby

4 6

No address in the results when ping or traceroute fail?
by Stephane Bortzmeyer 23 Jul '13

23 Jul '13

When a ping or traceroute emasurement fails, we do not know the IP address of the probe (empty "from" and no "src_addr"), which is annoying when you want to analyze the possible causes of the failure: { "size": 20, "addr": "2620:0:2d0:200:0:0:0:7", "min": -1, "rcvd": 0, "from": "", "dst_name": "2620:0:2d0:200:0:0:0:7", "af": 6, "timestamp": 1374395985, "fw": 4520, "proto": "ICMP", "name": "www.icann.org", "prb_id": 3953, "result": [ { "error": "sendto failed: Network is unreachable" }, { "error": "sendto failed: Network is unreachable" }, { "error": "sendto failed: Network is unreachable" } ], "max": -1, "dup": 0, "avg": -1, "type": "ping", "dst_addr": "2620:0:2d0:200::7", "sent": 0, "msm_id": 1013576 },

3 6

No probe shown in My Probes list (Registered. Plugged Probe v3 to network. 1st, 3rd, 4th LEDs lighted up.)
by Arthit Suriyawongkul 22 Jul '13

22 Jul '13

Hi I'm Arthit from Bangkok. New here. The switch at the probe is now at "3G/4G". Should i change to WISP or AP? thanks, Art -- เครือข่ายพลเมืองเน็ต -- "เปิดเน็ต เปิดใจ" Thai Netizen Network -- "Open Net. Open Mind." https://www.facebook.com/thainetizen

3 4

Strange and undocumented (?) result in traceroute JSON output
by Stephane Bortzmeyer 17 Jul '13

17 Jul '13

Measurement #1013405 contains: "result": [ { "x": "*" }, { "late": 20, "ttl": 61, "from": "88.79.15.141", "size": 96 }, { "x": "*" }, { "x": "*" } While "late" is documented <https://atlas.ripe.net/doc/data_struct#v4400_traceroute>, the lack of "rtt" field is not and crashes tools like json2traceroute.py.

3 2

[UDM] What value to give to 'requested' when 'type' = 'msm'?
by Stephane Bortzmeyer 17 Jul '13

17 Jul '13

The documentation <https://atlas.ripe.net/doc/measurement-creation-api/> says: "probes": [ { "requested": 1, "type": "msm", "value": 1000002 } ] but, from my tests, if you do so, you get only one probe, whatever measurement #1000002 actually used. To get all the probes, I had to indicate a very large number in 'requested' (unless you remember or count the actual number).

2 2