From BECHA at ripe.net Fri May 3 09:52:23 2013 From: BECHA at ripe.net (Vesna Manojlovic) Date: Fri, 03 May 2013 09:52:23 +0200 Subject: [atlas] News about latest RIPE Atlas release and a use-case story Message-ID: <51836CB7.7070006@ripe.net> Dear colleagues, as regular users, I am sure you have noticed the big changes we implemented last week: - new look of the opening page for visitors - new dashboard for logged-in users - new maps There are also more things added that are not so visible, but are the important features that you asked for: - probe sharing - one-off measurements - REST APIs Please see the details in this article by Robert Kisteleki, and let us know how happy you are with it all: https://labs.ripe.net/Members/kistel/new-ripe-atlas-features-april-2013 And just today, RIPE Labs article by St?phane Bortzmeyer was published, about using RIPE Atlas to take a look at how his anycast implementation behaves and which instance is the most popular: https://labs.ripe.net/Members/stephane_bortzmeyer/using-atlas-udm-to-find-the-popular-instances-of-a-dns-anycast-name-server If you have such an interesting measurement, please share it with us, and with the world. Regards, Vesna From robert at ripe.net Mon May 6 16:44:23 2013 From: robert at ripe.net (Robert Kisteleki) Date: Mon, 06 May 2013 16:44:23 +0200 Subject: [atlas] Fwd: [mat-wg] New on RIPE Labs: Releasing RIPE Atlas Measurements Source Code In-Reply-To: <5187C17B.2080305@ripe.net> References: <5187C17B.2080305@ripe.net> Message-ID: <5187C1C7.2040204@ripe.net> Dear RIPE Atlas users, Some of you might be interested in the news below. Regards, Robert Kisteleki -------- Original Message -------- Subject: [mat-wg] New on RIPE Labs: Releasing RIPE Atlas Measurements Source Code Date: Mon, 06 May 2013 16:43:07 +0200 From: Mirjam Kuehne To: mat-wg at ripe.net Dear colleagues, This new article on RIPE Labs introduces the RIPE Atlas measurement source code. The measurement code is the part that runs on the RIPE Atlas probes to schedule and execute particular measurements, and thereby forms the core of the RIPE Atlas system. https://labs.ripe.net/Members/philip_homburg/ripe-atlas-measurements-source-code Kind regards, Mirjam Kuehne RIPE NCC From BECHA at ripe.net Tue May 7 14:28:33 2013 From: BECHA at ripe.net (Vesna Manojlovic) Date: Tue, 07 May 2013 14:28:33 +0200 Subject: [atlas] Introduction of RIPE Atlas Quick Looks Message-ID: <5188F371.5020103@ripe.net> Dear colleagues, A new RIPE Atlas feature is now available to RIPE NCC members: Quick Look measurements. LIRs can use this service for a quick, real-time assessment of connectivity without hosting a RIPE Atlas probe. This feature is based on one-off measurements that are available to all RIPE Atlas probe hosts. Please find more information on RIPE Labs: https://labs.ripe.net/Members/kistel/ripe-atlas-quick-look-for-members Regards, Vesna From max+ratlml at grobecker.info Fri May 10 11:05:41 2013 From: max+ratlml at grobecker.info (Max Grobecker) Date: Fri, 10 May 2013 11:05:41 +0200 Subject: [atlas] Traceroute with GRE protocol possible? Message-ID: <518CB865.5040302@grobecker.info> Hi, I'm working for a company that gives customers access to PPTP and L2TP tunnels. Some of our customers have internet access via tv cable - without an exclusive public IPv4 address. These customers are more and more having trouble connecting to our systems via PPTP and we can't see any packets on our tunnel routers coming from these customers. A normal traceroute does not show anything weird and goes through to our servers... But with a traceroute --protocol=47 we would be able to find out which system is blocking the GRE packets used by PPTP. Is there any possibility to make GRE traceroutes with the ATLAS probes? Thank you! Greetings from Wuppertal, Germany Max From BECHA at ripe.net Mon May 13 12:38:02 2013 From: BECHA at ripe.net (Vesna Manojlovic) Date: Mon, 13 May 2013 12:38:02 +0200 Subject: [atlas] RIPE Atlas during RIPE66 Message-ID: <5190C28A.208@ripe.net> Dear colleagues (apologies for duplicates) this week, at the RIPE66 meeting in Dublin, you can meet few of the RIPE Atlas team people, if you are attending in person. Daniel, Robert, Rene and Vesna will be available to answer all your RIPE Atlas questions, and Lia and the the rest of Info Hub staff will be able to give you more probes, and also talk about sponsorship, ambassador-ship of the probes and other administrative details. We also have a few scheduled takes and events: - informal BoF session on Thursday evening: 18:00-19:00 .. where we will talk about new features and your wishes, both for "Anchors" and for regular RIPE Atlas functionality - 2 presentations at MAT-WG: an update - & related : RIPEstat public demo, Monday, BoF slot For the remote participation, you can watch webcasts and talk to us on irc (channel #bof), or send us emails or Tweets, as usual. Looking forward to meeting you this week, and having discussions and exchange of ideas! Regards, Vesna From nick at fluency.net.uk Mon May 13 16:39:28 2013 From: nick at fluency.net.uk (Nick Ryce) Date: Mon, 13 May 2013 14:39:28 +0000 Subject: [atlas] Probe registration Message-ID: Hi, Per my chat with Fearghas. Probe details are as below:- Probe 1: 10621 Probe 2: 10619 Nick -- Nick Ryce Fluency Communications Ltd. e. nick at fluency.net.uk w. http://fluency.net.uk/ t. 0845 874 7000 -------------- next part -------------- An HTML attachment was scrubbed... URL: From BECHA at ripe.net Mon May 13 17:21:44 2013 From: BECHA at ripe.net (Vesna Manojlovic) Date: Mon, 13 May 2013 16:21:44 +0100 Subject: [atlas] [Fwd: [mat-wg] New on RIPE Labs: RIPE Atlas Code for Analysis and Statistics Reporting] Message-ID: <51910508.3010906@ripe.net> Dear colleagues, please take a look at these tools, and let this be an inspiration & a reminder to upload your own to GitHub Community Repository! https://github.com/RIPE-Atlas-Community Regards, Vesna -------- Original Message -------- Subject: [mat-wg] New on RIPE Labs: RIPE Atlas Code for Analysis and Statistics Reporting Date: Mon, 13 May 2013 16:15:03 +0200 From: Mirjam Kuehne To: mat-wg at ripe.net Dear colleagues, We are releasing the code we use to analyse RIPE Atlas measurements and produce summary statistics. This will make processing these measurement results easier for the community. We're also inviting you to participate in improving this further. Please find more information on RIPE Labs: https://labs.ripe.net/Members/wilhelm/ripe-atlas-code-for-analysis-and-statistics-reporting Kind regards, Mirjam Kuehne RIPE NCC From pavelveselovskiy at gmail.com Tue May 14 14:25:48 2013 From: pavelveselovskiy at gmail.com (Pavel V. Veselovskiy) Date: Tue, 14 May 2013 16:25:48 +0400 Subject: [atlas] Probe number as a Target for measurements Message-ID: Hi, would it be possible to specify a probe number as Target for ping/traceroute mesurements? If no, could you advise, how i can programmatically mesure ping/traceroute between different pairs of probes. (It takes much time to do it manually). -- Thanks in advance & Best Regards -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- Pavel Veselovskiy Email: pavelveselovskiy at gmail.com Phone: +7 927 686 12 32 -------------- next part -------------- An HTML attachment was scrubbed... URL: From benc at cqx.ltd.uk Tue May 14 16:25:48 2013 From: benc at cqx.ltd.uk (Ben Clifford) Date: Tue, 14 May 2013 14:25:48 +0000 (UTC) Subject: [atlas] Probe number as a Target for measurements In-Reply-To: References: Message-ID: > would it be possible to specify a probe number as Target for > ping/traceroute mesurements? > If no, could you advise, how i can programmatically mesure > ping/traceroute between different pairs of probes. > (It takes much time to do it manually). If the probe has public DNS turned on, you can use a DNS name to refer to a probe - for example, my probe is number 10189 and appears in DNS as p10189.probes.atlas.ripe.net. You could use that name as the target for the ping. -- From office at newhost.com.ua Tue May 14 17:36:40 2013 From: office at newhost.com.ua (Nonna) Date: Tue, 14 May 2013 18:36:40 +0300 Subject: [atlas] =?utf-8?b?INCS0Ysg0YXQvtGC0LjRgtC1INGD0LrRgNC10L/QuNGC?= =?utf-8?b?0Ywg0LLQtdGA0YMg0LIg0YHQtdCx0Y8g0Lgg0YHQstC+0Lgg0LLQvtC30Lw=?= =?utf-8?b?0L7QttC90L7RgdGC0Lg/?= Message-ID: ?? ???????????? ?????? ???????? ???? ? ???? ? ???? ???????????? ?????? ??????? ? ??????????? ???? ?????????? ??? ???????? ???? ????????? ? ??????? ?????????? ??? ??? ?? ?????? ???????? ?????: "? ??????????!" ???????????? ???? ????????? ?????????? ???????? ? ????????? ?? ?????? ?????? ? ??????????? ?????. ????, 17-18-19 ???, 2013 ?. ??? ????: ??????? ??? ?????? ? ??????????????? ???????????! ???????????? ?? ??????? ???????? ? ?????????? ?????! ????????? ?? ????? ?????? ? ???????????! ????????? ? ??????????? ???? ????????? ?? 110%! ???????? ?????????? ??????? ??????? ? ????????! ?????????? ????????????! ???????? ??????? ? ??????????! ??????? ????????? ???????????! ?????? ??????????: "? ??????????!" - ??????????????? ????, ???????, ? ?????? ????? ?????????? ? ?????????????? ???????? ???????? ?? ???????? (??????????????? ? ??????????????) ???????. ???? ????? ??????? ???????? ? ?? ????? ???????? ??????????? ?????????? ??????????? ??????? ?????????. ? ????? ????????? ??????? ??? 6 ???????? ? ?????????. ??? ??????????? ????: ????????, ???????? ?? ????? ????????, ???????????-???????????? ???????, ???????????? ?????????, ???????? ?????????. ???? ???? ??????? ?????????? ????? 8-?? ??? ?? ????? ?????????? ???????? ??? ?????? ????? 10000 ??????? ? ???????? ??????? ??????????, ??????? ???? ???????, ????? ????????????, ??????????? ? ??????????? ???????????. ????? ????? "? ??????????!", ?? ???????: - ????? ?? ????? ????? ????????????; - ???????? "????????? ???????" ? ???????? ? ?????? ???????????; - ???????? ???? ???????? "?" ???????? ? ?????????????????; - ???????? ? ????????? ???????????? ???? ?????????; - ???????? ???????? ???????? ? ??????? ????; - ???????? ????? ?????? ??????????? ? ?????????; - ???????????? ?? ?????????, ??????? ? ???????? ???????? ???? ? ???????????; - ?????????? ?? ?????? ??????? ? ???????????; - ????????? ???????????? ??????????? ? ???????? ???????????? ?? ??????? ???; - ????? ?????????? ? ??????????? ?????????; - ????? ??????? ????????? ? "?????????? ?? ?????". ??????????????? ??????????: ???? ??????????: 17-18-19 ??? (3 ?????? ???) ?????? ?????: 17 ??? ? 10.00 ??????? ?????????? ? ?????????? ?????????? "?????????". 3 ??? ? ?????? ???????????, ??????????? ? ????????. ??????????? ???????? ? ????? ?????????? ?? ??. ????? "??????" ??????????? ??????? ??????? ?? 15 ???! ?????????? ? ???????: 450 ???. (?? ???? ?????? ??????????) ????????? ??????? ? ?????: ????? 795 ???! (?????? ?? 15 ???, ???.) ???????: (???? ?44) 36? 72 4? ???????????????* ?????????? ????? ????????: ?????????? ????? ??????????????? ? ?????????? ????????????. ??????????? ? ??????????? ? ??????? ? ?????????? ?????????. ?????????? ??????????? ? ??????? ??????????. ?????? ?????????????? ? ???????????? ?????????? ??????. ???????? ???????? ?? ???????, ??????????????? ? ????????. ???????? ???????????????? ?? ?????? ? ???????????. ??????????? ????????? ? ??????? ? ???????? ??????. ?????????? ???? ? ???? ? ???? ???????????. ?????????? ? ??????????????? ????? ?????????, ?????????? ??????????. ?????????? ????????? ?? ???????? ? ????? ?????. ?????? ? ?????? ? ??????? ? ???????! * 100% ????????! ???? ????? ??????????? ???????? ?? ??????? ??? ?? ???????? ??? ?? ???????????, ?? ?? ?????? 110% ????? ??????????. ??????????????? ??????: (???? ?44) 360 72 40 Click here to unsubscribe. -------------- next part -------------- An HTML attachment was scrubbed... URL: From BECHA at ripe.net Wed May 15 23:38:33 2013 From: BECHA at ripe.net (Vesna Manojlovic) Date: Wed, 15 May 2013 22:38:33 +0100 Subject: [atlas] [Fwd: [mat-wg] [Fwd: Community suggestion for ATLAS spoof test]] Message-ID: <51940059.9070001@ripe.net> Dear RIPE Atlas people, please take a look at this proposal, and discuss on the mat-wg mailing list. Thanks, Vesna -------- Original Message -------- Subject: [mat-wg] [Fwd: Community suggestion for ATLAS spoof test] Date: Wed, 15 May 2013 22:37:28 +0100 From: Vesna Manojlovic To: Measurement Analysis and Tools Working Group Dear colleagues, please take a look at the suggestion from Alexander Isavnin. Since he is here in Dublin, we can talk about it during MAT-WG or, if there is not enough time, at the RIPE Atlas community BoF. However, the opinion of the rest of the community counts too, so I ask you to comment on the mailing list, if you are interested. Regards, Vesna -------- Original Message -------- Subject: Community suggestion for ATLAS spoof test Date: Wed, 15 May 2013 21:16:30 +0200 From: Alexander Isavnin To: Vesna Manojlovic Dear Vesna! Could you forward this suggestion to mat-wg mailing list (and other appropriate lists). Due to high requirements to mitigate spoofing there is need to detect one. RIPE community have great distributed networking tool - ATLAS. As first step i suggest to select address from RIPE NCC network and allow all probes (if probe is not behind NAT) to send spoofed packet with this address as source. As first and a half step - allow to send packets with source addresses of anchors (if anchor's host agrees) As second step - allow probe host to permit use his address as spoofed source. Best regards, Alexander Isavnin From kix at kix.es Thu May 16 00:44:31 2013 From: kix at kix.es (Rodolfo =?utf-8?B?R2FyY8OtYSBQZcOxYXM=?=) Date: Thu, 16 May 2013 00:44:31 +0200 Subject: [atlas] [Fwd: [mat-wg] [Fwd: Community suggestion for ATLAS spoof test]] In-Reply-To: <51940059.9070001@ripe.net> References: <51940059.9070001@ripe.net> Message-ID: <20130515224431.GA25875@kentin.kix.es> Hi Vesna, IMO these options should be set by the "probe owner" (no all probes by default). What is the aim of these options? Probably are good to know if the ISP is allowing spoofing packets, but should we run them always? Cheers, kix On Wed, 15 May 2013, Vesna Manojlovic escribi?: > Dear RIPE Atlas people, > > please take a look at this proposal, > and discuss on the mat-wg mailing list. > > Thanks, > Vesna > > -------- Original Message -------- > Subject: [mat-wg] [Fwd: Community suggestion for ATLAS spoof test] > Date: Wed, 15 May 2013 22:37:28 +0100 > From: Vesna Manojlovic > To: Measurement Analysis and Tools Working Group > > Dear colleagues, > > please take a look at the suggestion from Alexander Isavnin. > > Since he is here in Dublin, we can talk about it during MAT-WG > or, if there is not enough time, at the RIPE Atlas community BoF. > > However, the opinion of the rest of the community counts too, > so I ask you to comment on the mailing list, if you are interested. > > Regards, > Vesna > > -------- Original Message -------- > Subject: Community suggestion for ATLAS spoof test > Date: Wed, 15 May 2013 21:16:30 +0200 > From: Alexander Isavnin > To: Vesna Manojlovic > > Dear Vesna! > > Could you forward this suggestion to mat-wg mailing list (and other > appropriate lists). > > Due to high requirements to mitigate spoofing there is need to detect one. > > RIPE community have great distributed networking tool - ATLAS. > > As first step i suggest to select address from RIPE NCC network and > allow all probes (if probe is not behind NAT) to send spoofed packet > with this address as source. > As first and a half step - allow to send packets with source addresses > of anchors (if anchor's host agrees) > As second step - allow probe host to permit use his address as spoofed > source. > > Best regards, > Alexander Isavnin > > > -- ||// //\\// Rodolfo "kix" Garcia ||\\// //\\ http://www.kix.es/ From arnoldyk.flickcutsy at mail.ru Thu May 16 15:27:46 2013 From: arnoldyk.flickcutsy at mail.ru (=?Windows-1251?B?z2Vw5ePu4u7w+y4gS+DqPw==?=) Date: Thu, 16 May 2013 17:27:46 +0400 Subject: [atlas] =?windows-1251?b?z3Do7fbo7/sg6CDhYefu4vvlIO1h4vvq6CDzY+9l?= =?windows-1251?b?+O37eCDvZfDl4+7i7vDu4g==?= Message-ID: <774400959.20130516317122@mail.ru> > ???xo????? ???e??? ?e????????? ? BA?? ?A???? ?????E ???E?? > ?pe???? ? 30 ??? ? 2013 ?. > ?. K??? ? ?o??????a ???p? ? ?p. 40-?e??? O?????? 70 ? c?. ?e??o ????oc???????? > ?e?.: (044) 228-90-?o??-????, 228-?e??pe-?????-69 -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- ??c??? ?pe????? - ?o????o???? ??o?e??????????? ???e??????????. ?????a?????? ?pe???? ?a???o? ?e????? ??????????x ???e??????? ?a??????? ?a p??????? ??e??? ? ?a???o?, ?e??x?????? ??? ?c?e????? ??a??o???????? ? ????ece. ?????o ?op?a????? ?p????, ??p????????? ?p??e?? ?o?????e?c? p??? ?c????????????? ?a?o???. ?o??????e ? ??e??? ??????a?? ??? ?a?o?? ?o?o?e? B?? ?o?????? ??????a????? ???e?? o? ??????x ???p??. ??o? ?p????? ?o?e??? ?e?, ??? ?o?o ?????????oc?? ???e??????? ????e??? ?e??x?????? ?c????e? ?c?????? ????e??????????? ????????o???. ???a?a? ??o?x??????? ??????? ???ec?????, o???o? pa???? ? ??e???? ?a???? c ?????? ?o??o ?a?????????? ?a ??????e????? ???????e??? ? ????ec?, a ??o?a??? ?e?? ??a????? ?????o? ???e????? ???e? ? ?p?????? ???e??????? ????o ??c????????? ?a ????????o??? ?????o ??o????e???. ripe.net ????B?? A???????? * p??o???????? o?????? ?p????, ???e????? ?o c????, ?????????e ???????a??, ??a?e???? ?o??o??? ????a??? ? ?.?. ?E?? ???H???? * ?o?????? ????e??????????? ????e????????? p????????????, ??o ?o?????? ????c??? ?????????oc?? pa???? ?ep??????, ?a?o??????? ? ?p??a???. ??E??? * ???o??e?? ?p??a ??a????p???? - ?a????a? ?c??o?????????? ?a?? ??o?e????, op?a??????????? ?o?c???????, ?o??, ?????a? 15-?? ?e???? o??? ?p???????? ???p???x ? ?o??????????? ??e????o?, ?o??????a??? ?o ?????? ? ??o????????????? ?po??e???. A??op ???ee 100 ?e?????? ?a?o?. ?oc??????? ????e?? ?o ?o?po??? ????e?? ??p???? ??p? K?ep. ripe-atlas ??O?????? 1. 5 ?c?o???? ??a??? ??pe????????? ????e???

