- ripe-atlas - mailman.ripe.net

Bug when creating DNS6 with udp_reply_bytes via API
by Willem Toorop 24 May '13

24 May '13

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

2 2

Cannot archive failed measurements
by Willem Toorop 24 May '13

24 May '13

Hi, Here is another bug report. I cannot archive/delete measurements that have the "Failed" status. Regards, -- Willem

1 0

reset IP configuration
by "Аптека 'Довголіт' (ТОВ 'К ЕШ, ЛТД')" 24 May '13

24 May '13

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 <http://dovgolit.com> Увага! Інформація у даному листі є конфіденційною!

1 0

Probe doesn't seem to automatically recover from IPv6 connectivity failure
by Sulev-Madis Silber 24 May '13

24 May '13

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.

8 22

Ripe atlas measurement issues
by balz＠Mathematik.Uni-Marburg.de 24 May '13

24 May '13

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=ud… 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

2 1

Re: [atlas] Хозяин Судьбы
by Sales Department 23 May '13

23 May '13

ТРЕНИНГ: ХОЗЯИН СУДЬБЫ Первый тренинг цикла "Хозяин Судьбы" от Сергея Змеева в Украине Хозяин Судьбы - это проект по кардинальному изменению жизни, один из самых знаковых продуктов инфобизнеса и рынка тренингов России, а теперь и Украины! Проект, охвативший активное и действующее русскоязычное сообщество по всему Миру! "Хозяин судьбы" - это мощная квинтэссенция, все самое эффективное и действенное, что могут дать квантовая физика, парапсихология, эзотерические, древневосточные и славянские практики, НЛП, классическая психология, управление финансами, бизнесом и организационными процессами. Это обобщенная и доведённая до алмазной чистоты обратная связь тысяч участников. В программе: - "Вызов" как способ реализации цели. - Зоны комфорта и выход из них. - "Точки отчаяния" - как их проходить с минимальными затратами энергии. - Методика естественного процесса сброса стресса. - Постановка и реализация поставленных целей. Этапы и структура движения. - Синдром достижения цели. - "Эффект перевернутой пирамиды". Почему и как люди теряют себя и деньги, смысл жизни. - Ценности и цели. - Предприниматель как устойчивая орбита и переход на самый высокий уровень. - Практики работы с эмоциональными состояниями. - Техника быстрого восстановления жизненных сил. - Практики принятия правильного решения. - Подключение к энергии денег. - Избавление от иллюзий. Мы гарантируем, что мероприятие будет нести практическую информацию и полезность. Это не будет очередной "голой презентацией" платных продуктов и тренингов. Несмотря на то, что любая история из уст Сергея является ценной информацией, Сергей Змеев обещал выдать не одну ключевую "фишку", которая может сильно "продвинуть" Вас по жизни. Информация о тренере: Сергей Змеев - практик Успеха No1, автор проекта "Хозяин Судьбы", бизнесмен, инвестор, эксперт психологии бизнеса, профессиональный бизнес-тренер, коуч, миллионер. Автор книг "Перезагрузка", "Путь бизнес Мага", "Как стать звездой - 35 советов бизнес тренерам", "Энергия Денег", "Как создать консалтинговую Империю?", "Личность и эффективность руководителя", "Гений Продаж" Каждому участнику предоставляется: Комплект учебно-методических материалов; Диплом о повышении квалификации по данной тематике. Дата и место проведения: 25 мая. г. Киев, Арена Сити, конференц-зал Royal De Luxe Hotel Стоимость участия: 1400.00 грн. - за одного участника. Для второго и третьего участника скидки 5% и 7% соответственно Формат тренинга: Регистрация участников: с 10.15 до 10.50. Время проведения: с 11.00 до 19.00. Обеденный перерыв: с 14.30 до 15.30 Если вы не хотите получать информацию о мероприятиях в сфере повышения квалификации, отпишитесь по ссылке unsubscribe

1 0

Re: [atlas] [ripe.net #1087039] New Probe Deployment
by mick.odonovan＠bt.com 22 May '13

22 May '13

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@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(a)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(a)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 > >

1 0

CV para su amable consideración
by Julia 21 May '13

21 May '13

1 0

(OT) RIPE PTR zone damaged in the last few days?
by Max Grobecker 21 May '13

21 May '13

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

2 1

Международные стандaрты финансовой oтчетнoсти (МСФO)
by Соcтавление финaнсoвой отчетнoсти пo междунapодным cтaндартам 20 May '13

20 May '13

1 0