Dear RIPE Atlas ambassadors, It’s been a long time since we shared some news, and we have a lot to tell you about! ******** One million credits ******** Do you know that you have 1,000,000 RIPE Atlas credits as thanks for helping us build the largest Internet measurement network? Here are some ways you can take advantage of these credits to run your own measurements: 1) If a customer complains they can't reach your network, you can schedule a ping from 500 probes to diagnose where else in the world this problem is visible. Cost for a one-off ping measurement using 500 probes around the world: 3,000 credits. 2) If you suspect that there are reachability problems between your server and a specific network, you can perform traceroute measurements every 30 minutes from 50 probes located in a certain AS Number, or in a specified country. Daily cost: 72,000 credits. 3) Use DomainMON to monitor your own name servers: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-domainmon-is-... For example, you could schedule a measurement of 6 name servers for ripe.net with UDP SOA every hour from 10 probes. Daily cost: 28,800 credits. View your own credits here: https://atlas.ripe.net/user/credits/ If you haven’t received the million credits yet, it means that none of your ambassador probes have been connected yet. Please chase your contacts and ask them to get their probes online! ******** 10% credits from your online ambassador probes ******** Since this is the holiday season, we believe our ambassadors deserve special recognition for their help. As an ambassador, you will now receive daily 10% of the credits that your ambassador probes generate when they are online. That means you’ll receive 2,160 credits every day for each of your ambassador probes that remain online. ******** Ambassador page improvements ******** The ambassador page has been improved. Besides being the place where you register the details of the people you gave the probes to, you can now find helpful information, including: 1) Tools for promoting RIPE Atlas 2) Communications: links to mailing list, conferences page and updates 3) How do I know where probes are needed? 4) How do I ask for more probes? https://atlas.ripe.net/ambassadors/probes/ ******** RIPE Atlas in multiple languages ******** You’ve asked us whether we can provide information about RIPE Atlas in other languages. We’ll soon have brochures available online in Spanish, Portuguese and French, with more languages coming. In the meantime, some community members have provided some information and we've collected their articles and blogs on GitHub. Take a look - and feel free to add your own: https://github.com/RIPE-Atlas-Community/multi-lingual-docs It has been a great year for RIPE Atlas and we wish to thank you for your contribution! We hope we can count on your cooperation again next year. Happy Holidays! Michela, Lia & Vesna Measurements Community Building RIPE NCC
Thanks :) Alex Ojeda On Tue, Dec 22, 2015 at 4:58 AM -0800, "Michela Galante" <mgalante@ripe.net<mailto:mgalante@ripe.net>> wrote: Dear RIPE Atlas ambassadors, It's been a long time since we shared some news, and we have a lot to tell you about! ******** One million credits ******** Do you know that you have 1,000,000 RIPE Atlas credits as thanks for helping us build the largest Internet measurement network? Here are some ways you can take advantage of these credits to run your own measurements: 1) If a customer complains they can't reach your network, you can schedule a ping from 500 probes to diagnose where else in the world this problem is visible. Cost for a one-off ping measurement using 500 probes around the world: 3,000 credits. 2) If you suspect that there are reachability problems between your server and a specific network, you can perform traceroute measurements every 30 minutes from 50 probes located in a certain AS Number, or in a specified country. Daily cost: 72,000 credits. 3) Use DomainMON to monitor your own name servers: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-domainmon-is-... For example, you could schedule a measurement of 6 name servers for ripe.net<http://ripe.net> with UDP SOA every hour from 10 probes. Daily cost: 28,800 credits. View your own credits here: https://atlas.ripe.net/user/credits/ If you haven't received the million credits yet, it means that none of your ambassador probes have been connected yet. Please chase your contacts and ask them to get their probes online! ******** 10% credits from your online ambassador probes ******** Since this is the holiday season, we believe our ambassadors deserve special recognition for their help. As an ambassador, you will now receive daily 10% of the credits that your ambassador probes generate when they are online. That means you'll receive 2,160 credits every day for each of your ambassador probes that remain online. ******** Ambassador page improvements ******** The ambassador page has been improved. Besides being the place where you register the details of the people you gave the probes to, you can now find helpful information, including: 1) Tools for promoting RIPE Atlas 2) Communications: links to mailing list, conferences page and updates 3) How do I know where probes are needed? 4) How do I ask for more probes? https://atlas.ripe.net/ambassadors/probes/ ******** RIPE Atlas in multiple languages ******** You've asked us whether we can provide information about RIPE Atlas in other languages. We'll soon have brochures available online in Spanish, Portuguese and French, with more languages coming. In the meantime, some community members have provided some information and we've collected their articles and blogs on GitHub. Take a look - and feel free to add your own: https://github.com/RIPE-Atlas-Community/multi-lingual-docs It has been a great year for RIPE Atlas and we wish to thank you for your contribution! We hope we can count on your cooperation again next year. Happy Holidays! Michela, Lia & Vesna Measurements Community Building RIPE NCC [cid:21D77272-24EC-4AE6-9E8D-57D80D19EA38@ripe.net]
Thanks and keep up the good work. we'd really appreciate more probes around the world and we're already putting them to good use. I'm happy to report from Israel that we increased coverage by ~33% and many more coming along the way. Here is some feedback I would like to share about the process: 1. There are many people here without USB ports on their routers or the USB port unpowered. it would be great if RIPE could provide kits with suitable power adaptors. as RIPE can buy them in bulk, it will probably be less costly than ambassadors providing these ourselves. 2. Not unrelated to the above, I added my own USB to power adaptor to one of the kits to help installation and it turned out faulty and caught fire. aside from embarrassment, this made people in the company a bit wary of hosting a probe. 3. People will chip in if explained that the credits will help our company deliver better service to our users. However, the current credit system forces me to register it under my name and not theirs. it would be better if at registration point, a user could permanently assign credits to a recipient or group. 4. Building up on the above, perhaps gamification and groups are a good way to encourage adoption. Seeing how many credits your group generated makes it a bit like a (positive) contest. 5. I have found trouble with getting coverage for mobile (3G/4G) networks. there are very few setups in which these are gateway'd to ethernet. as a case in point, we have a USB 3G adaptor as backup in the company and no one would mind if it's connected to a probe when it's unused (which is 99.99% of the time), but there is no physical port available for this (and possibly no CDC ethernet driver). another option might be to allow the probes to interface with mobile phones somehow, which would entail occasional access to these networks when a paired phone is nearby, but perhaps it would be better than nothing. I've been using RIPE insofar to support a decision for selecting our company's next ISP as well as to ascertain and debug performance issues with our CDN provider. as we are deployed worldwide, every probe you can put in every country matters and helps us provide better service. again, much appreciated. Happy holidays! Regards, Gil Bahat, DevOps Engineer, Magisto Ltd. On Tue, Dec 22, 2015 at 4:29 PM, Alex Ojeda <alex@chilenetworks.com> wrote:
Thanks :)
Alex Ojeda
On Tue, Dec 22, 2015 at 4:58 AM -0800, "Michela Galante" < mgalante@ripe.net> wrote:
Dear RIPE Atlas ambassadors,
It’s been a long time since we shared some news, and we have a lot to tell you about!
******** One million credits ********
Do you know that you have 1,000,000 RIPE Atlas credits as thanks for helping us build the largest Internet measurement network? Here are some ways you can take advantage of these credits to run your own measurements:
1) If a customer complains they can't reach your network, you can schedule a ping from 500 probes to diagnose where else in the world this problem is visible. Cost for a one-off ping measurement using 500 probes around the world: 3,000 credits. 2) If you suspect that there are reachability problems between your server and a specific network, you can perform traceroute measurements every 30 minutes from 50 probes located in a certain AS Number, or in a specified country. Daily cost: 72,000 credits. 3) Use DomainMON to monitor your own name servers: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-domainmon-is-...
For example, you could schedule a measurement of 6 name servers for ripe.net with UDP SOA every hour from 10 probes. Daily cost: 28,800 credits.
View your own credits here: https://atlas.ripe.net/user/credits/ If you haven’t received the million credits yet, it means that none of your ambassador probes have been connected yet. Please chase your contacts and ask them to get their probes online!
******** 10% credits from your online ambassador probes ********
Since this is the holiday season, we believe our ambassadors deserve special recognition for their help. As an ambassador, you will now receive daily 10% of the credits that your ambassador probes generate when they are online. That means you’ll receive 2,160 credits every day for each of your ambassador probes that remain online.
******** Ambassador page improvements ********
The ambassador page has been improved. Besides being the place where you register the details of the people you gave the probes to, you can now find helpful information, including:
1) Tools for promoting RIPE Atlas 2) Communications: links to mailing list, conferences page and updates 3) How do I know where probes are needed? 4) How do I ask for more probes?
https://atlas.ripe.net/ambassadors/probes/
******** RIPE Atlas in multiple languages ********
You’ve asked us whether we can provide information about RIPE Atlas in other languages. We’ll soon have brochures available online in Spanish, Portuguese and French, with more languages coming. In the meantime, some community members have provided some information and we've collected their articles and blogs on GitHub. Take a look - and feel free to add your own: https://github.com/RIPE-Atlas-Community/multi-lingual-docs
It has been a great year for RIPE Atlas and we wish to thank you for your contribution! We hope we can count on your cooperation again next year.
Happy Holidays!
Michela, Lia & Vesna Measurements Community Building RIPE NCC
_______________________________________________ RIPE-Atlas-Ambassadors mailing list RIPE-Atlas-Ambassadors@ripe.net https://www.ripe.net/mailman/listinfo/ripe-atlas-ambassadors
A major problem in setting up these probes is that we cannot configure it directly with a static IP address. So it is getting limited to places where they have a DHCP server. I have many customers without a DHCP server due to some reasons of their own. I feel it is trivial to provide a default IP address if the probe is reset and leave it to them to convert it to DHCP if they choose. Regards Durga Prasad +919849111010 From: RIPE-Atlas-Ambassadors [mailto:ripe-atlas-ambassadors-bounces@ripe.net] On Behalf Of Gil Bahat Sent: 24 December 2015 19:53 To: ripe-atlas-ambassadors@ripe.net Subject: Re: [RIPE Atlas Ambassadors] News and Happy Holidays! Thanks and keep up the good work. we'd really appreciate more probes around the world and we're already putting them to good use. I'm happy to report from Israel that we increased coverage by ~33% and many more coming along the way. Here is some feedback I would like to share about the process: 1. There are many people here without USB ports on their routers or the USB port unpowered. it would be great if RIPE could provide kits with suitable power adaptors. as RIPE can buy them in bulk, it will probably be less costly than ambassadors providing these ourselves. 2. Not unrelated to the above, I added my own USB to power adaptor to one of the kits to help installation and it turned out faulty and caught fire. aside from embarrassment, this made people in the company a bit wary of hosting a probe. 3. People will chip in if explained that the credits will help our company deliver better service to our users. However, the current credit system forces me to register it under my name and not theirs. it would be better if at registration point, a user could permanently assign credits to a recipient or group. 4. Building up on the above, perhaps gamification and groups are a good way to encourage adoption. Seeing how many credits your group generated makes it a bit like a (positive) contest. 5. I have found trouble with getting coverage for mobile (3G/4G) networks. there are very few setups in which these are gateway'd to ethernet. as a case in point, we have a USB 3G adaptor as backup in the company and no one would mind if it's connected to a probe when it's unused (which is 99.99% of the time), but there is no physical port available for this (and possibly no CDC ethernet driver). another option might be to allow the probes to interface with mobile phones somehow, which would entail occasional access to these networks when a paired phone is nearby, but perhaps it would be better than nothing. I've been using RIPE insofar to support a decision for selecting our company's next ISP as well as to ascertain and debug performance issues with our CDN provider. as we are deployed worldwide, every probe you can put in every country matters and helps us provide better service. again, much appreciated. Happy holidays! Regards, Gil Bahat, DevOps Engineer, Magisto Ltd. On Tue, Dec 22, 2015 at 4:29 PM, Alex Ojeda <alex@chilenetworks.com> wrote: Thanks :) Alex Ojeda On Tue, Dec 22, 2015 at 4:58 AM -0800, "Michela Galante" <mgalante@ripe.net> wrote: Dear RIPE Atlas ambassadors, It’s been a long time since we shared some news, and we have a lot to tell you about! ******** One million credits ******** Do you know that you have 1,000,000 RIPE Atlas credits as thanks for helping us build the largest Internet measurement network? Here are some ways you can take advantage of these credits to run your own measurements: 1) If a customer complains they can't reach your network, you can schedule a ping from 500 probes to diagnose where else in the world this problem is visible. Cost for a one-off ping measurement using 500 probes around the world: 3,000 credits. 2) If you suspect that there are reachability problems between your server and a specific network, you can perform traceroute measurements every 30 minutes from 50 probes located in a certain AS Number, or in a specified country. Daily cost: 72,000 credits. 3) Use DomainMON to monitor your own name servers: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-domainmon-is-... For example, you could schedule a measurement of 6 name servers for ripe.net with UDP SOA every hour from 10 probes. Daily cost: 28,800 credits. View your own credits here: https://atlas.ripe.net/user/credits/ If you haven’t received the million credits yet, it means that none of your ambassador probes have been connected yet. Please chase your contacts and ask them to get their probes online! ******** 10% credits from your online ambassador probes ******** Since this is the holiday season, we believe our ambassadors deserve special recognition for their help. As an ambassador, you will now receive daily 10% of the credits that your ambassador probes generate when they are online. That means you’ll receive 2,160 credits every day for each of your ambassador probes that remain online. ******** Ambassador page improvements ******** The ambassador page has been improved. Besides being the place where you register the details of the people you gave the probes to, you can now find helpful information, including: 1) Tools for promoting RIPE Atlas 2) Communications: links to mailing list, conferences page and updates 3) How do I know where probes are needed? 4) How do I ask for more probes? https://atlas.ripe.net/ambassadors/probes/ ******** RIPE Atlas in multiple languages ******** You’ve asked us whether we can provide information about RIPE Atlas in other languages. We’ll soon have brochures available online in Spanish, Portuguese and French, with more languages coming. In the meantime, some community members have provided some information and we've collected their articles and blogs on GitHub. Take a look - and feel free to add your own: https://github.com/RIPE-Atlas-Community/multi-lingual-docs It has been a great year for RIPE Atlas and we wish to thank you for your contribution! We hope we can count on your cooperation again next year. Happy Holidays! Michela, Lia & Vesna Measurements Community Building RIPE NCC _______________________________________________ RIPE-Atlas-Ambassadors mailing list RIPE-Atlas-Ambassadors@ripe.net https://www.ripe.net/mailman/listinfo/ripe-atlas-ambassadors
Well, if probe had remote configuration option to be controlled from RIPE atlas panel it would be nice. But you still need to bootstrap it. Perhaps IPv6 SLAAC instead? :)
On 24 груд. 2015, at 19:24, DurgaPrasad - DatasoftComnet <dp@datasoftcomnet.com> wrote:
A major problem in setting up these probes is that we cannot configure it directly with a static IP address. So it is getting limited to places where they have a DHCP server. I have many customers without a DHCP server due to some reasons of their own. I feel it is trivial to provide a default IP address if the probe is reset and leave it to them to convert it to DHCP if they choose.
Regards Durga Prasad +919849111010
From: RIPE-Atlas-Ambassadors [mailto:ripe-atlas-ambassadors-bounces@ripe.net] On Behalf Of Gil Bahat Sent: 24 December 2015 19:53 To: ripe-atlas-ambassadors@ripe.net Subject: Re: [RIPE Atlas Ambassadors] News and Happy Holidays!
Thanks and keep up the good work. we'd really appreciate more probes around the world and we're already putting them to good use.
I'm happy to report from Israel that we increased coverage by ~33% and many more coming along the way.
Here is some feedback I would like to share about the process:
1. There are many people here without USB ports on their routers or the USB port unpowered. it would be great if RIPE could provide kits with suitable power adaptors. as RIPE can buy them in bulk, it will probably be less costly than ambassadors providing these ourselves. 2. Not unrelated to the above, I added my own USB to power adaptor to one of the kits to help installation and it turned out faulty and caught fire. aside from embarrassment, this made people in the company a bit wary of hosting a probe. 3. People will chip in if explained that the credits will help our company deliver better service to our users. However, the current credit system forces me to register it under my name and not theirs. it would be better if at registration point, a user could permanently assign credits to a recipient or group. 4. Building up on the above, perhaps gamification and groups are a good way to encourage adoption. Seeing how many credits your group generated makes it a bit like a (positive) contest. 5. I have found trouble with getting coverage for mobile (3G/4G) networks. there are very few setups in which these are gateway'd to ethernet. as a case in point, we have a USB 3G adaptor as backup in the company and no one would mind if it's connected to a probe when it's unused (which is 99.99% of the time), but there is no physical port available for this (and possibly no CDC ethernet driver). another option might be to allow the probes to interface with mobile phones somehow, which would entail occasional access to these networks when a paired phone is nearby, but perhaps it would be better than nothing.
I've been using RIPE insofar to support a decision for selecting our company's next ISP as well as to ascertain and debug performance issues with our CDN provider. as we are deployed worldwide, every probe you can put in every country matters and helps us provide better service. again, much appreciated.
Happy holidays!
Regards,
Gil Bahat, DevOps Engineer, Magisto Ltd.
On Tue, Dec 22, 2015 at 4:29 PM, Alex Ojeda <alex@chilenetworks.com> wrote: Thanks :)
Alex Ojeda
On Tue, Dec 22, 2015 at 4:58 AM -0800, "Michela Galante" <mgalante@ripe.net> wrote:
Dear RIPE Atlas ambassadors,
It’s been a long time since we shared some news, and we have a lot to tell you about!
******** One million credits ********
Do you know that you have 1,000,000 RIPE Atlas credits as thanks for helping us build the largest Internet measurement network? Here are some ways you can take advantage of these credits to run your own measurements:
1) If a customer complains they can't reach your network, you can schedule a ping from 500 probes to diagnose where else in the world this problem is visible. Cost for a one-off ping measurement using 500 probes around the world: 3,000 credits. 2) If you suspect that there are reachability problems between your server and a specific network, you can perform traceroute measurements every 30 minutes from 50 probes located in a certain AS Number, or in a specified country. Daily cost: 72,000 credits. 3) Use DomainMON to monitor your own name servers: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-domainmon-is-... For example, you could schedule a measurement of 6 name servers for ripe.net with UDP SOA every hour from 10 probes. Daily cost: 28,800 credits.
View your own credits here: https://atlas.ripe.net/user/credits/ If you haven’t received the million credits yet, it means that none of your ambassador probes have been connected yet. Please chase your contacts and ask them to get their probes online!
******** 10% credits from your online ambassador probes ********
Since this is the holiday season, we believe our ambassadors deserve special recognition for their help. As an ambassador, you will now receive daily 10% of the credits that your ambassador probes generate when they are online. That means you’ll receive 2,160 credits every day for each of your ambassador probes that remain online.
******** Ambassador page improvements ********
The ambassador page has been improved. Besides being the place where you register the details of the people you gave the probes to, you can now find helpful information, including:
1) Tools for promoting RIPE Atlas 2) Communications: links to mailing list, conferences page and updates 3) How do I know where probes are needed? 4) How do I ask for more probes?
https://atlas.ripe.net/ambassadors/probes/
******** RIPE Atlas in multiple languages ********
You’ve asked us whether we can provide information about RIPE Atlas in other languages. We’ll soon have brochures available online in Spanish, Portuguese and French, with more languages coming. In the meantime, some community members have provided some information and we've collected their articles and blogs on GitHub. Take a look - and feel free to add your own: https://github.com/RIPE-Atlas-Community/multi-lingual-docs
It has been a great year for RIPE Atlas and we wish to thank you for your contribution! We hope we can count on your cooperation again next year.
Happy Holidays!
Michela, Lia & Vesna Measurements Community Building RIPE NCC
_______________________________________________ RIPE-Atlas-Ambassadors mailing list RIPE-Atlas-Ambassadors@ripe.net https://www.ripe.net/mailman/listinfo/ripe-atlas-ambassadors
_______________________________________________ RIPE-Atlas-Ambassadors mailing list RIPE-Atlas-Ambassadors@ripe.net https://www.ripe.net/mailman/listinfo/ripe-atlas-ambassadors
Hi all, Apologies for hijacking the list like this. On Sat, 26 Dec 2015 21:33:42 +0200 Dmitry Kohmanyuk wrote:
A major problem in setting up these probes is that we cannot configure it directly with a static IP address. So it is getting limited to places where they have a DHCP server. I have many customers without a DHCP server due to some reasons of their own.
Well, if probe had remote configuration option to be controlled from RIPE atlas panel it would be nice. But you still need to bootstrap it.
You can configure a probe to use static IP. I take it that most know this, but in case you have not found out: Log in on the ATLAS portal, select your probe, select the 'network' tab, and find that there are 'edit' buttons. Make your change there, when the probe connects to the network (for which it will need a DHCP-enabled network, alas), it will download the static-IP config and use it from then onwards. Two problems: 1. You need a DHCP-enabled network to bootstrap this; 2. You will need to change the probe BEFORE you change the network, so that the probe will get the new config (using the old network) before connectivity through the old network goes away. (using a button for "forget the net config and switch back to DHCP" may be a good idea) While I've done static config in the past for my probe, I find that just configuring DHCP to put the probe where I want it it to be a lot more convinient. The thing really is set up to "just connect to a network and forget". But, if you need static config to make the probe hookup fly, then it is can be done. Just don't expect it to be painless. Geert Jan
Dear Friends, Our whole objective is to make it easy for the hosts to deploy the devices and ensure uptime. So some hosts don't bother too much and just abandon the devices. DHCP is OK where we deploy in homes. The downside is that there will be lot of downtime. At night and sometimes during the day. The right locations would be offices where they would be powered on 24x7. However most of them do not have DHCP or have some authentication mechanism before they allow users to connect. In such scenarios the device should have a default IP which is available when we do a hard reset and then it is very easy to connect it to internet using their policy. Also most colleges do not support DHCP and they employ MAC authentication and give out static IPs to users. Our net objective is to ensure almost all Probes are Live all the time and they are not abandoned. Having an option of Default IP /Username/Password through RESET button would help things definitely. Regards Durga Prasad +919849111010 -----Original Message----- From: Geert Jan de Groot [mailto:GeertJan.deGroot@xs4all.nl] Sent: 27 December 2015 01:54 To: Dmitry Kohmanyuk Cc: DurgaPrasad - DatasoftComnet; <ripe-atlas-ambassadors@ripe.net> Subject: Re: [RIPE Atlas Ambassadors] News and Happy Holidays! Hi all, Apologies for hijacking the list like this. On Sat, 26 Dec 2015 21:33:42 +0200 Dmitry Kohmanyuk wrote:
A major problem in setting up these probes is that we cannot configure it directly with a static IP address. So it is getting limited to places where they have a DHCP server. I have many customers without a DHCP server due to some reasons of their own.
Well, if probe had remote configuration option to be controlled from RIPE atlas panel it would be nice. But you still need to bootstrap it.
You can configure a probe to use static IP. I take it that most know this, but in case you have not found out: Log in on the ATLAS portal, select your probe, select the 'network' tab, and find that there are 'edit' buttons. Make your change there, when the probe connects to the network (for which it will need a DHCP-enabled network, alas), it will download the static-IP config and use it from then onwards. Two problems: 1. You need a DHCP-enabled network to bootstrap this; 2. You will need to change the probe BEFORE you change the network, so that the probe will get the new config (using the old network) before connectivity through the old network goes away. (using a button for "forget the net config and switch back to DHCP" may be a good idea) While I've done static config in the past for my probe, I find that just configuring DHCP to put the probe where I want it it to be a lot more convinient. The thing really is set up to "just connect to a network and forget". But, if you need static config to make the probe hookup fly, then it is can be done. Just don't expect it to be painless. Geert Jan
Hello I totally agree. Most corporate segments that are internet DMZ facing will not have DHCP for obvious security reasons. The other side is if you put the device on your intranet, then our security folks start to get concerned if the device is compromised. I have multiple devices that are offline due to the this very reason and we originally had a goal of placing these worldwide. We need more flexibility with the device. Thanks Ken -----Original Message----- From: RIPE-Atlas-Ambassadors [mailto:ripe-atlas-ambassadors-bounces@ripe.net] On Behalf Of DurgaPrasad - DatasoftComnet Sent: 27 December 2015 06:11 To: 'Geert Jan de Groot'; 'Dmitry Kohmanyuk'; ripe-atlas-ambassadors@ripe.net Subject: Re: [RIPE Atlas Ambassadors] News and Happy Holidays! Dear Friends, Our whole objective is to make it easy for the hosts to deploy the devices and ensure uptime. So some hosts don't bother too much and just abandon the devices. DHCP is OK where we deploy in homes. The downside is that there will be lot of downtime. At night and sometimes during the day. The right locations would be offices where they would be powered on 24x7. However most of them do not have DHCP or have some authentication mechanism before they allow users to connect. In such scenarios the device should have a default IP which is available when we do a hard reset and then it is very easy to connect it to internet using their policy. Also most colleges do not support DHCP and they employ MAC authentication and give out static IPs to users. Our net objective is to ensure almost all Probes are Live all the time and they are not abandoned. Having an option of Default IP /Username/Password through RESET button would help things definitely. Regards Durga Prasad +919849111010 -----Original Message----- From: Geert Jan de Groot [mailto:GeertJan.deGroot@xs4all.nl] Sent: 27 December 2015 01:54 To: Dmitry Kohmanyuk Cc: DurgaPrasad - DatasoftComnet; <ripe-atlas-ambassadors@ripe.net> Subject: Re: [RIPE Atlas Ambassadors] News and Happy Holidays! Hi all, Apologies for hijacking the list like this. On Sat, 26 Dec 2015 21:33:42 +0200 Dmitry Kohmanyuk wrote:
A major problem in setting up these probes is that we cannot configure it directly with a static IP address. So it is getting limited to places where they have a DHCP server. I have many customers without a DHCP server due to some reasons of their own.
Well, if probe had remote configuration option to be controlled from RIPE atlas panel it would be nice. But you still need to bootstrap it.
You can configure a probe to use static IP. I take it that most know this, but in case you have not found out: Log in on the ATLAS portal, select your probe, select the 'network' tab, and find that there are 'edit' buttons. Make your change there, when the probe connects to the network (for which it will need a DHCP-enabled network, alas), it will download the static-IP config and use it from then onwards. Two problems: 1. You need a DHCP-enabled network to bootstrap this; 2. You will need to change the probe BEFORE you change the network, so that the probe will get the new config (using the old network) before connectivity through the old network goes away. (using a button for "forget the net config and switch back to DHCP" may be a good idea) While I've done static config in the past for my probe, I find that just configuring DHCP to put the probe where I want it it to be a lot more convinient. The thing really is set up to "just connect to a network and forget". But, if you need static config to make the probe hookup fly, then it is can be done. Just don't expect it to be painless. Geert Jan _______________________________________________ RIPE-Atlas-Ambassadors mailing list RIPE-Atlas-Ambassadors@ripe.net https://www.ripe.net/mailman/listinfo/ripe-atlas-ambassadors
Hi all, I believe there is a delicate balance to strike here. The current ATLAS probe design does not need any sort of user-facing interface, and this is probably a good thing. Then you have, on the higher end, the ATLAS anchors, which do have at least a console you could conceivably connect and have more flexibilty, but the cost is much higher. Maybe what is needed is something in between. cheers! -Carlos On 12/27/2015 9:08 AM, Tucker, Ken wrote:
Hello
I totally agree. Most corporate segments that are internet DMZ facing will not have DHCP for obvious security reasons. The other side is if you put the device on your intranet, then our security folks start to get concerned if the device is compromised.
I have multiple devices that are offline due to the this very reason and we originally had a goal of placing these worldwide.
We need more flexibility with the device.
Thanks Ken
-----Original Message----- From: RIPE-Atlas-Ambassadors [mailto:ripe-atlas-ambassadors-bounces@ripe.net] On Behalf Of DurgaPrasad - DatasoftComnet Sent: 27 December 2015 06:11 To: 'Geert Jan de Groot'; 'Dmitry Kohmanyuk'; ripe-atlas-ambassadors@ripe.net Subject: Re: [RIPE Atlas Ambassadors] News and Happy Holidays!
Dear Friends, Our whole objective is to make it easy for the hosts to deploy the devices and ensure uptime. So some hosts don't bother too much and just abandon the devices. DHCP is OK where we deploy in homes. The downside is that there will be lot of downtime. At night and sometimes during the day. The right locations would be offices where they would be powered on 24x7. However most of them do not have DHCP or have some authentication mechanism before they allow users to connect. In such scenarios the device should have a default IP which is available when we do a hard reset and then it is very easy to connect it to internet using their policy. Also most colleges do not support DHCP and they employ MAC authentication and give out static IPs to users. Our net objective is to ensure almost all Probes are Live all the time and they are not abandoned. Having an option of Default IP /Username/Password through RESET button would help things definitely.
Regards Durga Prasad +919849111010
-----Original Message----- From: Geert Jan de Groot [mailto:GeertJan.deGroot@xs4all.nl] Sent: 27 December 2015 01:54 To: Dmitry Kohmanyuk Cc: DurgaPrasad - DatasoftComnet; <ripe-atlas-ambassadors@ripe.net> Subject: Re: [RIPE Atlas Ambassadors] News and Happy Holidays!
Hi all,
Apologies for hijacking the list like this.
On Sat, 26 Dec 2015 21:33:42 +0200 Dmitry Kohmanyuk wrote:
A major problem in setting up these probes is that we cannot configure it directly with a static IP address. So it is getting limited to places where they have a DHCP server. I have many customers without a DHCP server due to some reasons of their own. Well, if probe had remote configuration option to be controlled from RIPE atlas panel it would be nice. But you still need to bootstrap it. You can configure a probe to use static IP. I take it that most know this, but in case you have not found out:
Log in on the ATLAS portal, select your probe, select the 'network' tab, and find that there are 'edit' buttons. Make your change there, when the probe connects to the network (for which it will need a DHCP-enabled network, alas), it will download the static-IP config and use it from then onwards.
Two problems: 1. You need a DHCP-enabled network to bootstrap this; 2. You will need to change the probe BEFORE you change the network, so that the probe will get the new config (using the old network) before connectivity through the old network goes away. (using a button for "forget the net config and switch back to DHCP" may be a good idea)
While I've done static config in the past for my probe, I find that just configuring DHCP to put the probe where I want it it to be a lot more convinient. The thing really is set up to "just connect to a network and forget".
But, if you need static config to make the probe hookup fly, then it is can be done. Just don't expect it to be painless.
Geert Jan
_______________________________________________ RIPE-Atlas-Ambassadors mailing list RIPE-Atlas-Ambassadors@ripe.net https://www.ripe.net/mailman/listinfo/ripe-atlas-ambassadors
_______________________________________________ RIPE-Atlas-Ambassadors mailing list RIPE-Atlas-Ambassadors@ripe.net https://www.ripe.net/mailman/listinfo/ripe-atlas-ambassadors
Agreed There might be some logic in the design. But if we give this option then there is a greater chance that probes will not be abandoned. Needless to add - This will result in great savings and the make program further succeed. I will relate my personal experience. One day I travelled into Interior areas of my state and found two colleges willing to host probes. Both had static IPs and MAC based authentication. We tried to setup a quick DHCP server but the administrators got less and less interested as we had to hunt for a Server/PC in one place and in another place they had to take permission with their Head but was not around. We ran out of time and abandoned the effort. Maybe we need more motivated hosts but that is not the point here. Result the opportunity to put two devices in Interior areas (read: blanks in the MAP) lost. Regards Durga Prasad +919849111010 -----Original Message----- From: Carlos M. Martinez [mailto:carlos@lacnic.net] Sent: 27 December 2015 19:14 To: Tucker, Ken; DurgaPrasad - DatasoftComnet; 'Geert Jan de Groot'; 'Dmitry Kohmanyuk'; ripe-atlas-ambassadors@ripe.net Subject: Re: [RIPE Atlas Ambassadors] News and Happy Holidays! Hi all, I believe there is a delicate balance to strike here. The current ATLAS probe design does not need any sort of user-facing interface, and this is probably a good thing. Then you have, on the higher end, the ATLAS anchors, which do have at least a console you could conceivably connect and have more flexibilty, but the cost is much higher. Maybe what is needed is something in between. cheers! -Carlos On 12/27/2015 9:08 AM, Tucker, Ken wrote:
Hello
I totally agree. Most corporate segments that are internet DMZ facing will not have DHCP for obvious security reasons. The other side is if you put the device on your intranet, then our security folks start to get concerned if the device is compromised.
I have multiple devices that are offline due to the this very reason and we originally had a goal of placing these worldwide.
We need more flexibility with the device.
Thanks Ken
-----Original Message----- From: RIPE-Atlas-Ambassadors [mailto:ripe-atlas-ambassadors-bounces@ripe.net] On Behalf Of DurgaPrasad - DatasoftComnet Sent: 27 December 2015 06:11 To: 'Geert Jan de Groot'; 'Dmitry Kohmanyuk'; ripe-atlas-ambassadors@ripe.net Subject: Re: [RIPE Atlas Ambassadors] News and Happy Holidays!
Dear Friends, Our whole objective is to make it easy for the hosts to deploy the devices and ensure uptime. So some hosts don't bother too much and just abandon the devices. DHCP is OK where we deploy in homes. The downside is that there will be lot of downtime. At night and sometimes during the day. The right locations would be offices where they would be powered on 24x7. However most of them do not have DHCP or have some authentication mechanism before they allow users to connect. In such scenarios the device should have a default IP which is available when we do a hard reset and then it is very easy to connect it to internet using their policy. Also most colleges do not support DHCP and they employ MAC authentication and give out static IPs to users. Our net objective is to ensure almost all Probes are Live all the time and they are not abandoned. Having an option of Default IP /Username/Password through RESET button would help things definitely.
Regards Durga Prasad +919849111010
-----Original Message----- From: Geert Jan de Groot [mailto:GeertJan.deGroot@xs4all.nl] Sent: 27 December 2015 01:54 To: Dmitry Kohmanyuk Cc: DurgaPrasad - DatasoftComnet; <ripe-atlas-ambassadors@ripe.net> Subject: Re: [RIPE Atlas Ambassadors] News and Happy Holidays!
Hi all,
Apologies for hijacking the list like this.
On Sat, 26 Dec 2015 21:33:42 +0200 Dmitry Kohmanyuk wrote:
A major problem in setting up these probes is that we cannot configure it directly with a static IP address. So it is getting limited to places where they have a DHCP server. I have many customers without a DHCP server due to some reasons of their own. Well, if probe had remote configuration option to be controlled from RIPE atlas panel it would be nice. But you still need to bootstrap it. You can configure a probe to use static IP. I take it that most know this, but in case you have not found out:
Log in on the ATLAS portal, select your probe, select the 'network' tab, and find that there are 'edit' buttons. Make your change there, when the probe connects to the network (for which it will need a DHCP-enabled network, alas), it will download the static-IP config and use it from then onwards.
Two problems: 1. You need a DHCP-enabled network to bootstrap this; 2. You will need to change the probe BEFORE you change the network, so that the probe will get the new config (using the old network) before connectivity through the old network goes away. (using a button for "forget the net config and switch back to DHCP" may be a good idea)
While I've done static config in the past for my probe, I find that just configuring DHCP to put the probe where I want it it to be a lot more convinient. The thing really is set up to "just connect to a network and forget".
But, if you need static config to make the probe hookup fly, then it is can be done. Just don't expect it to be painless.
Geert Jan
_______________________________________________ RIPE-Atlas-Ambassadors mailing list RIPE-Atlas-Ambassadors@ripe.net https://www.ripe.net/mailman/listinfo/ripe-atlas-ambassadors
_______________________________________________ RIPE-Atlas-Ambassadors mailing list RIPE-Atlas-Ambassadors@ripe.net https://www.ripe.net/mailman/listinfo/ripe-atlas-ambassadors
On 2015/12/27 13:08 , Tucker, Ken wrote:
I totally agree. Most corporate segments that are internet DMZ facing will not have DHCP for obvious security reasons. The other side is if you put the device on your intranet, then our security folks start to get concerned if the device is compromised.
I have multiple devices that are offline due to the this very reason and we originally had a goal of placing these worldwide.
We need more flexibility with the device.
A few comments: 1) Static configuration is supported. 2) Realistically, static config requires DHCP 'nearby'. It is a assumed that just about everybody has a network with DHCP somewhere. If you need to configure the probe, put it in the DHCP network, configure the probe and plug into the target network. Unfortunately, if the USB get corrupted, or otherwise becomes unusable, you need a DHCP network again to reflash the USB stick. Note that even a laptop that has both wifi and ethernet can create a network with DHCP. Is there something that can be done about this DHCP dependency? Probably yes. But are there really that many places in the world where people even at home don't have DHCP (or have laptops that can provide DHCP). I sort of doubt it. In the past, just about every aspect of static configuration has caused problems. Probes are most reliable when they don't have to store state. So I'd prefer not to change anything in this respect.
On 24 Dec 2015, at 16:22, Gil Bahat wrote:
3. People will chip in if explained that the credits will help our company deliver better service to our users. However, the current credit system forces me to register it under my name and not theirs. it would be better if at registration point, a user could permanently assign credits to a recipient or group.
i’m not sure why this is the case. i have exactly one probe registered in my name, and have distributed a few hundred. it’s easy enough, in an organisation, to have a general alias (eg. ripe-probes@example.isp.com) to which something like the network team/whomever can have access to. presumably this is a trusted group so tracking things like credits usage, etc. is a non-issue?
4. Building up on the above, perhaps gamification and groups are a good way to encourage adoption. Seeing how many credits your group generated makes it a bit like a (positive) contest. 5. I have found trouble with getting coverage for mobile (3G/4G) networks. there are very few setups in which these are gateway'd to ethernet. as a case in point, we have a USB 3G adaptor as backup in the company and no one would mind if it's connected to a probe when it's unused (which is 99.99% of the time), but there is no physical port available for this (and possibly no CDC ethernet driver). another option might be to allow the probes to interface with mobile phones somehow, which would entail occasional access to these networks when a paired phone is nearby, but perhaps it would be better than nothing.
my general rule of thumb has been to advise *AGAINST* deployment in mobile networks (or more correctly, against deployment in usage-based-billing networks), unless the organisation/individual understands the costs attached to this. since the majority of mobile accounts are limited to some silly data-cap, after which it becomes exorbitantly expensive, and even a relatively idle probe, can consume up to 2.5GB of data a month. that’s a nasty surprise for someone that wasn’t expecting to see this data usage. ymmv. —n.
On Fri, Dec 25, 2015 at 9:56 AM, Nishal Goburdhan <nishal@controlfreak.co.za
wrote:
On 24 Dec 2015, at 16:22, Gil Bahat wrote:
3. People will chip in if explained that the credits will help our company
deliver better service to our users. However, the current credit system forces me to register it under my name and not theirs. it would be better if at registration point, a user could permanently assign credits to a recipient or group.
i’m not sure why this is the case. i have exactly one probe registered in my name, and have distributed a few hundred. it’s easy enough, in an organisation, to have a general alias (eg. ripe-probes@example.isp.com) to which something like the network team/whomever can have access to. presumably this is a trusted group so tracking things like credits usage, etc. is a non-issue?
4. Building up on the above, perhaps gamification and groups are a good way
to encourage adoption. Seeing how many credits your group generated makes it a bit like a (positive) contest. 5. I have found trouble with getting coverage for mobile (3G/4G) networks. there are very few setups in which these are gateway'd to ethernet. as a case in point, we have a USB 3G adaptor as backup in the company and no one would mind if it's connected to a probe when it's unused (which is 99.99% of the time), but there is no physical port available for this (and possibly no CDC ethernet driver). another option might be to allow the probes to interface with mobile phones somehow, which would entail occasional access to these networks when a paired phone is nearby, but perhaps it would be better than nothing.
my general rule of thumb has been to advise *AGAINST* deployment in mobile networks (or more correctly, against deployment in usage-based-billing networks), unless the organisation/individual understands the costs attached to this. since the majority of mobile accounts are limited to some silly data-cap, after which it becomes exorbitantly expensive, and even a relatively idle probe, can consume up to 2.5GB of data a month. that’s a nasty surprise for someone that wasn’t expecting to see this data usage. ymmv.
tricky thing that, because those are networks with poor ATLAS coverage and in high demand (at least for us, we're a mobile app developer). I had 2 ways to approach this: 1. try to utilize idle backup connections at companies which otherwise use 3g/4g as a passive backup. I believe I'm going to have 2 such installations soon. 2. appeal directly to mobile operators to donate the equipment and bandwidth to host these probes. this is harder because there is no spare USB port on the probes themselves, so they either need to place them at their NOC (so it's not as representative) or bear the costs themselves. insofar no luck yet, though i'm trying to pull some leverage as a potential customer. 3. of course, if you're lucky enough to have no-cap plans in your country, you might be able to convince someone to do it. Gil
—n.
participants (10)
-
Alex Ojeda -
Carlos M. Martinez -
Dmitry Kohmanyuk -
DurgaPrasad - DatasoftComnet -
Geert Jan de Groot -
Gil Bahat -
Michela Galante -
Nishal Goburdhan -
Philip Homburg -
Tucker, Ken