2. ????o?o??? ? ??p????????: * o??o???? ?p?????? ? ?a?o??? ?a???? ?c?????? ??pe??????? * ?a?????? x?p????? ?e??????????? * ?o?????e?? ?a? ????p????? ?c?a???????? ?o??a??a * SMART-?e??: a????? ?o?c??????? ?e?e? ? ?e?e? ??p????? * ???a????? ?o?e?e??? ? ?ep???????? * o??e??????? c??p????? ?o????? * ??o?????, ???p????? ? ??c??e??? ?a ???e???????. 3. ??c???e???: * ?o?c? ?o???? ?e???? * ??e??o????? ? ?c????? * ???p????? ?pe???????? * ????????e ??o??? ????e??????? ?????e???? * o??p???? ? ?a?p???e ???p??? * ??a? ?? 5-?? ?????o? ?o ?a???a??? ?o?po??? * ?e????? a?????o?? c??????? * o??o???? ?p?e?? a???????o c???a??? * ???o? ?e???????? ?o?????. 4. ??x??????? ?c?a???????? ?c?????????????? ?o??a??? ? ????a??? ??????? ? ?ep????????? ??o?e??? (H?? ? ??x?o?????): * ??o????e??? * ???c?????? * ?a???????? ?o??a??? * ?e????e ??????e ?a c??e??????? * ????p?????????. 5. ?a????????? ? ?ep????????: * ?a? ??????? ?a???????????? ?o?e?e??? * ???? ?a?????????, ?c??????e??? ? ???e??????? * ??????a ????a??????? ? ?e???? ??e?? * ?a????a ??e???o? ??p??? * ??????a ?o??a???????? ?o?????? * ?a????a ??a?????. 6. Bo???????? o??o?????? ? ?a? c ???? ???o???? : * ?p????? ?o??????????? ???p?????? * ????p??????? ?o?p?????? ? ?ea????? * ?e?o???a ????p???????? ???p?????? * ?e????? o??e??? ?a ???p?????? 7. ????e?e??? ??o??? ?e?e??????? ? ?a? ? ?o??? p????? ?e ?c??????? ?ce. ?E?O?O????? ?PEH???? * ?e?????a ?po?e????? ??e????? ??e?c??????? ?o??? a?????o? ????e??? c ????e?????? ????-?e???? (?e??????????? ???o??), p??e??? ? ???o??x ??p, ?????a????? ??pa??e??? ??? p??p?????? ? ?a??e?????? ?????o? ? ??e???, ?p???o??? o?c???e??? ? a?????? ?o??pe???? c??????? ?? ?po?????????????? o???? ??a?????o?. ??A???????? ?E???????? * ?o??e????????? ? ????e?????????? ?e???????????; * ?oc??????? ???c????????? pe?????a?? ? ?ep????????? ??o?????; * ??e?e???? ?????e??? ? p???????x c???a???? ???e???; * ???c??????? ??c?p? ??xo???? o?????????e pe????? ? ????e??? ?e?????????; * ??e??? a?a?????????? ? ???o???????? ?????e???? o???. ????A???? * 9.30-18.00 * ?epe??? 13.30-14.30 * ????c?????? c 9.00 ? ?o??e. C?O??O??? * 1200.00 ?p?. ?a o??o?o ??ac????a. * ??? ??op??? ? ?????e?? ???c????a c????? ? 5% ? 7% ?o????????????. * B c????o??? ?xo???: ????p?a??????-???????????????? o?c????????? ?a ce???a??, c??p??? ?a?e??????, ????-?p???, ??e? ? pe???????, o????????? ?o?????? ? ???e? ??e????? c ?????p??. O?K??????? O? PAC????? * ???????e, ?c?? ??o ??c??? ?p??????o Ba? ??????c???. * Ba? ??p?? ???? ?? ???????x ????????o?: ?a? ?a???x ?pe??p?????, ??p??o?, ???-?a???? ? ?. ?. * ??o?? o??a?a???? o? ??c?????, ?o?a???c??, c?o????? ?a? ?a? ?????p????? a?pe? ?o ?????o??. ?E????????? * ?e?.: (044) 228-90-?o??-????, 228-?e???e-?????-69 * ???c: (044) 280-1044 * Ka???? ???c???? c??????? ?????a?? ????a???????? ?o???e?? ? o?????a?? ?o????????: ?o?o???, a??, op????a? c????, ?o??? c???e?e?????. -------------- next part -------------- An HTML attachment was scrubbed... URL: From arnoldy.flickcuts at mail.ru Thu May 16 22:55:47 2013 From: arnoldy.flickcuts at mail.ru (=?Windows-1251?B?wWHt6vDz8vHy4u4g5+Ag7W/i6Owg5+Dqb+1v7CE=?=) Date: Fri, 17 May 2013 00:55:47 +0400 Subject: [atlas] =?windows-1251?b?weDt6nBv8vHy4u4=?= Message-ID: <106852353.20130517012527@host.novidron.net> An HTML attachment was scrubbed... URL: From madis555 at hot.ee Fri May 17 00:32:32 2013 From: madis555 at hot.ee (Sulev-Madis Silber) Date: Fri, 17 May 2013 01:32:32 +0300 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure Message-ID: <51955E80.9020703@hot.ee> Hello. Probe (v2) doesn't seem to recover from all network failures automatically. It currently connects using IPv4 and reports IPv6 tests as "can't send". I can't ping probe on IPv6 and it seems like it doesn't talk IPv6 at all on that VLAN, although router sends RA's every minute. In web interface it says that it has IPv6 address (all other things under IPv6 are "Undetermined/Unknown") but it doesn't actually participate in network at all. Only router talks IPv6 in that network, according to tcpdump. I think not recovering from IPv6 failures is a bug. Somehow, it still recovers from IPv4 failures. Problem appeared after I had it physically disconnected from Ethernet for some hours. Before that, probe also didn't have connection to internet for a day. I wish I would not need to pull the power every time this happens. Although it's rare occasion that anything is down here. Thanks. From olaf.maunz at me.com Fri May 17 12:27:04 2013 From: olaf.maunz at me.com (Olaf Maunz) Date: Fri, 17 May 2013 11:27:04 +0100 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <51955E80.9020703@hot.ee> References: <51955E80.9020703@hot.ee> Message-ID: <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> I have noticed the same. I have a IPv4 and IPv6 enabled router. Every time I reboot the router I have to restart the probe. On 16 May 2013, at 23:32, Sulev-Madis Silber wrote: > Hello. > > Probe (v2) doesn't seem to recover from all network failures > automatically. It currently connects using IPv4 and reports IPv6 tests > as "can't send". I can't ping probe on IPv6 and it seems like it doesn't > talk IPv6 at all on that VLAN, although router sends RA's every minute. > In web interface it says that it has IPv6 address (all other things > under IPv6 are "Undetermined/Unknown") but it doesn't actually > participate in network at all. Only router talks IPv6 in that network, > according to tcpdump. > > I think not recovering from IPv6 failures is a bug. Somehow, it still > recovers from IPv4 failures. Problem appeared after I had it physically > disconnected from Ethernet for some hours. Before that, probe also > didn't have connection to internet for a day. I wish I would not need to > pull the power every time this happens. Although it's rare occasion that > anything is down here. > > > Thanks. > From walleryc.baykof at mail.ru Fri May 17 16:20:26 2013 From: walleryc.baykof at mail.ru (=?Windows-1251?B?SOXk4ujm6Ozu8fL8?=) Date: Fri, 17 May 2013 18:20:26 +0400 Subject: [atlas] =?windows-1251?b?x2H56PLgIO/w4OIgY+7h8fLi5e3t7vHy6A==?= Message-ID: <528288816.20100916367835@mail.ru> > ?????A ??A? ???C????????? > C?????? ? 6 ???? ? 2013 ?. > ?. K??? ? ????????a ???p? ? ?p. 40-?e??? O?????? 70 ? c?. ???po ?????c???????? > ?e?.: (044) 228-90-?o??-????, 228-?e??p?-?????-69 -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- ?P?H?? * ????e??? ????p?? - ??p???o? ???a?? ???, Bc??????????? ??e??????? ????, A???????e????? ?e???a ??pa????? ?a???a ????, a???p ??????a??? ? c????????????????? ???a???x ?C??o???????? ?e??????????: ?e???. ????c?????. ??e??, ???????p?, ?ce o ???????e????? ????e? ? ?p.. ????P???? ?P?K?????? 1. ?apa???? ?o????????? ? ?a????????????? ??e???????? ??a? ?a ?e???????? ????e???o. * o???? ?a?o?o?????????? * ??a??? ?po?e??? ? ?????o? ?e?????????? ?????o?????????? * ???a?????e c?op??? ? ?????? ??? c??????????? * ?o???? ?o??????????? ? ???a ?p??a ?a ????ec??o 2. ?p???? o??c??????? ??a? ?a ????????oe ????e???? * ?a????????????? * ???e???? * ???o?????? * ?o???????????? * ????c?????????? 3. ?co???????? ???c?????e?? ??????a ?e??c?????? ??a? ?a ????????o? ????e???? * ?a?o???????????? * o????? pe????????? * ???c? ? ????c? ??????a ?e??c?????? 4. H???? ?o????? ?po??????? pe??c?????? ??a? ?a ?e???????? ?????c??? (a????? ?????e??? ?a???? ??pa??? ?O ??e????? ???e????? ? ???o? ??p???? ?O ?oc??a????????? p???c?????? ?????x ?pa? ?a ?????????e ????ec??o ? ?x ??p????????? ? ?p???? ?????o????????? a??? ??pa???? o? 11.02.2010 ?. ? 1878-VI ? ?????c??????? ??p?a?????-???????? a???? ? ?oc?a???????? K?? ? 703 o? 22.06.2011 ? ? 1141 o? 22.11.2011). * o???p ???o???????????? * ?o??e op?a?? ?e?????????, ?e?ep? ?x 3 * ?o???????? ? ?c????? p???c?????? * o???p ?????o? ?????e? ????e?? 5. ???e??? ????e?a??? p?????????? * o?????????? o?????o? * ??c??p????????? c??c?? 6. He?o????? o?o???????? ? ???p?????? ?pa? ?a o?????? ??????????o ????e???a. H???? ?epe???? ?pa????????????????? ?????e??o?.

7. P?????????? ??a?a ?????o????? ??a???? ??? ?p???? ?????a????? ?o????????

8. ?c????????? p?????????? ??a?? co??????????? ?a ???e??? ?e???e???????? ???o?????????.

9. O?o???????? o????????? ? ?e??c?????? ca???????? ??c?p?????? o??e??o? (c??????? ? ??ec??e???? ??p????). ?pa????? ? ?co???????? ?e????????? ?e????????????.

10. ??p??o? ?p???????????? ???o??a??? ?? ??c??a?????????? pe?????? ?pa? (?o??e ?o??? ??e??????????? ???o??????).

11. ?e??c?????? ????e??.

PE??????? * 9.30-17.30 * ??p???? 13.30-14.30 * Pe??c?????? c 9.00 ? xo?e. ??O??O??? * 1400.00 ?p?. ?a o????? ??ac?????. * ??? ??opo?? ? ?????e?? ???c????? c????? ? 5% ? 7% c?????????????. * B c?o?????? ??o???: ???op?a??????-???????????????? o?c????????? ?a c????a??, ???p??? ???ep?????, ?o??-?????, o?e? ? p????????, o?????e??? ?o?????? ? ???e? ??e????? c ?????p??. O?KA?????? O? P??????? * ???????e, ?c?? ??o ??c??? ?p??????o ?a? ????o?c???. * Ba? ??p?? ???? ?? ???p???? ?c????????: ?a? ?a???? ??e??p?????, ??p??o?, ???-ca???? ? ?. ?. * ??o?? o??a?a???? o? ??c?????, ???????c??, ?oo????? ?a? B?? ?????po???? a??e? ?o ???e?o??. ?E????????? * ?e?.: (044) 228-90-?o??-????, 228-?e????-?????-69 * ?a??: * K????? ??a????? c??????? ?????ae? ????a??e????? ?o?????? ? ?p??????? ?????e??o?: ?o???o?, a??, o??????? c?e?a, ?o??? ????e???????. -------------- next part -------------- An HTML attachment was scrubbed... URL: From laurent at laurent-wattieaux.com Fri May 17 18:32:27 2013 From: laurent at laurent-wattieaux.com (Laurent Wattieaux) Date: Fri, 17 May 2013 18:32:27 +0200 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> Message-ID: <51965B9B.2050004@laurent-wattieaux.com> Hello, Me too I've the same problem. > I have noticed the same. > I have a IPv4 and IPv6 enabled router. Every time I reboot the router I have to restart the probe. > > > On 16 May 2013, at 23:32, Sulev-Madis Silber wrote: > >> Hello. >> >> Probe (v2) doesn't seem to recover from all network failures >> automatically. It currently connects using IPv4 and reports IPv6 tests >> as "can't send". I can't ping probe on IPv6 and it seems like it doesn't >> talk IPv6 at all on that VLAN, although router sends RA's every minute. >> In web interface it says that it has IPv6 address (all other things >> under IPv6 are "Undetermined/Unknown") but it doesn't actually >> participate in network at all. Only router talks IPv6 in that network, >> according to tcpdump. >> >> I think not recovering from IPv6 failures is a bug. Somehow, it still >> recovers from IPv4 failures. Problem appeared after I had it physically >> disconnected from Ethernet for some hours. Before that, probe also >> didn't have connection to internet for a day. I wish I would not need to >> pull the power every time this happens. Although it's rare occasion that >> anything is down here. >> >> >> Thanks. >> > -- Laurent Wattieaux Gsm: 06 86 67 62 30 Profil Google+ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: gprofile_button-32.png Type: image/png Size: 1487 bytes Desc: not available URL: From daniel.karrenberg at ripe.net Sat May 18 11:45:38 2013 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Sat, 18 May 2013 11:45:38 +0200 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <51965B9B.2050004@laurent-wattieaux.com> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> Message-ID: <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> Thank you for letting us know and also for speaking up to let us know this happens to more than one of you. We will look at this after the holiday weekend. In the meantime it would help to know the type of the routers and details about your IPv6 routing configuration. Thank you again Daniel On 17.05.2013, at 18:32 , Laurent Wattieaux wrote: > Hello, > > Me too > > I've the same problem. >> I have noticed the same. >> I have a IPv4 and IPv6 enabled router. Every time I reboot the router I have to restart the probe. >> >> >> On 16 May 2013, at 23:32, Sulev-Madis Silber >> >> wrote: >> >> >>> Hello. >>> >>> Probe (v2) doesn't seem to recover from all network failures >>> automatically. It currently connects using IPv4 and reports IPv6 tests >>> as "can't send". I can't ping probe on IPv6 and it seems like it doesn't >>> talk IPv6 at all on that VLAN, although router sends RA's every minute. >>> In web interface it says that it has IPv6 address (all other things >>> under IPv6 are "Undetermined/Unknown") but it doesn't actually >>> participate in network at all. Only router talks IPv6 in that network, >>> according to tcpdump. >>> >>> I think not recovering from IPv6 failures is a bug. Somehow, it still >>> recovers from IPv4 failures. Problem appeared after I had it physically >>> disconnected from Ethernet for some hours. Before that, probe also >>> didn't have connection to internet for a day. I wish I would not need to >>> pull the power every time this happens. Although it's rare occasion that >>> anything is down here. >>> >>> >>> Thanks. >>> >>> >> > > > -- > Laurent Wattieaux > Gsm: 06 86 67 62 30 > > From olaf.maunz at me.com Sat May 18 11:53:06 2013 From: olaf.maunz at me.com (Olaf Maunz) Date: Sat, 18 May 2013 10:53:06 +0100 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> Message-ID: <6F642DEF-1425-4FD6-A98C-CE93A076E1B3@me.com> I am using Apple's AirPort Extreme on a modem(FTTC) with native IPv4 and an IPv6 tunnel over tunnelbroker.net. Probe: 2142 On 18 May 2013, at 10:45, Daniel Karrenberg wrote: > Thank you for letting us know and also for speaking up to let us know this happens to more than one of you. We will look at this after the holiday weekend. In the meantime it would help to know the type of the routers and details about your IPv6 routing configuration. > > Thank you again > > Daniel > > On 17.05.2013, at 18:32 , Laurent Wattieaux wrote: > >> Hello, >> >> Me too >> >> I've the same problem. >>> I have noticed the same. >>> I have a IPv4 and IPv6 enabled router. Every time I reboot the router I have to restart the probe. >>> >>> >>> On 16 May 2013, at 23:32, Sulev-Madis Silber >>> >>> wrote: >>> >>> >>>> Hello. >>>> >>>> Probe (v2) doesn't seem to recover from all network failures >>>> automatically. It currently connects using IPv4 and reports IPv6 tests >>>> as "can't send". I can't ping probe on IPv6 and it seems like it doesn't >>>> talk IPv6 at all on that VLAN, although router sends RA's every minute. >>>> In web interface it says that it has IPv6 address (all other things >>>> under IPv6 are "Undetermined/Unknown") but it doesn't actually >>>> participate in network at all. Only router talks IPv6 in that network, >>>> according to tcpdump. >>>> >>>> I think not recovering from IPv6 failures is a bug. Somehow, it still >>>> recovers from IPv4 failures. Problem appeared after I had it physically >>>> disconnected from Ethernet for some hours. Before that, probe also >>>> didn't have connection to internet for a day. I wish I would not need to >>>> pull the power every time this happens. Although it's rare occasion that >>>> anything is down here. >>>> >>>> >>>> Thanks. >>>> >>>> >>> >> >> >> -- >> Laurent Wattieaux >> Gsm: 06 86 67 62 30 >> >> > > From madis555 at hot.ee Sat May 18 13:01:23 2013 From: madis555 at hot.ee (Sulev-Madis Silber) Date: Sat, 18 May 2013 14:01:23 +0300 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <6F642DEF-1425-4FD6-A98C-CE93A076E1B3@me.com> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <6F642DEF-1425-4FD6-A98C-CE93A076E1B3@me.com> Message-ID: <51975F83.2000801@hot.ee> Here it's FreeBSD doing RA and giving out /64 for probe #4415 It's nicely separated in it's own VLAN. Weird to think, /64 only for single device... :) What a F... waste of IPv6 space... P.S.: There is a field in probe's config that says "type of router". Everyone should fill that field up, so no more asking about what kind of router this is you run. On 2013-05-18 12:53, Olaf Maunz wrote: > I am using Apple's AirPort Extreme on a modem(FTTC) with native IPv4 and an IPv6 tunnel over tunnelbroker.net. > Probe: 2142 > > > > On 18 May 2013, at 10:45, Daniel Karrenberg wrote: > >> Thank you for letting us know and also for speaking up to let us know this happens to more than one of you. We will look at this after the holiday weekend. In the meantime it would help to know the type of the routers and details about your IPv6 routing configuration. >> >> Thank you again >> >> Daniel >> >> On 17.05.2013, at 18:32 , Laurent Wattieaux wrote: >> >>> Hello, >>> >>> Me too >>> >>> I've the same problem. >>>> I have noticed the same. >>>> I have a IPv4 and IPv6 enabled router. Every time I reboot the router I have to restart the probe. >>>> >>>> >>>> On 16 May 2013, at 23:32, Sulev-Madis Silber >>>> >>>> wrote: >>>> >>>> >>>>> Hello. >>>>> >>>>> Probe (v2) doesn't seem to recover from all network failures >>>>> automatically. It currently connects using IPv4 and reports IPv6 tests >>>>> as "can't send". I can't ping probe on IPv6 and it seems like it doesn't >>>>> talk IPv6 at all on that VLAN, although router sends RA's every minute. >>>>> In web interface it says that it has IPv6 address (all other things >>>>> under IPv6 are "Undetermined/Unknown") but it doesn't actually >>>>> participate in network at all. Only router talks IPv6 in that network, >>>>> according to tcpdump. >>>>> >>>>> I think not recovering from IPv6 failures is a bug. Somehow, it still >>>>> recovers from IPv4 failures. Problem appeared after I had it physically >>>>> disconnected from Ethernet for some hours. Before that, probe also >>>>> didn't have connection to internet for a day. I wish I would not need to >>>>> pull the power every time this happens. Although it's rare occasion that >>>>> anything is down here. >>>>> >>>>> >>>>> Thanks. >>>>> >>>>> >>>> >>> >>> >>> -- >>> Laurent Wattieaux >>> Gsm: 06 86 67 62 30 >>> >>> >> >> > > From robert at ripe.net Sat May 18 13:11:00 2013 From: robert at ripe.net (Robert Kisteleki) Date: Sat, 18 May 2013 12:11:00 +0100 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <51975F83.2000801@hot.ee> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <6F642DEF-1425-4FD6-A98C-CE93A076E1B3@me.com> <51975F83.2000801@hot.ee> Message-ID: <519761C4.1000504@ripe.net> > P.S.: There is a field in probe's config that says "type of router". > Everyone should fill that field up, so no more asking about what kind of > router this is you run. Indeed, but we can only ask hosts to fill that up, it's up to them to actually do that. Quick statistics: almost 50% of the currently connected probes have this field filled in somehow. Eyeballing the contents tells me it's mostly sensible data. Regards, Robert From laurent at laurent-wattieaux.com Sat May 18 13:52:35 2013 From: laurent at laurent-wattieaux.com (Laurent Wattieaux) Date: Sat, 18 May 2013 13:52:35 +0200 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <519761C4.1000504@ripe.net> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <6F642DEF-1425-4FD6-A98C-CE93A076E1B3@me.com> <51975F83.2000801@hot.ee> <519761C4.1000504@ripe.net> Message-ID: <51976B83.1050605@laurent-wattieaux.com> Hello, My router is a D-Link DIR-825 (Hardware Version: B1 Firmware Version: 2.06EU) with IPv6 in IPv4 tunnel over SixXS (Autoconfiguration type : SLAAC+Stateless DHCPv6 and automatic IPv6 address assignment enabled). I am using SixXS DNS cache service for my IPv6. -- Laurent Wattieaux -------------- next part -------------- An HTML attachment was scrubbed... URL: From max+ratlml at grobecker.info Sat May 18 18:09:09 2013 From: max+ratlml at grobecker.info (Max Grobecker) Date: Sat, 18 May 2013 18:09:09 +0200 Subject: [atlas] (OT) RIPE PTR zone damaged in the last few days? Message-ID: <5197A7A5.6080502@grobecker.info> Hi, this is not directly an ATLAS issue - but at least a RIPE related question. A friend of mine has problems at the moment with his server hoster. In particular, the PTR record for the server's IP cannot be resolved because the attached nameserver answers with NXDOMAIN. Not a big problem, espacially not a RIPE problem. But here's the response he got from his hoster a few days ago (translated from german). It's a bit... Well... The right word would be: "venturesome": -------- Today at 5:21 PM we got a reply from a RIPE technician who acknowledged that this is a known issue. Not only our IPs are affected by this. The RIPE had a large synchronisation problem between their root name servers which leaded to the situation that the responsible name servers are not connected to the right IPs. The RIPE technician said, the problem could only be solved by a serialized restart of all root name servers, followed by a resync. -------- Funny, eh? A few sentences later: -------- At the moment, the RIPE technicians are busy with preparations for this restart and sync. Actually, the restart of the servers will be done in the night from monday to tuesday. The synchronization process needs about eight more hours to complete. After that, your PTR should be resolved correctly. -------- A RESTART of the ROOT NAME SERVERS? "PTR doesn't work!" - "Have you tried turning it off and on again?" But the best part: -------- We got information that not only our IPs are affected by this, about 27% of all available IP subnets are affected - which is a huge amount. -------- The RIPE status page says: It's all OK, we have no planned maintenances. So I'm very sure the hoster is lying to us and should get a really long wooden nose. But before we make bigger trouble I would like to hear from some others (maybe a RIPE employee?) that the PTR zone was not harmed in the last few days. It's a bit more official, you know... ;-) THANK YOU! -- Greetings from Wuppertal, Germany Max Grobecker From tore at fud.no Sun May 19 16:57:39 2013 From: tore at fud.no (Tore Anderson) Date: Sun, 19 May 2013 16:57:39 +0200 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> Message-ID: <5198E863.7090604@fud.no> * Daniel Karrenberg > Thank you for letting us know and also for speaking up to let us know > this happens to more than one of you. We will look at this after the > holiday weekend. In the meantime it would help to know the type of > the routers and details about your IPv6 routing configuration. FYI, in case you want to debug this problem present on a live probe, it appears to be the case for probe 121 at the moment. It's connected behind an AVM Fritzbox using SLAAC. No other devices connected to it have a similar problem. The probe should have had the IPv6 address 2a02:fe0:cf16:70:220:4aff:fec6:cd7a (which actually shows up on the probe's web page), but it does not respond to anything - not to ICMPv6 NS from the local link to the aforementioned address, nor to fe80::220:4aff:fec6:cd7a. No responses from its link-local address is seen when pinging ff02::1 either. All the default measurements says "Cannot send". If you have no use for this debugging opportunity, let me know and I'll reboot the probe and see if its IPv6 connectivity comes back then. Tore From whitetigx at gmail.com Sun May 19 22:30:23 2013 From: whitetigx at gmail.com (=?UTF-8?B?UmVuw6kgU2Now7xtYW5u?=) Date: Sun, 19 May 2013 22:30:23 +0200 Subject: [atlas] (no subject) Message-ID: <5199365F.2030403@gmail.com> From larisza.fedretsuko at mail.ru Mon May 20 00:46:16 2013 From: larisza.fedretsuko at mail.ru (=?Windows-1251?B?wf7k5mXy6PBv4uDt6OU=?=) Date: Mon, 20 May 2013 02:46:16 +0400 Subject: [atlas] =?windows-1251?b?S1BJluxv8uji4Pbo/yDk6/8g8PPq7uJv5Ojy5evl?= =?windows-1251?q?=E9?= Message-ID: <800066801.20130520943735@mail.ru> > ???????p??????, KPI??o??????? ??? ???o?o??????? > ?p????? ? 30 ?a? ? 2013 ?. > ?. K??? ? ?oc?????? ???p? ? ?p. 40-?e??? ?????p? 70 ? c?. ???p? ????o????????? > ?e?.: (044) 228-90-?o??-????, 228-?e??pe-?????-69 -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- ??? ???O ??? co?c????????? ? ?????o??????? ?????c? ?E?? ? ?A?A?? ?P?????? * ?a?? c?c?e???? ?o?x?? ? ??a????????? ? ??pa??e??? ?e?????????? ????e?a / ?o??????????? * ?a????? ?op???????? ????e?? ? ?x a?a?????????? * ?o?a?a?? ???e??????? ??c?p??e??? ???????po????? ? ?a? ??a?????? ?p?a???????? ?p??e??, ??o?? ?e ?p????? ????e? ?pe?? ? pe????? * ?a?? ??c??????? co???????? ?a?pa? ? ?o???e??? ?????????o???, ???a?????? ???e????? ?o?????? * ?o???a??, ?a? ??pa????? ?????co? / ?o???????????? ?p? ?o???? ????e??? * ?a?? ?po???? ? ??o???? ???????e?? ??pa?????? p??????????? * ?o?a???? ????e??? ?a???p? ? ?x ??????e ?a ????????oc?? ????e?? * ???p???????? KPI ??? ????a???, ???o????????? ?a??a?????? ? ????a???????? * ?a?? ??c?p??e??? ? c?c???? ??c?p????? ???a?? ?o p??????a??? KPI ? ?o???a??? ???H??-??????? * H???p?????? ??op? ? ?e????????? ???e??o? ???????o??-?????????????? ????a??? ??o???e???, ????????a??, ??e???? o??? 17 ?e? ??pa??e??? ? 10 ?e???? o??? pa???? ???a??o??? ??p??????? ? ????a???x ?????a? ????a. A??o? ?o?ee 50 ??????a??? ? ?.?. ???? ?????e???o?????. O? c?pa????? ?o ????e?a ?o?a????? ???o?o??????, ?C?c?e?? c??????????????? ?????a?????: ??e?p????, o????? ????e??????? ?o??a????. ??c???? ?o ?o?po??? ??????o???? ??????e???, pe?????a??????? p??o?o?????, c??a????? ? ?o???????? c?????? ???a??e??? ????ec??. * C?ap??????? ???a ? ????e?-?????? c ???ee ?e? 16-?? ?e???? ??a????????? o???o? ??pa??e??? ?????ca?? x??????o??? c??????p ?????o?? ?????c?. ??c?ep?-??????? ? o???c?? ?????co?, ???????p??????, c?????? c??????????????? ?????a?????, ??????e???????? ??e??, a?a???a ? o?????o???. ???o???? o??? ?op????????? ??c???? ??p???e???????? ??e?? ? ????p??????, ?oc??????? ?ex???e???? ?a????? ??? ??e?p???? ERP-??c?e? ??? ?p???? ?o??????, ?op?a??????? ?????c ??o?????? ?o??????. ???op ??o?ec??? ??????a??? ? ?.?. ????: - ?????e?????????: o? c?pa????? ?o ????e?a-????????? p???????????, x?? ??o??? ? ?H? ?a ?po???e??? 5 ?e?; - ?C???e?? ??a?a??????????? ???a???????: ????p????, o?e??? ????e??????? ????a????. ?PO?????? ??EH???? * ?o???? 1. C???e?? ??????e??? p??????a???? ?????c? * ??c?????? ?????? ?a ?a?o?? ???e???e???. ??e??? ???e????????? p??o???????? ? ??????e?? * He ??????e ????e???? - o????????????? ?a ?o???a???? * C ?o?o??? ?e?? ??pa????? ?????o?????? ? ????p??e??? ??p????????? ??????a / ???p?????????
- ??p???e??? ???????.
- ?a? ??a???o???? ?e??e???o??? ????a???.
- ?e?? ?o??a??? ? ???a?co??? ???a?a????.
- C?e??o? ?????e? ? ?e??? ? ??a??. * ????e ?????co??? ?e?? ?e??x????? o?pe?????? ??? pa??????x ??pa????? ? ?a?a? ?????c?
- ?????c???? ?e?? ??? 3 ????e??? ??p?????? ??x??? ?? ????e????? ????a ????ec? ? c??a?????????? ?e?e? ????a???
- c?c???? c??????????????? ?o?????????. * ?a? ???e???? ?c?e?? * C???? ?o?????????? ? ?pa??o??????? ???e?. O? ???e? ?o??a??? ? ????e?? - * ???e?????? ???e? ????a??? ? c?????? ????????o????? * ?oc?a????? ?????c???? ?e?e?, ??c?????????? o????c????????? ?a ???????a? c ?o?o??? ?o???? ? ???o?? * ??????e ???a??e??????? p??e??? ?a ???a?c???? ?????a???? * ?a???p?, ???????e ?a ?p????? ??p??. ?e?? ?p???e? ?p?????. * ?o???? 2 ?e??o????? ????e??o?o ??????e??? ?o??a???? * Ka??? po?? o??e???? ???????p?????? ? ??pa?????? ????e??? * ???a??e??????? ? ????e???? ????. ??o ??o??????? ???a?? ???e???e???, ??o?? ?o??????c? ?c?a?o??????? ?e?e? * ?a?e? ????o ???????po?????? ?e??, c??e??????, ????o??o??? ??c???? ????e????o ??????e??? ?p???p??????. * C ?e?? ??????e??? ??c?p????? ??c?e?? ????e???o????? * ?e?o???? ????e??p??????. ????e??po????? ?o ??O ? ?p??????? op?e??????????? ????e??po????? (ABB ????e??p??????) * ??o ????a?? c???????? ????e? ??? ??o??????? ??a??p?????? * Oc?o???? ???? ????e?o? ? o?e?????????, ???e?????????? ? ???a?????? ????e?? * Op????????????? ? ??????o??? c??????p?.
- ???e? ????a ???a?????? ??p??????? ???? ??O
- ?p?????? ?o?????????? ?????co??? c?p????p? ?a ???e ?p?????????????. ????e????????? ?o ??O. * C??????p? ? ??c??? ??????a * ??a?????????? ????e?o? ?o??a??? * ?o???? 3 ???o???? c?????????? ??????o? * ???a?????? ??a????????? ?a? ?????o???? ????e??p?????? * ?a? c??????????? ?????c???? ?e?? ????a???? * ?p????? ?o?e?? ???a?c????? ?????p?????? (?????e?? ?po?o????????????? ?a??a? ? ?ac?? a????o? o??e?? ??o???); * ??a??????????????? ??????o???? ????a * K?? ?oc?????? ????????e ?po??o??? ???????p? ? ?ex?o????? coc???????? ??????a. * ?a? ?????o???????? ???o??. * ??p????????? ?o????????? ??? ????e?a. ????????o????? ??e??? ???? ? c???? ??e??. * ?ex???? ?????p?????? o??????????? ??????o?, ????e?o? ????a????????
- B???????e ???a?????????? ?a??o??? ????e??
- ????e? ?p??a?,
- O??e??????? ?o??e?????? ? ?????c?p?????? o????? ?po???
- ????e? ?o??e??????? ?ac?????,
- ????e? ce???????????,
- ????e? ?????o?,
- ????????o????? pac????? ?a ?ep?????
- ??a????????? o?o??????? ?????a?? (c????, ??????p???? ?a????e??????, ?e????)
- ??a??po????? ?c???????? ???????p?????? ????a???: co????????? ? ???????e????.
- Ka? c?????p????? ???e???? ?o???, ?p?????, ?o?pe?????? ?o ??e??e? ?????c????????? ???a?c???? ?????p??????, ??????o??? ????e??: ????e? ???o??? ? ??c????? (??????e? ? ?????o?), ????e? ????e??? ?e?e???? c?e????, ??o??????? ?????c. ??x???? ??a??p??????.
- C?????? ????e? ????a??? * ??o??o?????????, c???a??????? ? ???ep?????? ????e?a. * K?? o?o??????? ? ?a?????? ????e?? * ????e? ?p???? * HR ????e? * ????e? ?a???????? * ????e? ?o??????? * ??o??? ????e?? * ?o???? 4 ????a????, ?o??po?? ?c???????? ????e??? ? a????? o???o?????. * K?? pa?p??????? ????e???? pe??a???? * ?o?????? ? ??o?????? ???o??e??? ??????a. * A?a??? ??????e??? ??????a. B??? ??????a. * ?a? ?po????? ??a??? o???o????? ??a?-?a?? * ???a???a ????e??o?? a?????a * ?????a ?a???p??, ?o???????? ?a o????????? ? c?e?e?? ?x ??????? * K???p????? ? ??????o??? ?o ????e?a? * ?o???? 5 P??p?????? ??c?e?? o?e??? ?e??e???o??? ????a???, ?o??a???????? ? c??p??????? KPI - ?????a??? * ?e?? ????e?a ? ?e?? pa?o?? c?p????p??? ?o?p?????????. ?e???? ?e?e? * ??p????a DuP- int.
- K?? ?o???????? ????a??? ? ????o????? ?a?o? ??? o?pe??????? ?o?a?a????? ???p????????? ? c??p???????. * ?a? ??o????? ??a????? ??????a ?c?o???o???? ? ???a?????? ????a???? ? co?p?????? * ?o???????? ??? ?a??o?? ??o??? op????????? * ???e?e??? KPI ? ??pe??????? ?e????? o??e??????????? ?a ?o????????. * ????e?? ?????a??? (?a??p??????? ?oc?????????)
- ???e? ?eo?????? a????? ?????a? ?a p???e ????a.
- C?c???? ?pe??p?????? ? ?o??a?p???????
- ??a??po????? ? ??c?a?????? ?e???
- O?ec??????? ?????????o??? ?e?c????? * ??c??????? c???e?? ???a?o? ? ????c??; * ?o?????? ?o?????? ?o ?????po?????? ???a?? ?o?-???????????; * ?o?????a ????a??? ?o ??????o?????? o????e ?p?????? ?e?e???????; * ??p??????? ??c?? ???a?? ?p??? ??? ??e ?ap???????????? ?o?p?????????; * ???e?????? ?a??? ???a?? ?p??a ??? ???p???????????? ?o??a????????. ????e? ???a?? ?p??? ??? o????? ????a?; * O????? ???e?????o??? ??p??????
- B??? ?????a????? ? o??ac?? ????e????? (?o??p???, o?e??a ??????????c??, ?o??p????? ??c?e?? ?pe?????????)
- KPI. ?p???? ?o???a?????. KPI - ??a??e???. KPI - ??o?????????. KPI -????c????. KPI - C???. KPI - Ka???. KPI - ?a??e????. KPI - ???a???; * ?a?????????? ?o???????
- ?p?????? ?o???????? ??c?e?? ?pe?????????.
- ?o?????????? ??p????p? ?o?o???. O?pe??????? ?o????????? ?a??e? ??pa?????? ??a??. ??o ????e? ?a ?p??e?? ?/??
- C???? ??c???? ??e??p?????? c KPI
- ??p???????? ????e??? ?o??????e??o? KPI
- B??????? ?xe?? ??c???? ??p??????? ??c??
- O??e??????? ?op???? ??c???? ?o?a?a?????, ??a????? ? ?????a ????????e??o?
- ?op??p?????? o???? ?ap??a???? ?o?????
- O?pe??????? ?o??a ?o??????? ??? ?o??????. ?p????? ??p??p?????? ??????a ?a ?O?
- ?o?????????? ??p???? ?ac???? ?e?e?????? ??c?? ??p??????? ??a??
- ???????e o????? ? c?e??? ?o?????o????? * ??e?????? c?????? ??e??? ?????????oc?? ? ??p????? ?a ?o??? ??c???? ???a?? ?p???
- ?e???? o????c????????? ? op?a???????, ??????p????????? ? ???p?????? ? o??????a??? ??c???? ????a????????? ? ???a??????? o?e??? ???e?????o??? (KPI). P??? o??e?? ???c?????
- ??o???????? o?????????? c???? ???a?? ?p??? PE??????? * 9.30-17.00 * ???e??? 13.30-14.30 * P???c?????? c 9.00 ? ?o?e. C????O??? * 1600.00 ?p?. ?a o????o ??ac?????. * ??? ??op??? ? ??e????? ???c????? c????? ? 5% ? 7% c?????????????. * B ??o?????? ?xo???: ??????a??????-???????????????? ????????a??? ?a ce???a??, c?o???? ?a????????, ???e-?????, o??? ? ?e???????, ??c???e??? ?o??a?o? ? o???? ??e????? c ????o???. ???A?????? O? ?A?????? * ???????e, ?c?? ??o ??c??? ?p??????o ?a? ????o?c???. * B?? ??p?? ???? ?? ???p???x ???o??????: ?a? ?a???? ?????p?????, ?op????, ???-?a???? ? ?. ?. * ??o?? ???a?????? o? pac?????, ?o?????c??, ??o????? ?a? B?? ??e??po???? ??p?? ?o ?????o??. ?E????????? * ?e?.: (044) 228-90-?o??-????, 228-?????e-?????-69 * ???c: * Ka???? ??ac???? ?????a?? ?o???ae? ????a???????? ?????e?? ? op????a?? ?o??????o?: ?????o?, a??, ?p?????? ??e?a, ?o??? c???e???????. -------------- next part -------------- An HTML attachment was scrubbed... URL: From madis555 at hot.ee Mon May 20 05:33:15 2013 From: madis555 at hot.ee (Sulev-Madis Silber) Date: Mon, 20 May 2013 06:33:15 +0300 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <51976B83.1050605@laurent-wattieaux.com> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <6F642DEF-1425-4FD6-A98C-CE93A076E1B3@me.com> <51975F83.2000801@hot.ee> <519761C4.1000504@ripe.net> <51976B83.1050605@laurent-wattieaux.com> Message-ID: <5199997B.7080008@hot.ee> What the hell is going on there? It's in "can't send" state again. And I somehow remember I could ping it outside of it's /64, now I can't. It doesn't respond. However now it answers to ICMP ping (inside of it's /64) and also talks NDP like it should. From nattalyk.geoodofa at mail.ru Mon May 20 10:48:35 2013 From: nattalyk.geoodofa at mail.ru (=?Windows-1251?B?wWHt6nDz8mPy4u4g5+Ag7e7i6Owg5+Dq7u3u7CE=?=) Date: Mon, 20 May 2013 12:48:35 +0400 Subject: [atlas] =?windows-1251?b?weDt6nBv8vHy4u4=?= Message-ID: <371586708.20130520273383@mail.rurki.com> An HTML attachment was scrubbed... URL: From mick.odonovan at bt.com Mon May 20 11:25:09 2013 From: mick.odonovan at bt.com (mick.odonovan at bt.com) Date: Mon, 20 May 2013 10:25:09 +0100 Subject: [atlas] New Probe Deployment Message-ID: Hi Atlas team, Fresh from RIPE66 meeting I've just deployed my new atlas probe this morning and can see it's pingable locally on the network with it's dhcp'ed address. I am just wondering now however how long it takes before this probe should be visible at http://atlas.ripe.net as I need to give it a fixed IP address for live network deployment. Thanks in advance, Mick Mick O?Donovan | Network Engineer | Core & Access Operations | BT Ireland | Block C, Dundrum Business Park, Dublin 14, Ireland | Phone: +353 1 4326480 | Mob: +353 863870425 | BT MeetMe +353 12421053 ? 1800946924 PartCode: 75039807# |E: mick.odonovan at bt.com | Web: www.btireland.ie Planned Absence: This e-mail and any files transmitted with it are confidential and may be privileged and are intended solely for the use of the individual(s) or entity to whom they are addressed. As email can be subject to operational or technical difficulties and time delays, communications that are subject to deadlines should also be sent by post. Any unauthorised direct or indirect dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this e-mail in error, please let me know immediately on the e-mail address above and delete the e-mail from your system. Thank you for your co-operation. BT accepts no responsibility for changes to or interception of this e-mail after it was sent or for any damage to the recipient?s systems or data caused by this message or its attachments. We monitor our e-mail system, and may record your e-mails. This e-mail shall not constitute a binding contract. BT Ireland, trading in Republic of Ireland as BT Communications Ireland Limited. Registered office: Grand Canal Plaza, Upper Grand Canal Street, Dublin 4, Registered in Ireland no 141524 and trading in Northern Ireland as British Telecommunications plc. Registered office: 81 Newgate Street London EC1A 7AJ Registered in England no: 1800000, both being affiliates of BT Group plc. ? Please don't print this e-mail unless you really need to -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8232 bytes Desc: not available URL: From robert at ripe.net Mon May 20 11:43:18 2013 From: robert at ripe.net (Robert Kisteleki) Date: Mon, 20 May 2013 11:43:18 +0200 Subject: [atlas] New Probe Deployment In-Reply-To: References: Message-ID: <5199F036.4070109@ripe.net> On 2013.05.20. 11:25, mick.odonovan at bt.com wrote: > Hi Atlas team, > > Fresh from RIPE66 meeting I've just deployed my new atlas probe this morning and can see it's pingable locally on the network with it's dhcp'ed address. > > I am just wondering now however how long it takes before this probe should be visible at http://atlas.ripe.net as I need to give it a fixed IP address for live network deployment. > > Thanks in advance, > > Mick Hi, This depends on a few factors. We've given out a lot of probes at RIPE66 so I expect to be somewhat behind on the administration of this. You also have to register your probe at https://atlas.ripe.net/register. If our part of the administration is done (see above) *and* you register your probe using the same user account (email address) that you gave us when we gave your probe, then the process could be done in half an hour. Otherwise it needs checking on our side. Hope this helps, Robert From mick.odonovan at bt.com Mon May 20 11:47:38 2013 From: mick.odonovan at bt.com (mick.odonovan at bt.com) Date: Mon, 20 May 2013 10:47:38 +0100 Subject: [atlas] New Probe Deployment In-Reply-To: <5199F036.4070109@ripe.net> References: <5199F036.4070109@ripe.net> Message-ID: Hi, This depends on a few factors. We've given out a lot of probes at RIPE66 so I expect to be somewhat behind on the administration of this. You also have to register your probe at https://atlas.ripe.net/register. If our part of the administration is done (see above) *and* you register your probe using the same user account (email address) that you gave us when we gave your probe, then the process could be done in half an hour. Otherwise it needs checking on our side. > Thanks Robert - I believe my probe is indeed registered. What I did was I > registered on the site on Monday and collected at the info hub on Tuesday. I > was informed that the probe was linked to my account but I'm obviously not > 100% I had thought it should be all up and running by now but it's still showing as offline. (10740) is the id. Thanks, Mick -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8232 bytes Desc: not available URL: From jomat+ripeatlasml at jmt.gr Mon May 20 13:23:07 2013 From: jomat+ripeatlasml at jmt.gr (Johannes Matheis) Date: Mon, 20 May 2013 11:23:07 +0000 Subject: [atlas] Probe marked offline but responds icmp echo requests Message-ID: <1369048846-turnsole-44597@leto.j.dn42> Hello, today I got a notification that my probe 4365 is offline. But it still responds to ICMP echo requests. Is there a way to bring it back online to the atlas network, preferably without physical access to it? Regards, Johannes Matheis From robert at ripe.net Mon May 20 13:46:06 2013 From: robert at ripe.net (Robert Kisteleki) Date: Mon, 20 May 2013 13:46:06 +0200 Subject: [atlas] Probe marked offline but responds icmp echo requests In-Reply-To: <1369048846-turnsole-44597@leto.j.dn42> References: <1369048846-turnsole-44597@leto.j.dn42> Message-ID: <519A0CFE.2070001@ripe.net> Hi, We're experiencing a problem with one of our controlling servers, which in some cases (like yours) causes probes to be shown as disconnected, while in fact they are sending in data normally. We expect to resolve this soon, most likely tomorrow. Regards, Robert On 2013.05.20. 13:23, Johannes Matheis wrote: > Hello, > > today I got a notification that my probe 4365 is offline. But it still > responds to ICMP echo requests. > Is there a way to bring it back online to the atlas network, preferably > without physical access to it? > > Regards, > Johannes Matheis > > From natallyc.maxheriyn at mail.ru Mon May 20 13:48:25 2013 From: natallyc.maxheriyn at mail.ru (=?Windows-1251?B?0e5j8uDi6+Xt6OUg9OjtYe3xb+Lu6SDu8vfl8u1v8fLoIO9vIOzl5uTz7WFw7uTt++wgY/Jh7eTg8PLg7A==?=) Date: Mon, 20 May 2013 15:48:25 +0400 Subject: [atlas] =?windows-1251?b?zOXm5PPt4PDu5O375SDx8uDt5GHw8vsg9Ojt4O3x?= =?windows-1251?b?7uLu6SBv8vfl8u1v8fLoICjM0dRPKQ==?= Message-ID: <985359794.20130520110477@server.rurki.com> An HTML attachment was scrubbed... URL: From madis555 at hot.ee Tue May 21 07:37:54 2013 From: madis555 at hot.ee (Sulev-Madis Silber) Date: Tue, 21 May 2013 08:37:54 +0300 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <5199997B.7080008@hot.ee> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <6F642DEF-1425-4FD6-A98C-CE93A076E1B3@me.com> <51975F83.2000801@hot.ee> <519761C4.1000504@ripe.net> <51976B83.1050605@laurent-wattieaux.com> <5199997B.7080008@hot.ee> Message-ID: <519B0832.4090600@hot.ee> Update. After pulling the plug, ICMP ping suddenly works from everywhere? WHAT? And probe runs all fine tests again... On 2013-05-20 06:33, Sulev-Madis Silber wrote: > What the hell is going on there? It's in "can't send" state again. And I > somehow remember I could ping it outside of it's /64, now I can't. It > doesn't respond. However now it answers to ICMP ping (inside of it's > /64) and also talks NDP like it should. > From antony at ripe.net Tue May 21 09:17:08 2013 From: antony at ripe.net (Antony Antony) Date: Tue, 21 May 2013 09:17:08 +0200 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <5198E863.7090604@fud.no> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <5198E863.7090604@fud.no> Message-ID: <20130521071708.GA15900@kitten.ripe.net> Hi Tore, Could you please unplug the ethernet cable and re-plug again? I want see if it repeats systematically. The last time after a reboot your probe had a Global V6 address for about an hour (~64 minutes) and after that the probe unconfigured all V6 addresses. Olaf Maunz, Now I see IPv6 on you probe V6 measurements are working again. May be it rebooted on its own. I will look into the details later. Laurent Wattieaux, could you please let me know your Probe ID. You could drop me a private mail if you prefer that. We have seen this on couple of probes, however, yet figure out the details and a solution. We know the place were we saw the issue, it repeats. So it is good to have few more cases reported. May be we can use your help to debug and solve the problem. Thanks for all reports. We will increase the priority of chasing this bug. So far the symptom is after a reboot, some time later the probe unconfigure all V6 addresses. The case were we saw it most frequently was using a Fritz Boz 7270; i think. There is no userland client for RA so it is a bit hard to debug. We are trying add code to report the RA announcements seen by the probe. regards, -antony On Sun, May 19, 2013 at 04:57:39PM +0200, Tore Anderson wrote: > * Daniel Karrenberg > > > Thank you for letting us know and also for speaking up to let us know > > this happens to more than one of you. We will look at this after the > > holiday weekend. In the meantime it would help to know the type of > > the routers and details about your IPv6 routing configuration. > > FYI, in case you want to debug this problem present on a live probe, it > appears to be the case for probe 121 at the moment. It's connected > behind an AVM Fritzbox using SLAAC. No other devices connected to it > have a similar problem. > > The probe should have had the IPv6 address > 2a02:fe0:cf16:70:220:4aff:fec6:cd7a (which actually shows up on the > probe's web page), but it does not respond to anything - not to ICMPv6 > NS from the local link to the aforementioned address, nor to > fe80::220:4aff:fec6:cd7a. No responses from its link-local address is > seen when pinging ff02::1 either. All the default measurements says > "Cannot send". > > If you have no use for this debugging opportunity, let me know and I'll > reboot the probe and see if its IPv6 connectivity comes back then. > > Tore > > From robert at ripe.net Tue May 21 09:42:54 2013 From: robert at ripe.net (Robert Kisteleki) Date: Tue, 21 May 2013 09:42:54 +0200 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <519B0832.4090600@hot.ee> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <6F642DEF-1425-4FD6-A98C-CE93A076E1B3@me.com> <51975F83.2000801@hot.ee> <519761C4.1000504@ripe.net> <51976B83.1050605@laurent-wattieaux.com> <5199997B.7080008@hot.ee> <519B0832.4090600@hot.ee> Message-ID: <519B257E.4000705@ripe.net> Hi, We'll work on fixing this issue. Please, if someone has a reilable way of reproducing the condition, send it to atlas-bugs at ripe.net. Thank you! On 2013.05.21. 7:37, Sulev-Madis Silber wrote: > Update. > > After pulling the plug, ICMP ping suddenly works from everywhere? WHAT? > > And probe runs all fine tests again... If you power cycle the probe, then it restarts it state too, meaning DHCP leases, SLAAC, whatever. That works all the time, but it's not very convenient... and it should be fixed. Cheers, Robert > On 2013-05-20 06:33, Sulev-Madis Silber wrote: >> What the hell is going on there? It's in "can't send" state again. And I >> somehow remember I could ping it outside of it's /64, now I can't. It >> doesn't respond. However now it answers to ICMP ping (inside of it's >> /64) and also talks NDP like it should. >> > > From tore at fud.no Tue May 21 10:15:01 2013 From: tore at fud.no (Tore Anderson) Date: Tue, 21 May 2013 10:15:01 +0200 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <20130521071708.GA15900@kitten.ripe.net> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <5198E863.7090604@fud.no> <20130521071708.GA15900@kitten.ripe.net> Message-ID: <519B2D05.2050302@fud.no> * Antony Antony > Could you please unplug the ethernet cable and re-plug again? I want > see if it repeats systematically. The last time after a reboot your > probe had a Global V6 address for about an hour (~64 minutes) and > after that the probe unconfigured all V6 addresses. Done. Note that I did not unplug the USB cable, so the probe remained powered all the time. Tore From daniel.karrenberg at ripe.net Tue May 21 13:32:08 2013 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Tue, 21 May 2013 13:32:08 +0200 Subject: [atlas] (OT) RIPE PTR zone damaged in the last few days? In-Reply-To: <5197A7A5.6080502@grobecker.info> References: <5197A7A5.6080502@grobecker.info> Message-ID: Max, this really looks bogus to me, or at least "venturesome". Based on what you wrote we can not take any action. If your friend wants to take it up with us, please ask him to contact dns-help at ripe.net or, if he prefers, myself. I can read and write German in case that helps. Mit freundlichem Gruss Daniel From antony at ripe.net Tue May 21 15:39:15 2013 From: antony at ripe.net (Antony Antony) Date: Tue, 21 May 2013 15:39:15 +0200 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <519B2D05.2050302@fud.no> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <5198E863.7090604@fud.no> <20130521071708.GA15900@kitten.ripe.net> <519B2D05.2050302@fud.no> Message-ID: <20130521133915.GA10094@puppy.ripe.net> Hi Tore, Yes I was hopping just unplugging the Ethernet cable would fix it temporally. and we can reproduce it again. It seems that was not enough. So lets reboot, unplug the USB an replug it, and if the problem re-appear shortly after that you could try to move to another v6 router? The logs show the laster time it for ~6 hours ors and then the probe dropped its Global V6 address Do you have another V6 router where you can plug it in regards, -antony On Tue, May 21, 2013 at 10:15:01AM +0200, Tore Anderson wrote: > * Antony Antony > > > Could you please unplug the ethernet cable and re-plug again? I want > > see if it repeats systematically. The last time after a reboot your > > probe had a Global V6 address for about an hour (~64 minutes) and > > after that the probe unconfigured all V6 addresses. > > Done. Note that I did not unplug the USB cable, so the probe remained > powered all the time. > > Tore > > From tore at fud.no Tue May 21 15:56:09 2013 From: tore at fud.no (Tore Anderson) Date: Tue, 21 May 2013 15:56:09 +0200 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <20130521133915.GA10094@puppy.ripe.net> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <5198E863.7090604@fud.no> <20130521071708.GA15900@kitten.ripe.net> <519B2D05.2050302@fud.no> <20130521133915.GA10094@puppy.ripe.net> Message-ID: <519B7CF9.7080507@fud.no> * Antony Antony > Hi Tore, Yes I was hopping just unplugging the Ethernet cable would > fix it temporally. and we can reproduce it again. It seems that was > not enough. So lets reboot, unplug the USB an replug it, and if the > problem re-appear shortly after that you could try to move to > another v6 router? The logs show the laster time it for ~6 hours ors > and then the probe dropped its Global V6 address Not just the global one, as I mentioned earlier it had stopped responding to link-local pings as well. It seemed like the entire IPv6 stack was dead, to be honest. In any case, I rebooted it now and now it responds fine to IPv6 pings again, both to its global and link-local addresses. > Do you have another V6 router where you can plug it in Not at home, but I can connect it straight to my ISP's cable modem via a L2 switch (not behind my HGW as it is today). However my ISP does not use SLAAC, only DHCPv6 IA_NA - I don't know if the Atlas probes have gotten support for this nowadays? Otherwise I could always bring the probe to work and connect it there. Tore From curriculum.vitae at juliadelatorre.info Tue May 21 17:23:15 2013 From: curriculum.vitae at juliadelatorre.info (Julia) Date: Tue, 21 May 2013 17:23:15 +0200 Subject: [atlas] =?iso-8859-1?q?CV_para_su_amable_consideraci=F3n?= Message-ID: <519B9163.3070601@juliadelatorre.info> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: gr?ficos1 Type: image/gif Size: 10726 bytes Desc: not available URL: From mick.odonovan at bt.com Wed May 22 16:16:39 2013 From: mick.odonovan at bt.com (mick.odonovan at bt.com) Date: Wed, 22 May 2013 15:16:39 +0100 Subject: [atlas] [ripe.net #1087039] New Probe Deployment In-Reply-To: References: Message-ID: Hi Alastair, Any more information on this? I have a packet capture running most of the day and I can see connection initiations between 178.63.78.18 and the probe but still my probe appears as "disconnected" on atlas.ripe.net Appreciate any help you can lend in getting the probe online. Thanks, Mick -----Original Message----- From: Alastair Strachan [mailto:atlas at ripe.net] Sent: 21 May 2013 14:47 To: O'Donovan,M,Mick,MWE22E R Subject: [ripe.net #1087039] New Probe Deployment Hello Mick, Thanks for your email. The probe itself should be visible when you are logged into the Atlas website. I can see from the system the probe has not yet been able to connected outside your network. Please ensure all firewalls/security software has been amended to allow the probe a clean connection outside your network. If you do have any further questions, please do not hesitate to contact us. Thank you for taking the time to host an Atlas probe. Kind Regards, Alastair Strachan RIPE Atlas Team On Mon May 20 11:10:49 2013, mick.odonovan at bt.com wrote: > Hi Atlas team, > > Fresh from RIPE66 meeting I've just deployed my new atlas probe this > morning and can see it's pingable locally on the network with it's > dhcp'ed address. > > I am just wondering now however how long it takes before this probe > should be visible at http://atlas.ripe.net as I need to give it a > fixed IP address for live network deployment. > > Thanks in advance, > > Mick > > > > Mick O?Donovan | Network Engineer | Core & Access Operations | BT > Ireland | Block C, Dundrum Business Park, Dublin 14, Ireland | > Phone: +353 1 4326480 | Mob: +353 863870425 | BT MeetMe +353 > 12421053 ? 1800946924 > PartCode: 75039807# |E: mick.odonovan at bt.com | Web: www.btireland.ie > > Planned Absence: > > This e-mail and any files transmitted with it are confidential and may > be privileged and are intended solely for the use of the > individual(s) or entity to whom they are addressed. As email can be > subject to operational or technical difficulties and time delays, > communications that are subject to deadlines should also be sent by > post. Any unauthorised direct or indirect dissemination, > distribution or copying of this message and any attachments is > strictly prohibited. If you have received this e-mail in error, > please let me know immediately on the e-mail address above and > delete the e-mail from your system. Thank you for your co- > operation. > > BT accepts no responsibility for changes to or interception of this e- > mail after it was sent or for any damage to the recipient?s systems > or data caused by this message or its attachments. We monitor our > e-mail system, and may record your e-mails. This e-mail shall not > constitute a binding contract. > > BT Ireland, trading in Republic of Ireland as BT Communications > Ireland Limited. Registered office: Grand Canal Plaza, Upper Grand > Canal Street, Dublin 4, Registered in Ireland no 141524 and trading > in Northern Ireland as British Telecommunications plc. Registered > office: 81 Newgate Street London EC1A 7AJ Registered in England > no: 1800000, both being affiliates of BT Group plc. > ? Please don't print this e-mail unless you really need to > > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8232 bytes Desc: not available URL: From madis555 at hot.ee Thu May 23 04:09:27 2013 From: madis555 at hot.ee (Sulev-Madis Silber) Date: Thu, 23 May 2013 05:09:27 +0300 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <5199997B.7080008@hot.ee> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <6F642DEF-1425-4FD6-A98C-CE93A076E1B3@me.com> <51975F83.2000801@hot.ee> <519761C4.1000504@ripe.net> <51976B83.1050605@laurent-wattieaux.com> <5199997B.7080008@hot.ee> Message-ID: <519D7A57.6080808@hot.ee> Here it goes again?! Global address unpingable and probe is even marked as disconnected, maybe it will try to reconnect over IPv4 later. Nothing like this happened before. Something is broken there I'm afraid. It's all the same router and everything. On 2013-05-20 06:33, Sulev-Madis Silber wrote: > What the hell is going on there? It's in "can't send" state again. And I > somehow remember I could ping it outside of it's /64, now I can't. It > doesn't respond. However now it answers to ICMP ping (inside of it's > /64) and also talks NDP like it should. > From antony at ripe.net Thu May 23 10:56:53 2013 From: antony at ripe.net (Antony Antony) Date: Thu, 23 May 2013 10:56:53 +0200 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <519D7A57.6080808@hot.ee> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <6F642DEF-1425-4FD6-A98C-CE93A076E1B3@me.com> <51975F83.2000801@hot.ee> <519761C4.1000504@ripe.net> <51976B83.1050605@laurent-wattieaux.com> <5199997B.7080008@hot.ee> <519D7A57.6080808@hot.ee> Message-ID: <20130523085653.GA29686@puppy.ripe.net> Dear Silber, may be at your location the problem is a bit more frequent? The other place i was watching, Tore's probe, is happy for 3 days. I am not sure this time it is address configuration error. If you look at the graphs of your probe #4415. I see a different pattern now. It is not Yellow, can't sent error, any more. Compare it on the weekly graph, week 19-20 and now. May be some other issue? So far, from my experience, Red is not IPv6 address disappearing error. Only a series of good results and yellow is the sign. For details, you could download the data and look at it more closely. For example, look at the measurement ID 2001 pinging the K-root. Now it is working fine. The last time the error occurred for a few measurements and it seems to have recovered on its own. The timestamp of the error is "time":1369197942 Never the less, we are sure there is an IPv6 RA related problem that affect a few probes. We are trying figure out a solution. However, the harder part is to reproduce it in a controlled environment where we have access and create a solution. The wired thing about this bug is there is one place with two probes on a same router and only one of them occasionally run into this problem. regards, -antony On Thu, May 23, 2013 at 05:09:27AM +0300, Sulev-Madis Silber wrote: > Here it goes again?! Global address unpingable and probe is even marked > as disconnected, maybe it will try to reconnect over IPv4 later. Nothing > like this happened before. Something is broken there I'm afraid. It's > all the same router and everything. > > > On 2013-05-20 06:33, Sulev-Madis Silber wrote: > > What the hell is going on there? It's in "can't send" state again. And I > > somehow remember I could ping it outside of it's /64, now I can't. It > > doesn't respond. However now it answers to ICMP ping (inside of it's > > /64) and also talks NDP like it should. > > > > From tore at fud.no Thu May 23 11:19:43 2013 From: tore at fud.no (Tore Anderson) Date: Thu, 23 May 2013 11:19:43 +0200 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <20130523085653.GA29686@puppy.ripe.net> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <6F642DEF-1425-4FD6-A98C-CE93A076E1B3@me.com> <51975F83.2000801@hot.ee> <519761C4.1000504@ripe.net> <51976B83.1050605@laurent-wattieaux.com> <5199997B.7080008@hot.ee> <519D7A57.6080808@hot.ee> <20130523085653.GA29686@puppy.ripe.net> Message-ID: <519DDF2F.5000108@fud.no> * Antony Antony > Never the less, we are sure there is an IPv6 RA related problem that > affect a few probes. Just to highlight a data point I've mentioned before: My probe did not even respond to pings to its link local address. The link local address is *not* dependent on, or initialised based on IPv6 RAs; it is always present on all interfaces with an IPv6 stack active. For this reason I strongly suspect that the problem is found deeper down in the stack then ICMPv6 RA processing is. Best regards, Tore Anderson From olaf.maunz at me.com Thu May 23 11:20:37 2013 From: olaf.maunz at me.com (Olaf Maunz) Date: Thu, 23 May 2013 10:20:37 +0100 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <20130523085653.GA29686@puppy.ripe.net> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <6F642DEF-1425-4FD6-A98C-CE93A076E1B3@me.com> <51975F83.2000801@hot.ee> <519761C4.1000504@ripe.net> <51976B83.1050605@laurent-wattieaux.com> <5199997B.7080008@hot.ee> <519D7A57.6080808@hot.ee> <20130523085653.GA29686@puppy.ripe.net> Message-ID: Just thoughts. And can't really confirm it at the moment. I am having the feeling that it depends on the simultaneous reboot of the probe and the router and some timed boot sequences. I can not reproduce it at the moment but when the probe's USB was plugged in the router and the entire router unplugged and restarted IPv6 failed. With the probe plugged into a different power source no IPv6 problems occurred when the router was power cycled. Each device at its own reboot fine with me. The problem might be when the probe reboots and the router is an undefined state. Sent from my iPhone On 23 May 2013, at 09:56, Antony Antony wrote: > Dear Silber, > > may be at your location the problem is a bit more frequent? The other place i was watching, Tore's probe, is happy for 3 days. I am not sure this time it is address configuration error. If you look at the graphs of your probe #4415. I see a different pattern now. It is not Yellow, can't sent error, any more. Compare it on the weekly graph, week 19-20 and now. May be some other issue? > > So far, from my experience, Red is not IPv6 address disappearing error. Only a series of good results and yellow is the sign. > > For details, you could download the data and look at it more closely. For example, look at the measurement ID 2001 pinging the K-root. Now it is working fine. The last time the error occurred for a few measurements and it seems to have recovered on its own. The timestamp of the error is "time":1369197942 > > Never the less, we are sure there is an IPv6 RA related problem that affect a few probes. We are trying figure out a solution. However, the harder part is to reproduce it in a controlled environment where we have access and create a solution. > > The wired thing about this bug is there is one place with two probes on a same router and only one of them occasionally run into this problem. > > regards, > -antony > > > On Thu, May 23, 2013 at 05:09:27AM +0300, Sulev-Madis Silber wrote: >> Here it goes again?! Global address unpingable and probe is even marked >> as disconnected, maybe it will try to reconnect over IPv4 later. Nothing >> like this happened before. Something is broken there I'm afraid. It's >> all the same router and everything. >> >> >> On 2013-05-20 06:33, Sulev-Madis Silber wrote: >>> What the hell is going on there? It's in "can't send" state again. And I >>> somehow remember I could ping it outside of it's /64, now I can't. It >>> doesn't respond. However now it answers to ICMP ping (inside of it's >>> /64) and also talks NDP like it should. >>> >> >> > From alexsaroyan at gmail.com Thu May 23 13:41:10 2013 From: alexsaroyan at gmail.com (Alex Saroyan) Date: Thu, 23 May 2013 15:41:10 +0400 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador Message-ID: <519E0056.8010508@gmail.com> Hi, I'm not sure, but seems that if the probe was initially assigned to ambassador then ambassador assigned to the host the probe in not appearing in host's account. Example 1 Probe F81A674D7482 was assigned to levon.avagyan at gmail.com by me ambassador alex.saroyan at gmail.com. In Ambassador page I see this probe as "Online, not hosted", and host does not see the probe on his account at all. Example 2 Probe A0F3C1C44063 was assigned to surenispiryan at gmail.com again by me ambassador alex.saroyan at gmail.com. He didn't connect the probe yet to network. In Ambassador page I see the probe status "Applied" and host does not see the probe in his account under "my probes" at all. Regards. /Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From fearghas at gmail.com Thu May 23 13:52:19 2013 From: fearghas at gmail.com (Fearghas McKay) Date: Thu, 23 May 2013 12:52:19 +0100 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador In-Reply-To: <519E0056.8010508@gmail.com> References: <519E0056.8010508@gmail.com> Message-ID: <1DF9FD6B-FCBA-4A82-A44E-96B3C8DAD312@gmail.com> Hi I am seeing issues with probes handed out and registered both by myself and the recipient. They are then showing as online but not hosted. f On 23 May 2013, at 12:41, Alex Saroyan wrote: > Hi, > > I'm not sure, but seems that if the probe was initially assigned to ambassador then ambassador assigned to the host the probe in not appearing in host's account. > > > Example 1 > Probe F81A674D7482 was assigned to levon.avagyan at gmail.com by me ambassador alex.saroyan at gmail.com. > In Ambassador page I see this probe as "Online, not hosted", and host does not see the probe on his account at all. > > Example 2 > Probe A0F3C1C44063 was assigned to surenispiryan at gmail.com again by me ambassador alex.saroyan at gmail.com. > He didn't connect the probe yet to network. > In Ambassador page I see the probe status "Applied" and host does not see the probe in his account under "my probes" at all. > > Regards. > /Alex From robert at ripe.net Thu May 23 14:01:03 2013 From: robert at ripe.net (Robert Kisteleki) Date: Thu, 23 May 2013 14:01:03 +0200 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador In-Reply-To: <519E0056.8010508@gmail.com> References: <519E0056.8010508@gmail.com> Message-ID: <519E04FF.8070708@ripe.net> Hi, On 2013.05.23. 13:41, Alex Saroyan wrote: > Hi, > > I'm not sure, but seems that if the probe was initially assigned to > ambassador then ambassador assigned to the host the probe in not appearing > in host's account. > > > Example 1 > Probe F81A674D7482 was assigned to levon.avagyan at gmail.com by me ambassador > alex.saroyan at gmail.com. > In Ambassador page I see this probe as "Online, not hosted", and host does > not see the probe on his account at all. That means it's plugged in, but the host did not register it yet. He/she will not see the probe in his/her list until then. > Example 2 > Probe A0F3C1C44063 was assigned to surenispiryan at gmail.com again by me > ambassador alex.saroyan at gmail.com. > He didn't connect the probe yet to network. > In Ambassador page I see the probe status "Applied" and host does not see > the probe in his account under "my probes" at all. This person applied/registered. As long as the MAC+email combination matches what the ambassador said, the process is automatic in about 30 minutes. If they don't match we have to do something manually, so it takes more time. Hope this explains, Robert > Regards. > /Alex From robert at ripe.net Thu May 23 14:01:42 2013 From: robert at ripe.net (Robert Kisteleki) Date: Thu, 23 May 2013 14:01:42 +0200 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador In-Reply-To: <1DF9FD6B-FCBA-4A82-A44E-96B3C8DAD312@gmail.com> References: <519E0056.8010508@gmail.com> <1DF9FD6B-FCBA-4A82-A44E-96B3C8DAD312@gmail.com> Message-ID: <519E0526.2060300@ripe.net> Hi, On 2013.05.23. 13:52, Fearghas McKay wrote: > Hi > > I am seeing issues with probes handed out and registered both by myself and the recipient. > > They are then showing as online but not hosted. See the previous mail -- this means that the host plugged the probe in but haven't registered it yet. Regards, Robert > f > > On 23 May 2013, at 12:41, Alex Saroyan wrote: > >> Hi, >> >> I'm not sure, but seems that if the probe was initially assigned to ambassador then ambassador assigned to the host the probe in not appearing in host's account. >> >> >> Example 1 >> Probe F81A674D7482 was assigned to levon.avagyan at gmail.com by me ambassador alex.saroyan at gmail.com. >> In Ambassador page I see this probe as "Online, not hosted", and host does not see the probe on his account at all. >> >> Example 2 >> Probe A0F3C1C44063 was assigned to surenispiryan at gmail.com again by me ambassador alex.saroyan at gmail.com. >> He didn't connect the probe yet to network. >> In Ambassador page I see the probe status "Applied" and host does not see the probe in his account under "my probes" at all. >> >> Regards. >> /Alex > > > From fearghas at gmail.com Thu May 23 14:13:04 2013 From: fearghas at gmail.com (Fearghas McKay) Date: Thu, 23 May 2013 13:13:04 +0100 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador In-Reply-To: <519E04FF.8070708@ripe.net> References: <519E0056.8010508@gmail.com> <519E04FF.8070708@ripe.net> Message-ID: <5D5133A9-2A07-4FA7-AE88-0E023F64FFA6@gmail.com> On 23 May 2013, at 13:01, Robert Kisteleki wrote: > This person applied/registered. As long as the MAC+email combination matches > what the ambassador said, the process is automatic in about 30 minutes. If > they don't match we have to do something manually, so it takes more time. Then this goes against what I was told as an Ambassador, that it didn't matter if the addresses were different. ~half of the probes I have handed out will probably be using different addresses. Perhaps the 30 minutes information could be updated to let people know that there may be a difference. Thanks f From alexsaroyan at gmail.com Thu May 23 14:16:38 2013 From: alexsaroyan at gmail.com (Alex Saroyan) Date: Thu, 23 May 2013 16:16:38 +0400 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador In-Reply-To: <5D5133A9-2A07-4FA7-AE88-0E023F64FFA6@gmail.com> References: <519E0056.8010508@gmail.com> <519E04FF.8070708@ripe.net> <5D5133A9-2A07-4FA7-AE88-0E023F64FFA6@gmail.com> Message-ID: <519E08A6.4080309@gmail.com> Hi, Actually both my initial examples waited much more then 30 minutes. One case was resolved by Alastair yesterday, why I wrote here now on the mailing list because seems this is global problem. Regards. /Alex On 05/23/2013 04:13 PM, Fearghas McKay wrote: > On 23 May 2013, at 13:01, Robert Kisteleki wrote: > >> This person applied/registered. As long as the MAC+email combination matches >> what the ambassador said, the process is automatic in about 30 minutes. If >> they don't match we have to do something manually, so it takes more time. > Then this goes against what I was told as an Ambassador, that it didn't matter if the addresses were different. ~half of the probes I have handed out will probably be using different addresses. Perhaps the 30 minutes information could be updated to let people know that there may be a difference. > > Thanks > > f > > From levon.avagyan at gmail.com Thu May 23 14:15:33 2013 From: levon.avagyan at gmail.com (Levon Avagyan) Date: Thu, 23 May 2013 17:15:33 +0500 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador In-Reply-To: <5D5133A9-2A07-4FA7-AE88-0E023F64FFA6@gmail.com> References: <519E0056.8010508@gmail.com> <519E04FF.8070708@ripe.net> <5D5133A9-2A07-4FA7-AE88-0E023F64FFA6@gmail.com> Message-ID: Hi Robert, The thing is that i've already registered that probe on my page and received confirmation email from the system. Providing the email I've received below: >>>>>>>>>>>>>>>>>> Dear Levon Avagyan, Thank you for registering your RIPE Atlas probe! All you need to do now is plug it in. You can find instructions online on how to do this, along with other helpful information (you have already completed steps 1 and 2, so please jump to step 3): atlas.ripe.net/getting-started We also have a FAQ section that should cover any queries you have: https://atlas.ripe.net/faq If you have any further questions, please do not hesitate to contact us at atlas at ripe.net Thank you for being part of the RIPE Atlas network. Kind regards, RIPE Atlas Team >>>>>>>>>>>>>>>>> Best regards Levon Avagyan On Thu, May 23, 2013 at 4:01 PM, Robert Kisteleki wrote: > Hi, > > On 2013.05.23. 13:52, Fearghas McKay wrote: > > Hi > > > > I am seeing issues with probes handed out and registered both by myself > and the recipient. > > > > They are then showing as online but not hosted. > > See the previous mail -- this means that the host plugged the probe in but > haven't registered it yet. > > Regards, > Robert > > > f > > > > On 23 May 2013, at 12:41, Alex Saroyan wrote: > > > >> Hi, > >> > >> I'm not sure, but seems that if the probe was initially assigned to > ambassador then ambassador assigned to the host the probe in not appearing > in host's account. > >> > >> > >> Example 1 > >> Probe F81A674D7482 was assigned to levon.avagyan at gmail.com by me > ambassador alex.saroyan at gmail.com. > >> In Ambassador page I see this probe as "Online, not hosted", and host > does not see the probe on his account at all. > >> > >> Example 2 > >> Probe A0F3C1C44063 was assigned to surenispiryan at gmail.com again by me > ambassador alex.saroyan at gmail.com. > >> He didn't connect the probe yet to network. > >> In Ambassador page I see the probe status "Applied" and host does not > see the probe in his account under "my probes" at all. > >> > >> Regards. > >> /Alex > > > > > > > > > Best regards Levon Avagyan On Thu, May 23, 2013 at 4:13 PM, Fearghas McKay wrote: > > On 23 May 2013, at 13:01, Robert Kisteleki wrote: > > > This person applied/registered. As long as the MAC+email combination > matches > > what the ambassador said, the process is automatic in about 30 minutes. > If > > they don't match we have to do something manually, so it takes more time. > > Then this goes against what I was told as an Ambassador, that it didn't > matter if the addresses were different. ~half of the probes I have handed > out will probably be using different addresses. Perhaps the 30 minutes > information could be updated to let people know that there may be a > difference. > > Thanks > > f > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert at ripe.net Thu May 23 14:42:22 2013 From: robert at ripe.net (Robert Kisteleki) Date: Thu, 23 May 2013 14:42:22 +0200 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador In-Reply-To: References: <519E0056.8010508@gmail.com> <519E04FF.8070708@ripe.net> <5D5133A9-2A07-4FA7-AE88-0E023F64FFA6@gmail.com> Message-ID: <519E0EAE.1010709@ripe.net> On 2013.05.23. 14:15, Levon Avagyan wrote: > Hi Robert, > > The thing is that i've already registered that probe on my page and received > confirmation email from the system. > > Providing the email I've received below: Hi, It's possible that we have a bug in the procedure somewhere, though previously we haven't seen evidence of it. We'll check what's going on in these cases and get back to you. Regards, Robert From lorenzo at google.com Thu May 23 14:39:16 2013 From: lorenzo at google.com (Lorenzo Colitti) Date: Thu, 23 May 2013 21:39:16 +0900 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <519DDF2F.5000108@fud.no> References: <51955E80.9020703@hot.ee> <70026C5B-1FEF-4821-AD4D-40B8F98DF151@me.com> <51965B9B.2050004@laurent-wattieaux.com> <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <6F642DEF-1425-4FD6-A98C-CE93A076E1B3@me.com> <51975F83.2000801@hot.ee> <519761C4.1000504@ripe.net> <51976B83.1050605@laurent-wattieaux.com> <5199997B.7080008@hot.ee> <519D7A57.6080808@hot.ee> <20130523085653.GA29686@puppy.ripe.net> <519DDF2F.5000108@fud.no> Message-ID: On Thu, May 23, 2013 at 6:19 PM, Tore Anderson wrote: > Just to highlight a data point I've mentioned before: My probe did not > even respond to pings to its link local address. The link local address > is *not* dependent on, or initialised based on IPv6 RAs; it is always > present on all interfaces with an IPv6 stack active. > Did it fail DAD on the link-local address, then? -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexsaroyan at gmail.com Thu May 23 14:49:25 2013 From: alexsaroyan at gmail.com (Alex Saroyan) Date: Thu, 23 May 2013 16:49:25 +0400 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador In-Reply-To: <519E0EAE.1010709@ripe.net> References: <519E0056.8010508@gmail.com> <519E04FF.8070708@ripe.net> <5D5133A9-2A07-4FA7-AE88-0E023F64FFA6@gmail.com> <519E0EAE.1010709@ripe.net> Message-ID: <519E1055.3030700@gmail.com> If you need anything to be tested or redo from our side feel free to ask, we are looking forward to help during the troubleshooting. For me it is more important the bug to be fixed then to solve the particular problem. Also please take into consideration that Alastair Strachan is also working on the case #1087274 regards. /Alex On 05/23/2013 04:42 PM, Robert Kisteleki wrote: > On 2013.05.23. 14:15, Levon Avagyan wrote: >> Hi Robert, >> >> The thing is that i've already registered that probe on my page and received >> confirmation email from the system. >> >> Providing the email I've received below: > Hi, > > It's possible that we have a bug in the procedure somewhere, though > previously we haven't seen evidence of it. We'll check what's going on in > these cases and get back to you. > > Regards, > Robert > > From levon.avagyan at gmail.com Thu May 23 14:53:53 2013 From: levon.avagyan at gmail.com (Levon Avagyan) Date: Thu, 23 May 2013 17:53:53 +0500 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador In-Reply-To: <519E1055.3030700@gmail.com> References: <519E0056.8010508@gmail.com> <519E04FF.8070708@ripe.net> <5D5133A9-2A07-4FA7-AE88-0E023F64FFA6@gmail.com> <519E0EAE.1010709@ripe.net> <519E1055.3030700@gmail.com> Message-ID: Hi, My probe has just started to show in My probes page, my probe's mac address is F8:1A:67:4D:74:82 Best regards Levon Avagyan On Thu, May 23, 2013 at 4:49 PM, Alex Saroyan wrote: > If you need anything to be tested or redo from our side feel free to ask, > we are looking forward to help during the troubleshooting. > > For me it is more important the bug to be fixed then to solve the > particular problem. > Also please take into consideration that Alastair Strachan is also working > on the case #1087274 > > regards. > /Alex > > > > > On 05/23/2013 04:42 PM, Robert Kisteleki wrote: > >> On 2013.05.23. 14:15, Levon Avagyan wrote: >> >>> Hi Robert, >>> >>> The thing is that i've already registered that probe on my page and >>> received >>> confirmation email from the system. >>> >>> Providing the email I've received below: >>> >> Hi, >> >> It's possible that we have a bug in the procedure somewhere, though >> previously we haven't seen evidence of it. We'll check what's going on in >> these cases and get back to you. >> >> Regards, >> Robert >> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From office at spseminar.net.ua Thu May 23 15:42:55 2013 From: office at spseminar.net.ua (Sales Department) Date: Thu, 23 May 2013 16:42:55 +0300 Subject: [atlas] =?koi8-r?b?6M/a0cnOIPPVxNjC2Q==?= Message-ID: <836320DDEFCE47EE82D11A69704B67D6@grad-add-186.terabit.com.ua> ???????: ?????? ?????? ?????? ??????? ????? "?????? ??????" ?? ?????? ?????? ? ??????? ?????? ?????? - ??? ?????? ?? ????????????? ????????? ?????, ???? ?? ????? ???????? ????????? ??????????? ? ????? ????????? ??????, ? ?????? ? ???????! ??????, ?????????? ???????? ? ??????????? ????????????? ?????????? ?? ????? ????! "?????? ??????" - ??? ?????? ?????????????, ??? ????? ??????????? ? ???????????, ??? ????? ???? ????????? ??????, ??????????????, ?????????????, ??????????????? ? ?????????? ????????, ???, ???????????? ??????????, ?????????? ?????????, ???????? ? ???????????????? ??????????. ??? ?????????? ? ?????????? ?? ???????? ??????? ???????? ????? ????? ??????????. ? ?????????: - "?????" ??? ?????? ?????????? ????. - ???? ???????? ? ????? ?? ???. - "????? ????????" - ??? ?? ????????? ? ???????????? ????????? ???????. - ???????? ????????????? ???????? ?????? ???????. - ?????????? ? ?????????? ???????????? ?????. ????? ? ????????? ????????. - ??????? ?????????? ????. - "?????? ???????????? ????????". ?????? ? ??? ???? ?????? ???? ? ??????, ????? ?????. - ???????? ? ????. - ??????????????? ??? ?????????? ?????? ? ??????? ?? ????? ??????? ???????. - ???????? ?????? ? ?????????????? ???????????. - ??????? ???????? ?????????????? ????????? ???. - ???????? ???????? ??????????? ???????. - ??????????? ? ??????? ?????. - ?????????? ?? ???????. ?? ???????????, ??? ??????????? ????? ????? ???????????? ?????????? ? ??????????. ??? ?? ????? ????????? "????? ????????????" ??????? ????????? ? ?????????. ???????? ?? ??, ??? ????? ??????? ?? ??? ?????? ???????? ?????? ???????????, ?????? ????? ?????? ?????? ?? ???? ???????? "?????", ??????? ????? ?????? "??????????" ??? ?? ?????. ?????????? ? ???????: ?????? ????? - ??????? ?????? No1, ????? ??????? "?????? ??????", ?????????, ????????, ??????? ?????????? ???????, ???????????????? ??????-??????, ????, ?????????. ????? ???? "????????????", "???? ?????? ????", "??? ????? ??????? - 35 ??????? ?????? ????????", "??????? ?????", "??? ??????? ?????????????? ????????", "???????? ? ????????????? ????????????", "????? ??????" ??????? ????????? ???????????????: ???????? ??????-???????????? ??????????; ?????? ? ????????? ???????????? ?? ?????? ????????. ???? ? ????? ??????????: 25 ???. ?. ????, ????? ????, ?????????-??? Royal De Luxe Hotel ????????? ???????: 1400.00 ???. - ?? ?????? ?????????. ??? ??????? ? ???????? ????????? ?????? 5% ? 7% ?????????????? ?????? ????????: ??????????? ??????????: ? 10.15 ?? 10.50. ????? ??????????: ? 11.00 ?? 19.00. ????????? ???????: ? 14.30 ?? 15.30 ???? ?? ?? ?????? ???????? ?????????? ? ???????????? ? ????? ????????? ????????????, ?????????? ?? ?????? unsubscribe -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: header.jpg Type: image/jpeg Size: 34603 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: button_reg_now.jpg Type: image/jpeg Size: 9715 bytes Desc: not available URL: From steve at enta.net Thu May 23 17:49:46 2013 From: steve at enta.net (Steve Lalonde) Date: Thu, 23 May 2013 16:49:46 +0100 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador In-Reply-To: <5D5133A9-2A07-4FA7-AE88-0E023F64FFA6@gmail.com> References: <519E0056.8010508@gmail.com> <519E04FF.8070708@ripe.net> <5D5133A9-2A07-4FA7-AE88-0E023F64FFA6@gmail.com> Message-ID: Hi I now have 7 probes online in the last 24 hours (Thanks Fearghas), none of them show up in the "my probes" section yet they are 10614 10616 10622 10623 10624 10625 the 7th is in a different site so I can't read the ID from here. We are going to configure them with statics and deploy them to places on our network where there are no other probes geographically close. -- Steve Lalonde Chief Technical Officer Entanet International Ltd http://www.enta.net/ On 23 May 2013, at 13:13, Fearghas McKay wrote: > > On 23 May 2013, at 13:01, Robert Kisteleki wrote: > >> This person applied/registered. As long as the MAC+email combination matches >> what the ambassador said, the process is automatic in about 30 minutes. If >> they don't match we have to do something manually, so it takes more time. > > Then this goes against what I was told as an Ambassador, that it didn't matter if the addresses were different. ~half of the probes I have handed out will probably be using different addresses. Perhaps the 30 minutes information could be updated to let people know that there may be a difference. > > Thanks > > f > > From steve at enta.net Fri May 24 08:18:39 2013 From: steve at enta.net (Steve Lalonde) Date: Fri, 24 May 2013 07:18:39 +0100 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador In-Reply-To: References: <519E0056.8010508@gmail.com> <519E04FF.8070708@ripe.net> <5D5133A9-2A07-4FA7-AE88-0E023F64FFA6@gmail.com> Message-ID: <98B82E3E-EE94-4105-86C5-A7C38F346F7B@enta.net> Just for completeness the 7th probe is 10643 Steve On 23 May 2013, at 16:49, Steve Lalonde wrote: > Hi > > I now have 7 probes online in the last 24 hours (Thanks Fearghas), none of them show up in the "my probes" section yet > > they are > > 10614 > 10616 > 10622 > 10623 > 10624 > 10625 > > the 7th is in a different site so I can't read the ID from here. > > We are going to configure them with statics and deploy them to places on our network where there are no other probes geographically close. > > > -- > Steve Lalonde > Chief Technical Officer > Entanet International Ltd > http://www.enta.net/ > > > > On 23 May 2013, at 13:13, Fearghas McKay wrote: > >> >> On 23 May 2013, at 13:01, Robert Kisteleki wrote: >> >>> This person applied/registered. As long as the MAC+email combination matches >>> what the ambassador said, the process is automatic in about 30 minutes. If >>> they don't match we have to do something manually, so it takes more time. >> >> Then this goes against what I was told as an Ambassador, that it didn't matter if the addresses were different. ~half of the probes I have handed out will probably be using different addresses. Perhaps the 30 minutes information could be updated to let people know that there may be a difference. >> >> Thanks >> >> f >> >> > > From balz at Mathematik.Uni-Marburg.de Fri May 24 09:47:35 2013 From: balz at Mathematik.Uni-Marburg.de (balz at Mathematik.Uni-Marburg.de) Date: Fri, 24 May 2013 09:47:35 +0200 Subject: [atlas] Ripe atlas measurement issues Message-ID: <33875208a29998dd4d72ebee6ce8237f.squirrel@www.mathematik.uni-marburg.de> Hello Atlas team, I have a problem concerning downloads of measurement data from ripe atlas data. In order to evaluate some measurements, I use a script which downloads measurement data of the current week. This worked perfectly until the changes in the download section of ripe atlas. Since then, the urls are not considering time constraints and return measurement data from further in the past. My urls look like: https://udm01.atlas.ripe.net/api/v1/measurement/1000002/result/?filename=udmlog_1000026_2013_20.json&y=2013&w=20 I also tried the start_time parameter, instead of &y / &w but the problem stays the same. Did anyone experience similar issues and could help me out on this? Many thanks in advance. Best Regards, Alexander Balz From dquinn at ripe.net Fri May 24 11:18:14 2013 From: dquinn at ripe.net (Daniel Quinn) Date: Fri, 24 May 2013 11:18:14 +0200 Subject: [atlas] Ripe atlas measurement issues In-Reply-To: <33875208a29998dd4d72ebee6ce8237f.squirrel@www.mathematik.uni-marburg.de> References: <33875208a29998dd4d72ebee6ce8237f.squirrel@www.mathematik.uni-marburg.de> Message-ID: <519F3056.9080204@ripe.net> On 05/24/2013 09:47 AM, balz at Mathematik.Uni-Marburg.de wrote: > Since then, the urls are not considering time constraints and return > measurement data from further in the past. > My urls look like: > > https://udm01.atlas.ripe.net/api/v1/measurement/1000002/result/?filename=udmlog_1000026_2013_20.json&y=2013&w=20 This is due to the fact that we changed the old URL parameters to use whole words a short time ago. As this wasn't part of the official API, I didn't announce it, but you'll find if you use year=2013&week=20 it will perform as expected. I'm sorry that you got caught by this, but I'm hoping this will set you back on track. https://udm01.atlas.ripe.net/api/v1/measurement/1000002/result/?filename=udmlog_1000026_2013_20.json&year=2013&week=20 From antony at ripe.net Fri May 24 11:43:37 2013 From: antony at ripe.net (Antony Antony) Date: Fri, 24 May 2013 11:43:37 +0200 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: References: <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <6F642DEF-1425-4FD6-A98C-CE93A076E1B3@me.com> <51975F83.2000801@hot.ee> <519761C4.1000504@ripe.net> <51976B83.1050605@laurent-wattieaux.com> <5199997B.7080008@hot.ee> <519D7A57.6080808@hot.ee> <20130523085653.GA29686@puppy.ripe.net> <519DDF2F.5000108@fud.no> Message-ID: <20130524094337.GA6402@puppy.ripe.net> Hi, A quick update. DAD seems a good theory to look into. Thanks for the tip Lorenzo! I will try reproduce the issue. I see a similar error message as reported here when two Development probes are configured with the same link local and the same global IPv6 address. This idea has been around but we never got around verifying it thoroughly. We did not want create loops at RIPE NCC office network to verify it. So if it is true, some how the probe triggers Duplicate Address Detection(DAD) and disable it's own IPv6 address. May be due to temporary layer two loop? One puzzle is in some cases the probe disable the address after a while(it can be hours later, say 6 hours after a reboot) and in some other cases right after a reboot. Is the DAD continuously running in the Linux Kernel? or only when configuring an IPv6 address? I will try to figure out. I have herd other annoyances due DAD. regards, -antony On Thu, May 23, 2013 at 09:39:16PM +0900, Lorenzo Colitti wrote: > On Thu, May 23, 2013 at 6:19 PM, Tore Anderson wrote: > > > Just to highlight a data point I've mentioned before: My probe did not > > even respond to pings to its link local address. The link local address > > is *not* dependent on, or initialised based on IPv6 RAs; it is always > > present on all interfaces with an IPv6 stack active. > > > > Did it fail DAD on the link-local address, then? From tore at fud.no Fri May 24 12:31:47 2013 From: tore at fud.no (Tore Anderson) Date: Fri, 24 May 2013 12:31:47 +0200 Subject: [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure In-Reply-To: <20130524094337.GA6402@puppy.ripe.net> References: <40E93E97-772C-4F61-9CEC-FF7688466058@ripe.net> <6F642DEF-1425-4FD6-A98C-CE93A076E1B3@me.com> <51975F83.2000801@hot.ee> <519761C4.1000504@ripe.net> <51976B83.1050605@laurent-wattieaux.com> <5199997B.7080008@hot.ee> <519D7A57.6080808@hot.ee> <20130523085653.GA29686@puppy.ripe.net> <519DDF2F.5000108@fud.no> <20130524094337.GA6402@puppy.ripe.net> Message-ID: <519F4193.4060802@fud.no> * Antony Antony > DAD seems a good theory to look into. Thanks for the tip Lorenzo! I > will try reproduce the issue. Agreed, failing DAD could explain the problem. > This idea has been around but we never got around verifying it > thoroughly. We did not want create loops at RIPE NCC office network > to verify it. So if it is true, some how the probe triggers > Duplicate Address Detection(DAD) and disable it's own IPv6 address. > May be due to temporary layer two loop? One puzzle is in some cases > the probe disable the address after a while(it can be hours later, > say 6 hours after a reboot) and in some other cases right after a > reboot. In my case, there are no physical loops in the network, but since it's connected straight to a CPE (which contains internal software bridges and switch modules and the like) it's certainly not impossible that some packets are being looped during initialisation/bootup. In my experience, CPEs do all sorts of crazy things... > Is the DAD continuously running in the Linux Kernel? or only when > configuring an IPv6 address? I will try to figure out. I have herd > other annoyances due DAD. DAD is run when an address is added to an interface, or when the interface transitions to the UP state, I believe. When completed (either successfully or unsuccessfully), it is never retried. As I understand it, anyway. (DAD can be a very nice DoS attack actually!) One theory could be that the CPE rebooted, which made the probe's uplink go DOWN/UP, triggering DAD. If the CPE was retransmitting the probe's own packets back to itself at this point, DAD could have failed, and the probe would be left without IPv6 connectivity. OTOH unplugging/replugging the probe didn't solve the problem for me, but perhaps once the address goes into a DAD-failed state, a link DOWN/UP event won't help either. Or maybe I was too quick, so that the probe didn't register the DOWN/UP events. Tore From store at dovgolit.com Fri May 24 12:39:53 2013 From: store at dovgolit.com (=?UTF-8?B?ItCQ0L/RgtC10LrQsCAn0JTQvtCy0LPQvtC70ZbRgicgKNCi0J7QkiAn0Jo=?= =?UTF-8?B?0JXQqCwg0JvQotCUJyki?=) Date: Fri, 24 May 2013 13:39:53 +0300 Subject: [atlas] reset IP configuration Message-ID: <519F4379.9090809@dovgolit.com> Hello! I have RIPE Atlas probe v3 (TP-Link). First i used DHCP configuration, for test at home. But then i was configured my Probe to static IP. Setting will saved with error, and now probe cannot connect to worldwide network. How i can manual reset my Probe to factory/default dhcp settings? -- ? ???????, ?????? ???????? ??? "???,???" www.dovgolit.com ?????! ?????????? ? ?????? ????? ? ??????????????! -------------- next part -------------- An HTML attachment was scrubbed... URL: From willem at nlnetlabs.nl Fri May 24 16:47:20 2013 From: willem at nlnetlabs.nl (Willem Toorop) Date: Fri, 24 May 2013 16:47:20 +0200 Subject: [atlas] Bug when creating DNS6 with udp_reply_bytes via API In-Reply-To: <519F7C52.3000409@nlnetlabs.nl> References: <519F7C52.3000409@nlnetlabs.nl> Message-ID: <519F7D78.8080105@nlnetlabs.nl> Oh yes, here are some measurements illustrating the problem: https://atlas.ripe.net/api/v1/measurement/1009504/ https://atlas.ripe.net/api/v1/measurement/1009505/ https://atlas.ripe.net/api/v1/measurement/1009506/ https://atlas.ripe.net/api/v1/measurement/1009519/ Here is one given with the interface that has a proper value for udp_payload_size: https://atlas.ripe.net/api/v1/measurement/1009517/ And here two submitted via the API that succeed because no udp_reply_bytes was given: https://atlas.ripe.net/api/v1/measurement/1009516/ https://atlas.ripe.net/api/v1/measurement/1009518/ Op 24-05-13 16:42, Willem Toorop schreef: > Hi RIPE Atlas developers, > > I found a bug in the DNS API. > > When creating a DNS measurements via the API that have udp_reply_bytes > property set, they never leave the "Scheduled" state and eventually fail. > > When I query the status of the measurements I notice that they have the > udp_payload_size property set to true in stead of the value given with > udp_reply_bytes. This is different from measurements created via the > interface, where udp_payload_size reflects udp_reply_bytes. > > Also, it appears I can only origin 80 probes (by probe id), whilst in > the interface I can origin from 500 probes. Is that correct? Would it be > possible to (temporarily) increase my limit to 1050 probes? > > Best regards, > > -- Willem > From willem at nlnetlabs.nl Fri May 24 16:42:26 2013 From: willem at nlnetlabs.nl (Willem Toorop) Date: Fri, 24 May 2013 16:42:26 +0200 Subject: [atlas] Bug when creating DNS6 with udp_reply_bytes via API Message-ID: <519F7C52.3000409@nlnetlabs.nl> Hi RIPE Atlas developers, I found a bug in the DNS API. When creating a DNS measurements via the API that have udp_reply_bytes property set, they never leave the "Scheduled" state and eventually fail. When I query the status of the measurements I notice that they have the udp_payload_size property set to true in stead of the value given with udp_reply_bytes. This is different from measurements created via the interface, where udp_payload_size reflects udp_reply_bytes. Also, it appears I can only origin 80 probes (by probe id), whilst in the interface I can origin from 500 probes. Is that correct? Would it be possible to (temporarily) increase my limit to 1050 probes? Best regards, -- Willem From willem at nlnetlabs.nl Fri May 24 17:00:05 2013 From: willem at nlnetlabs.nl (Willem Toorop) Date: Fri, 24 May 2013 17:00:05 +0200 Subject: [atlas] Cannot archive failed measurements Message-ID: <519F8075.7010109@nlnetlabs.nl> Hi, Here is another bug report. I cannot archive/delete measurements that have the "Failed" status. Regards, -- Willem From dquinn at ripe.net Fri May 24 17:06:09 2013 From: dquinn at ripe.net (Daniel Quinn) Date: Fri, 24 May 2013 17:06:09 +0200 Subject: [atlas] Bug when creating DNS6 with udp_reply_bytes via API In-Reply-To: <519F7C52.3000409@nlnetlabs.nl> References: <519F7C52.3000409@nlnetlabs.nl> Message-ID: <519F81E1.2090209@ripe.net> Hello, and thanks for the bug report! But please don't send bug reports to this list. This is the place for discussion about, and seeking help in using RIPE Atlas. Instead target all bugs to: atlas-bugs at ripe.net From alexsaroyan at gmail.com Fri May 24 17:10:25 2013 From: alexsaroyan at gmail.com (Alex Saroyan) Date: Fri, 24 May 2013 19:10:25 +0400 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador In-Reply-To: <98B82E3E-EE94-4105-86C5-A7C38F346F7B@enta.net> References: <519E0056.8010508@gmail.com> <519E04FF.8070708@ripe.net> <5D5133A9-2A07-4FA7-AE88-0E023F64FFA6@gmail.com> <98B82E3E-EE94-4105-86C5-A7C38F346F7B@enta.net> Message-ID: <519F82E1.5090208@gmail.com> Hi, Again similar problem with another probe. I have assigned the probe to surenispiryan at gmail.com then he registered, received registration confirmation e-mail, then connected the probe. Now the probe is seen in the map, but not seen neighther in Ambassador's "my probes" section nor at host's (surenispiryan at gmail.com) "my probes" section Below is row from Ambassador's page 10736 A0F3C1C44063 Suren Ispiryan surenispiryan at gmail.com Hosted 22 May 2013 14:20:02 +0000 Armenian ambassador Regards. /Alex On 05/24/2013 10:18 AM, Steve Lalonde wrote: > Just for completeness the 7th probe is > > 10643 > > Steve > > > On 23 May 2013, at 16:49, Steve Lalonde wrote: > >> Hi >> >> I now have 7 probes online in the last 24 hours (Thanks Fearghas), none of them show up in the "my probes" section yet >> >> they are >> >> 10614 >> 10616 >> 10622 >> 10623 >> 10624 >> 10625 >> >> the 7th is in a different site so I can't read the ID from here. >> >> We are going to configure them with statics and deploy them to places on our network where there are no other probes geographically close. >> >> >> -- >> Steve Lalonde >> Chief Technical Officer >> Entanet International Ltd >> http://www.enta.net/ >> >> >> >> On 23 May 2013, at 13:13, Fearghas McKay wrote: >> >>> On 23 May 2013, at 13:01, Robert Kisteleki wrote: >>> >>>> This person applied/registered. As long as the MAC+email combination matches >>>> what the ambassador said, the process is automatic in about 30 minutes. If >>>> they don't match we have to do something manually, so it takes more time. >>> Then this goes against what I was told as an Ambassador, that it didn't matter if the addresses were different. ~half of the probes I have handed out will probably be using different addresses. Perhaps the 30 minutes information could be updated to let people know that there may be a difference. >>> >>> Thanks >>> >>> f >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dquinn at ripe.net Fri May 24 17:25:15 2013 From: dquinn at ripe.net (Daniel Quinn) Date: Fri, 24 May 2013 17:25:15 +0200 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador In-Reply-To: <519F82E1.5090208@gmail.com> References: <519E0056.8010508@gmail.com> <519E04FF.8070708@ripe.net> <5D5133A9-2A07-4FA7-AE88-0E023F64FFA6@gmail.com> <98B82E3E-EE94-4105-86C5-A7C38F346F7B@enta.net> <519F82E1.5090208@gmail.com> Message-ID: <519F865B.3070909@ripe.net> On 05/24/2013 05:10 PM, Alex Saroyan wrote: > Again similar problem with another probe. Hi everyone, and thanks for letting us know about all of this. We believe that we've found the problem, but aren't keen on deploying any systemic changes on a Friday afternoon. Instead we'll be posting a fix on Monday, at which point all past and future probe assignments will be fixed. Thanks for your patience. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexsaroyan at gmail.com Fri May 24 17:44:57 2013 From: alexsaroyan at gmail.com (Alex Saroyan) Date: Fri, 24 May 2013 19:44:57 +0400 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador In-Reply-To: <519F865B.3070909@ripe.net> References: <519E0056.8010508@gmail.com> <519E04FF.8070708@ripe.net> <5D5133A9-2A07-4FA7-AE88-0E023F64FFA6@gmail.com> <98B82E3E-EE94-4105-86C5-A7C38F346F7B@enta.net> <519F82E1.5090208@gmail.com> <519F865B.3070909@ripe.net> Message-ID: <519F8AF9.70901@gmail.com> Hi, I am happy that root cause was found which was more important for me then to solve particular problems. Regards. /Alex On 05/24/2013 07:25 PM, Daniel Quinn wrote: > On 05/24/2013 05:10 PM, Alex Saroyan wrote: >> Again similar problem with another probe. > > Hi everyone, and thanks for letting us know about all of this. We > believe that we've found the problem, but aren't keen on deploying any > systemic changes on a Friday afternoon. Instead we'll be posting a > fix on Monday, at which point all past and future probe assignments > will be fixed. > > Thanks for your patience. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdimonius at gmail.com Sun May 26 16:00:16 2013 From: sdimonius at gmail.com (=?UTF-8?B?0JTQvNC40YLRgNC40Lkg0KHQtdGA0LPQtdC10LLQuNGH?=) Date: Sun, 26 May 2013 17:00:16 +0300 Subject: [atlas] problem with connection to network Message-ID: <51A21570.8090201@gmail.com> Hello! I have problem with my probe v3 (ID 11003, FW 4520). First i used DHCP (at Home, for tests), all was worked fine. Then i reconfigure my probe to Static IP (by manual). Static IP necessary to install my probe 24/7/365 in server room. We don't use DHCP. But probe can't connect to network... I brought probe to home, connect to DHCP network. Router give IP to probe. But probe still disconnected on atlas.ripe.net at least 3 hours... LEDs: 1 - ON 2 - OFF 3 - Slow blink 4 - ON 5 - ON Power reset - no result. Try to change Router cfg (ip, dns, mask) - no result. Probe still disconnected. I read, that if set static IP - probe try to test setting. By LEDs - "Network test"? But 3+ hours "Network test"? DHCP work correctly (Router - Zyxell Keenetic, last firmware), PC work without problems on full autoconfiguration (IP, mask, gateway, DNS) Can you help me? P.S. Sorry for my english, i'm from Ukraine -- ? ?????????, ??????? ?????? ????: www.weblance.com.ua ?????: www.mukachevo.net ??????: www.dovgolit.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: afggjbfe.png Type: image/png Size: 59591 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: connections.png Type: image/png Size: 59591 bytes Desc: not available URL: From rozboris at gmail.com Sun May 26 17:14:05 2013 From: rozboris at gmail.com (Boris Rozenshteyn) Date: Sun, 26 May 2013 11:14:05 -0400 Subject: [atlas] problem with connection to network In-Reply-To: <51A21570.8090201@gmail.com> References: <51A21570.8090201@gmail.com> Message-ID: Hi Dmitry! I had a very similar issue when I was using faulty and cheap USB charger: probe was somehow working and sometimes even blinking the light, but never connected to Atlas network. Please try using more powerful USB adapter -- that might help. Regards, Boris Rozenshteyn On Sun, May 26, 2013 at 10:00 AM, ??????? ????????? wrote: > Hello! > > I have problem with my probe v3 (ID 11003, FW 4520). > > First i used DHCP (at Home, for tests), all was worked fine. > > Then i reconfigure my probe to Static IP (by manual). Static IP necessary > to install my probe 24/7/365 in server room. We don't use DHCP. > > But probe can't connect to network... > > I brought probe to home, connect to DHCP network. Router give IP to probe. > But probe still disconnected on atlas.ripe.net at least 3 hours... > > LEDs: > 1 - ON > 2 - OFF > 3 - Slow blink > 4 - ON > 5 - ON > > Power reset - no result. Try to change Router cfg (ip, dns, mask) - no > result. Probe still disconnected. > > I read, that if set static IP - probe try to test setting. > > By LEDs - "Network test"? But 3+ hours "Network test"? > > DHCP work correctly (Router - Zyxell Keenetic, last firmware), PC work > without problems on full autoconfiguration (IP, mask, gateway, DNS) > > Can you help me? > > P.S. Sorry for my english, i'm from Ukraine > > > > -- > ? ?????????, ??????? > ?????? ????: www.weblance.com.ua > ?????: www.mukachevo.net > ??????: www.dovgolit.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: afggjbfe.png Type: image/png Size: 59591 bytes Desc: not available URL: From atlas at ripe.net Mon May 27 15:23:08 2013 From: atlas at ripe.net (Alastair Strachan) Date: Mon, 27 May 2013 15:23:08 +0200 Subject: [atlas] [ripe.net #1087678] problem with connection to network In-Reply-To: <51A21570.8090201@gmail.com> References: <51A21570.8090201@gmail.com> Message-ID: Hello, Thanks for your email and update. It would appear there is something on the network that is blocking the probe from connecting outside the network. If a probe has been assigned a Static IP and for some reason that is not reachable, the probe will automatically fall back to DHCP. As this is not happening, there must be something blocking it. The probe is currently configured via DHCP, again, this is not allowing the probe to connect outside your network. Please ensure port 443 is fully open and all firewall/security rules have been adjusted accordingly. Please take a look at our FAQ for more troubleshooting steps: https://atlas.ripe.net/about/faq/ If you do have any further questions, please do not hesitate to contact us. Thank you for taking the time to host an Atlas probe. Kind Regards, Alastair Strachan RIPE Atlas Team ============================================================ Take the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! Participants will be entered into prize draws to win an iPad. https://www.ripe.net/survey2013 ============================================================= On Sun May 26 16:01:00 2013, sdimonius at gmail.com wrote: > Hello! > > I have problem with my probe v3 (ID 11003, FW 4520). > > First i used DHCP (at Home, for tests), all was worked fine. > > Then i reconfigure my probe to Static IP (by manual). Static IP > necessary to install my probe 24/7/365 in server room. We don't use DHCP. > > But probe can't connect to network... > > I brought probe to home, connect to DHCP network. Router give IP to > probe. But probe still disconnected on atlas.ripe.net at least 3 hours... > > LEDs: > 1 - ON > 2 - OFF > 3 - Slow blink > 4 - ON > 5 - ON > > Power reset - no result. Try to change Router cfg (ip, dns, mask) - no > result. Probe still disconnected. > > I read, that if set static IP - probe try to test setting. > > By LEDs - "Network test"? But 3+ hours "Network test"? > > DHCP work correctly (Router - Zyxell Keenetic, last firmware), PC work > without problems on full autoconfiguration (IP, mask, gateway, DNS) > > Can you help me? > > P.S. Sorry for my english, i'm from Ukraine > > > From randy at psg.com Mon May 27 17:28:49 2013 From: randy at psg.com (Randy Bush) Date: Tue, 28 May 2013 00:28:49 +0900 Subject: [atlas] RIPE Atlas slides for AFNOG Message-ID: the atlas folk have been kind enough to hand me a batch of probes to hand out key engineers at the afnog workshops in lusaka. i want to give maybe a half hour talk on the probes, something that starts from the beginning, o what is ripe atlas, o how do i install a probe, o how do i register it, o how do i interpret the web pages, o etc. vesna was kind enough to give me her dublin preso, but that assumes a *lot* of background. i need ripe atlas 101. thanks. randy From atlas at ripe.net Mon May 27 18:33:28 2013 From: atlas at ripe.net (=?UTF-8?B?0JTQvNC40YLRgNC40Lkg0KHQtdGA0LPQtdC10LLQuNGH?=) Date: Mon, 27 May 2013 18:33:28 +0200 Subject: [atlas] [ripe.net #1087678] problem with connection to network In-Reply-To: <51A38AD1.6050000@gmail.com> References: <51A21570.8090201@gmail.com> <51A38AD1.6050000@gmail.com> Message-ID: Hello and thanks for reply! Now probe is work. I was read all FaQ, but nothing help. The network is efficient for 100%. Experiments help me. First i remove external memory, boot from built in, and then attach usb flash, after 10 mins probe connect to network. 27.05.2013 16:23, Alastair Strachan ?????: > Hello, > > Thanks for your email and update. > > It would appear there is something on the network that is blocking the probe from connecting outside the network. > > If a probe has been assigned a Static IP and for some reason that is not reachable, the probe will automatically fall back to DHCP. As this is not happening, there must be something blocking it. > > The probe is currently configured via DHCP, again, this is not allowing the probe to connect outside your network. > > Please ensure port 443 is fully open and all firewall/security rules have been adjusted accordingly. Please take a look at our FAQ for more troubleshooting steps: https://atlas.ripe.net/about/faq/ > > If you do have any further questions, please do not hesitate to contact us. > > Thank you for taking the time to host an Atlas probe. > > Kind Regards, > > Alastair Strachan > > RIPE Atlas Team > > ============================================================ Take the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! > Participants will be entered into prize draws to win an iPad. > https://www.ripe.net/survey2013 ============================================================= > > > > > > On Sun May 26 16:01:00 2013, sdimonius at gmail.com wrote: >> Hello! >> >> I have problem with my probe v3 (ID 11003, FW 4520). >> >> First i used DHCP (at Home, for tests), all was worked fine. >> >> Then i reconfigure my probe to Static IP (by manual). Static IP >> necessary to install my probe 24/7/365 in server room. We don't use DHCP. >> >> But probe can't connect to network... >> >> I brought probe to home, connect to DHCP network. Router give IP to >> probe. But probe still disconnected on atlas.ripe.net at least 3 hours... >> >> LEDs: >> 1 - ON >> 2 - OFF >> 3 - Slow blink >> 4 - ON >> 5 - ON >> >> Power reset - no result. Try to change Router cfg (ip, dns, mask) - no >> result. Probe still disconnected. >> >> I read, that if set static IP - probe try to test setting. >> >> By LEDs - "Network test"? But 3+ hours "Network test"? >> >> DHCP work correctly (Router - Zyxell Keenetic, last firmware), PC work >> without problems on full autoconfiguration (IP, mask, gateway, DNS) >> >> Can you help me? >> >> P.S. Sorry for my english, i'm from Ukraine >> >> >> > > -- ? ?????????, ??????? ?????? ????: www.weblance.com.ua ?????: www.mukachevo.net ??????: www.dovgolit.com From daniel.karrenberg at ripe.net Mon May 27 20:35:58 2013 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Mon, 27 May 2013 20:35:58 +0200 Subject: [atlas] RIPE Atlas slides for AFNOG In-Reply-To: References: Message-ID: <0CE96FF3-A045-4839-8498-86A98969942C@ripe.net> On 27.05.2013, at 17:28 , Randy Bush wrote: > the atlas folk have been kind enough to hand me a batch of probes to > hand out key engineers at the afnog workshops in lusaka. i want to give > maybe a half hour talk on the probes, something that starts from the > beginning, > o what is ripe atlas, > o how do i install a probe, > o how do i register it, > o how do i interpret the web pages, > o etc. > > vesna was kind enough to give me her dublin preso, but that assumes a > *lot* of background. i need ripe atlas 101. > > thanks. > > randy > > http://www.ripe.net/ripe/meetings/regional-meetings/dubrovnik-2011/presentations/20110909-dubrovnik-measurements.ppt.pdf http://ripe61.ripe.net/presentations/110-20101115-dfk-atlas-noglobe.pdf fit the bill? i can send you source if needed. d From daniel.karrenberg at ripe.net Mon May 27 20:56:56 2013 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Mon, 27 May 2013 20:56:56 +0200 Subject: [atlas] RIPE Atlas slides for AFNOG In-Reply-To: <0CE96FF3-A045-4839-8498-86A98969942C@ripe.net> References: <0CE96FF3-A045-4839-8498-86A98969942C@ripe.net> Message-ID: <2BEFD3AF-6DF6-4752-86C8-F6810FFC4092@ripe.net> On 27.05.2013, at 20:35 , Daniel Karrenberg wrote: > > On 27.05.2013, at 17:28 , Randy Bush wrote: > >> the atlas folk have been kind enough to hand me a batch of probes to >> hand out key engineers at the afnog workshops in lusaka. i want to give >> maybe a half hour talk on the probes, something that starts from the >> beginning, >> o what is ripe atlas, >> o how do i install a probe, >> o how do i register it, >> o how do i interpret the web pages, >> o etc. >> >> vesna was kind enough to give me her dublin preso, but that assumes a >> *lot* of background. i need ripe atlas 101. >> >> thanks. >> >> randy >> >> > > http://www.ripe.net/ripe/meetings/regional-meetings/dubrovnik-2011/presentations/20110909-dubrovnik-measurements.ppt.pdf > > http://ripe61.ripe.net/presentations/110-20101115-dfk-atlas-noglobe.pdf > > fit the bill? > > i can send you source if needed. > > d > To be clear: it is only to the "what is ripe atlas" part. The rest you need to get from Vesna. From randy at psg.com Tue May 28 02:49:52 2013 From: randy at psg.com (Randy Bush) Date: Tue, 28 May 2013 09:49:52 +0900 Subject: [atlas] RIPE Atlas slides for AFNOG In-Reply-To: <0CE96FF3-A045-4839-8498-86A98969942C@ripe.net> References: <0CE96FF3-A045-4839-8498-86A98969942C@ripe.net> Message-ID: thanks daniel. more in private email. randy From atlas at ripe.net Tue May 28 10:37:50 2013 From: atlas at ripe.net (Alastair Strachan) Date: Tue, 28 May 2013 10:37:50 +0200 Subject: [atlas] [ripe.net #1087678] problem with connection to network In-Reply-To: References: <51A21570.8090201@gmail.com> <51A38AD1.6050000@gmail.com> Message-ID: Hello, Thanks for your email and update. I can confirm the probe is back online and reporting without issue. If you do have any further questions, please do not hesitate to contact us. Thank you for taking the time to host an Atlas probe. Kind Regards, Alastair Strachan RIPE Atlas Team ============================================================ Take the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! Participants will be entered into prize draws to win an iPad. https://www.ripe.net/survey2013 ============================================================= On Mon May 27 18:33:28 2013, sdimonius at gmail.com wrote: > Hello and thanks for reply! > > Now probe is work. I was read all FaQ, but nothing help. > > The network is efficient for 100%. > > Experiments help me. First i remove external memory, boot from built > in, > and then attach usb flash, after 10 mins probe connect to network. > > 27.05.2013 16:23, Alastair Strachan ?????: > > Hello, > > > > Thanks for your email and update. > > > > It would appear there is something on the network that is blocking > the probe from connecting outside the network. > > > > If a probe has been assigned a Static IP and for some reason that is > not reachable, the probe will automatically fall back to DHCP. As this > is not happening, there must be something blocking it. > > > > The probe is currently configured via DHCP, again, this is not > allowing the probe to connect outside your network. > > > > Please ensure port 443 is fully open and all firewall/security rules > have been adjusted accordingly. Please take a look at our FAQ for more > troubleshooting steps: https://atlas.ripe.net/about/faq/ > > > > If you do have any further questions, please do not hesitate to > contact us. > > > > Thank you for taking the time to host an Atlas probe. > > > > Kind Regards, > > > > Alastair Strachan > > > > RIPE Atlas Team > > > > ============================================================ Take > the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! > > Participants will be entered into prize draws to win an iPad. > > https://www.ripe.net/survey2013 > ============================================================= > > > > > > > > > > > > On Sun May 26 16:01:00 2013, sdimonius at gmail.com wrote: > >> Hello! > >> > >> I have problem with my probe v3 (ID 11003, FW 4520). > >> > >> First i used DHCP (at Home, for tests), all was worked fine. > >> > >> Then i reconfigure my probe to Static IP (by manual). Static IP > >> necessary to install my probe 24/7/365 in server room. We don't use > DHCP. > >> > >> But probe can't connect to network... > >> > >> I brought probe to home, connect to DHCP network. Router give IP to > >> probe. But probe still disconnected on atlas.ripe.net at least 3 > hours... > >> > >> LEDs: > >> 1 - ON > >> 2 - OFF > >> 3 - Slow blink > >> 4 - ON > >> 5 - ON > >> > >> Power reset - no result. Try to change Router cfg (ip, dns, mask) - > no > >> result. Probe still disconnected. > >> > >> I read, that if set static IP - probe try to test setting. > >> > >> By LEDs - "Network test"? But 3+ hours "Network test"? > >> > >> DHCP work correctly (Router - Zyxell Keenetic, last firmware), PC > work > >> without problems on full autoconfiguration (IP, mask, gateway, DNS) > >> > >> Can you help me? > >> > >> P.S. Sorry for my english, i'm from Ukraine > >> > >> > >> > > > > > > From atlas at ripe.net Tue May 28 10:50:44 2013 From: atlas at ripe.net (Dmitriy Kazimirov) Date: Tue, 28 May 2013 10:50:44 +0200 Subject: [atlas] [ripe.net #1087678] problem with connection to network In-Reply-To: <95CC171F-1AB6-40E6-9C75-F7694BAA3161@viorsan.com> References: <51A21570.8090201@gmail.com> <51A38AD1.6050000@gmail.com> <95CC171F-1AB6-40E6-9C75-F7694BAA3161@viorsan.com> Message-ID: hi, Well,ok. thanks 1st question: - Probe is hosted behind Dual-WAN router with 2 residtual connections with 2 different ISPs. Both connections are online, traffic is load-balanced between them. Right now I configured router to allow probe traffic via main connection. Should I allow router to just switch between connections as all other devices on internal network do ? Should I ask for 2nd probe and lock it into 2nd connection? (If that's matter, I use Astaro Security Gateway software appliance as router) 28.05.2013, ? 15:37, Alastair Strachan ???????(?): > Hello, > > Thanks for your email and update. > > I can confirm the probe is back online and reporting without issue. > > If you do have any further questions, please do not hesitate to contact us. > > Thank you for taking the time to host an Atlas probe. > > Kind Regards, > > Alastair Strachan > > RIPE Atlas Team > > ============================================================ > Take the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! > Participants will be entered into prize draws to win an iPad. > https://www.ripe.net/survey2013 > ============================================================= > > > On Mon May 27 18:33:28 2013, sdimonius at gmail.com wrote: >> Hello and thanks for reply! >> >> Now probe is work. I was read all FaQ, but nothing help. >> >> The network is efficient for 100%. >> >> Experiments help me. First i remove external memory, boot from built >> in, >> and then attach usb flash, after 10 mins probe connect to network. >> >> 27.05.2013 16:23, Alastair Strachan ?????: >>> Hello, >>> >>> Thanks for your email and update. >>> >>> It would appear there is something on the network that is blocking >> the probe from connecting outside the network. >>> >>> If a probe has been assigned a Static IP and for some reason that is >> not reachable, the probe will automatically fall back to DHCP. As this >> is not happening, there must be something blocking it. >>> >>> The probe is currently configured via DHCP, again, this is not >> allowing the probe to connect outside your network. >>> >>> Please ensure port 443 is fully open and all firewall/security rules >> have been adjusted accordingly. Please take a look at our FAQ for more >> troubleshooting steps: https://atlas.ripe.net/about/faq/ >>> >>> If you do have any further questions, please do not hesitate to >> contact us. >>> >>> Thank you for taking the time to host an Atlas probe. >>> >>> Kind Regards, >>> >>> Alastair Strachan >>> >>> RIPE Atlas Team >>> >>> ============================================================ > Take >> the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! >>> Participants will be entered into prize draws to win an iPad. >>> https://www.ripe.net/survey2013 >> ============================================================= >>> >>> >>> >>> >>> >>> On Sun May 26 16:01:00 2013, sdimonius at gmail.com wrote: >>>> Hello! >>>> >>>> I have problem with my probe v3 (ID 11003, FW 4520). >>>> >>>> First i used DHCP (at Home, for tests), all was worked fine. >>>> >>>> Then i reconfigure my probe to Static IP (by manual). Static IP >>>> necessary to install my probe 24/7/365 in server room. We don't use >> DHCP. >>>> >>>> But probe can't connect to network... >>>> >>>> I brought probe to home, connect to DHCP network. Router give IP to >>>> probe. But probe still disconnected on atlas.ripe.net at least 3 >> hours... >>>> >>>> LEDs: >>>> 1 - ON >>>> 2 - OFF >>>> 3 - Slow blink >>>> 4 - ON >>>> 5 - ON >>>> >>>> Power reset - no result. Try to change Router cfg (ip, dns, mask) - >> no >>>> result. Probe still disconnected. >>>> >>>> I read, that if set static IP - probe try to test setting. >>>> >>>> By LEDs - "Network test"? But 3+ hours "Network test"? >>>> >>>> DHCP work correctly (Router - Zyxell Keenetic, last firmware), PC >> work >>>> without problems on full autoconfiguration (IP, mask, gateway, DNS) >>>> >>>> Can you help me? >>>> >>>> P.S. Sorry for my english, i'm from Ukraine >>>> >>>> >>>> >>> >>> >> >> > > > From dmitriy.kazimirov at viorsan.com Tue May 28 10:51:57 2013 From: dmitriy.kazimirov at viorsan.com (Dmitriy Kazimirov) Date: Tue, 28 May 2013 15:51:57 +0700 Subject: [atlas] [ripe.net #1087678] problem with connection to network In-Reply-To: References: <51A21570.8090201@gmail.com> <51A38AD1.6050000@gmail.com> Message-ID: <95CC171F-1AB6-40E6-9C75-F7694BAA3161@viorsan.com> hi, Well,ok. thanks 1st question: - Probe is hosted behind Dual-WAN router with 2 residtual connections with 2 different ISPs. Both connections are online, traffic is load-balanced between them. Right now I configured router to allow probe traffic via main connection. Should I allow router to just switch between connections as all other devices on internal network do ? Should I ask for 2nd probe and lock it into 2nd connection? (If that's matter, I use Astaro Security Gateway software appliance as router) 28.05.2013, ? 15:37, Alastair Strachan ???????(?): > Hello, > > Thanks for your email and update. > > I can confirm the probe is back online and reporting without issue. > > If you do have any further questions, please do not hesitate to contact us. > > Thank you for taking the time to host an Atlas probe. > > Kind Regards, > > Alastair Strachan > > RIPE Atlas Team > > ============================================================ > Take the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! > Participants will be entered into prize draws to win an iPad. > https://www.ripe.net/survey2013 > ============================================================= > > > On Mon May 27 18:33:28 2013, sdimonius at gmail.com wrote: >> Hello and thanks for reply! >> >> Now probe is work. I was read all FaQ, but nothing help. >> >> The network is efficient for 100%. >> >> Experiments help me. First i remove external memory, boot from built >> in, >> and then attach usb flash, after 10 mins probe connect to network. >> >> 27.05.2013 16:23, Alastair Strachan ?????: >>> Hello, >>> >>> Thanks for your email and update. >>> >>> It would appear there is something on the network that is blocking >> the probe from connecting outside the network. >>> >>> If a probe has been assigned a Static IP and for some reason that is >> not reachable, the probe will automatically fall back to DHCP. As this >> is not happening, there must be something blocking it. >>> >>> The probe is currently configured via DHCP, again, this is not >> allowing the probe to connect outside your network. >>> >>> Please ensure port 443 is fully open and all firewall/security rules >> have been adjusted accordingly. Please take a look at our FAQ for more >> troubleshooting steps: https://atlas.ripe.net/about/faq/ >>> >>> If you do have any further questions, please do not hesitate to >> contact us. >>> >>> Thank you for taking the time to host an Atlas probe. >>> >>> Kind Regards, >>> >>> Alastair Strachan >>> >>> RIPE Atlas Team >>> >>> ============================================================ > Take >> the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! >>> Participants will be entered into prize draws to win an iPad. >>> https://www.ripe.net/survey2013 >> ============================================================= >>> >>> >>> >>> >>> >>> On Sun May 26 16:01:00 2013, sdimonius at gmail.com wrote: >>>> Hello! >>>> >>>> I have problem with my probe v3 (ID 11003, FW 4520). >>>> >>>> First i used DHCP (at Home, for tests), all was worked fine. >>>> >>>> Then i reconfigure my probe to Static IP (by manual). Static IP >>>> necessary to install my probe 24/7/365 in server room. We don't use >> DHCP. >>>> >>>> But probe can't connect to network... >>>> >>>> I brought probe to home, connect to DHCP network. Router give IP to >>>> probe. But probe still disconnected on atlas.ripe.net at least 3 >> hours... >>>> >>>> LEDs: >>>> 1 - ON >>>> 2 - OFF >>>> 3 - Slow blink >>>> 4 - ON >>>> 5 - ON >>>> >>>> Power reset - no result. Try to change Router cfg (ip, dns, mask) - >> no >>>> result. Probe still disconnected. >>>> >>>> I read, that if set static IP - probe try to test setting. >>>> >>>> By LEDs - "Network test"? But 3+ hours "Network test"? >>>> >>>> DHCP work correctly (Router - Zyxell Keenetic, last firmware), PC >> work >>>> without problems on full autoconfiguration (IP, mask, gateway, DNS) >>>> >>>> Can you help me? >>>> >>>> P.S. Sorry for my english, i'm from Ukraine >>>> >>>> >>>> >>> >>> >> >> > > > From philip.homburg at ripe.net Tue May 28 11:26:21 2013 From: philip.homburg at ripe.net (Philip Homburg) Date: Tue, 28 May 2013 11:26:21 +0200 Subject: [atlas] [ripe.net #1087678] problem with connection to network In-Reply-To: References: <51A21570.8090201@gmail.com> <51A38AD1.6050000@gmail.com> <95CC171F-1AB6-40E6-9C75-F7694BAA3161@viorsan.com> Message-ID: <51A4783D.2050805@ripe.net> On 5/28/13 10:50 , Dmitriy Kazimirov wrote: > hi, > Well,ok. thanks > 1st question: > - Probe is hosted behind Dual-WAN router with 2 residtual connections with 2 different ISPs. Both connections are online, traffic is load-balanced between them. Right now I configured router to allow probe traffic via main connection. Should I allow router to just switch between connections as all other devices on internal network do ? Should I ask for 2nd probe and lock it into 2nd connection? > (If that's matter, I use Astaro Security Gateway software appliance as router) > Hi, For getting consistent results it would be best to configure the router to use just one connection for the probe. I think it is best to get the current probe to be stable for a while before asking for a second probe. From atlas at ripe.net Tue May 28 11:26:22 2013 From: atlas at ripe.net (Philip Homburg) Date: Tue, 28 May 2013 11:26:22 +0200 Subject: [atlas] [ripe.net #1087678] problem with connection to network In-Reply-To: <51A4783D.2050805@ripe.net> References: <51A21570.8090201@gmail.com> <51A38AD1.6050000@gmail.com> <95CC171F-1AB6-40E6-9C75-F7694BAA3161@viorsan.com> <51A4783D.2050805@ripe.net> Message-ID: On 5/28/13 10:50 , Dmitriy Kazimirov wrote: > hi, > Well,ok. thanks > 1st question: > - Probe is hosted behind Dual-WAN router with 2 residtual connections with 2 different ISPs. Both connections are online, traffic is load-balanced between them. Right now I configured router to allow probe traffic via main connection. Should I allow router to just switch between connections as all other devices on internal network do ? Should I ask for 2nd probe and lock it into 2nd connection? > (If that's matter, I use Astaro Security Gateway software appliance as router) > Hi, For getting consistent results it would be best to configure the router to use just one connection for the probe. I think it is best to get the current probe to be stable for a while before asking for a second probe. From alexsaroyan at gmail.com Wed May 29 15:29:58 2013 From: alexsaroyan at gmail.com (Alex Saroyan) Date: Wed, 29 May 2013 17:29:58 +0400 Subject: [atlas] Troubles with registering the probe if assigned by Ambassador In-Reply-To: <519F865B.3070909@ripe.net> References: <519E0056.8010508@gmail.com> <519E04FF.8070708@ripe.net> <5D5133A9-2A07-4FA7-AE88-0E023F64FFA6@gmail.com> <98B82E3E-EE94-4105-86C5-A7C38F346F7B@enta.net> <519F82E1.5090208@gmail.com> <519F865B.3070909@ripe.net> Message-ID: <51A602D6.9050304@gmail.com> Hi, Did you apply the fix already ? I'm not sure about future probe assignments but past probe assignments did not appear yet. A0F3C1C45A92 A0F3C1C44BC6 A0F3C1C44063 Regards. /Alex On 05/24/2013 07:25 PM, Daniel Quinn wrote: > On 05/24/2013 05:10 PM, Alex Saroyan wrote: >> Again similar problem with another probe. > > Hi everyone, and thanks for letting us know about all of this. We > believe that we've found the problem, but aren't keen on deploying any > systemic changes on a Friday afternoon. Instead we'll be posting a > fix on Monday, at which point all past and future probe assignments > will be fixed. > > Thanks for your patience. -------------- next part -------------- An HTML attachment was scrubbed... URL: