[atlas] Re: Subject-line in (dis)connect mails

[Daniel Suchy via ripe-atlas]

Hi,

On 9/11/24 2:24 PM, Gert Doering wrote:

I was wondering if it is possible to bring dis- and reconnect messages of
RIPE Atlas probes more in line with each other.

"In-Reply-To:" and/or "References:", please, so my MUA can nicely sort
these together.


This might be harder, as you have to store message-id of original
notification sent to each particular user in database. I think this is
"stateless" now (just sending notification about status change).


The system knows when the probe disappeared, so has a timestamp that can
be used to generate (togehter with the probe ID) a unique message ID
which can be reconstructed on the second & further mails...

Since there is an connect/disconnect history in the web page, the system
very likely already stores all necessary details :-)


If I look on message headers, notifications messages are sent from 
somewhat random workers. And worker hostname is now part of message id 
(sure, this can be changed to something more generic). I'm not saying 
it's not possible, but proper analysis needs to be performed.


- Daniel


Gert Doering
 -- NetMaster


-
To unsubscribe from this mailing list or change your subscription options, 
please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. 
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/

[atlas] Re: Subject-line in (dis)connect mails

[Daniel Suchy via ripe-atlas]

On 9/11/24 1:50 PM, Gert Doering wrote:

I was wondering if it is possible to bring dis- and reconnect messages of
RIPE Atlas probes more in line with each other.

"In-Reply-To:" and/or "References:", please, so my MUA can nicely sort
these together.


This might be harder, as you have to store message-id of original 
notification sent to each particular user in database. I think this is 
"stateless" now (just sending notification about status change).


- Daniel
-
To unsubscribe from this mailing list or change your subscription options, 
please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. 
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/

[atlas] Re: probes do not register

[Daniel Suchy via ripe-atlas]

Hello,

On 9/10/24 8:24 PM, Robert Kisteleki wrote:

I'd like to thank you for reporting this, since as a consequence we
saw that other probes may experience similar issues and applied the
same solution to those.

even though i realize i am being a pita, i always report problems
because others might have them.

This mailing list (and the RIPE Forum, Twitter, ...) are not really
the best venues for individual support; we have the ticketed
atlas@ripe for that. However, in most cases it's hard to know in
advance if something is an isolated case or not. While we*prefer*
tickets, such a public ask for assistance is also ok.


But it is necessary to admit that many current problems have a global 
basis... this will of course be hidden in your tickets...


The information on the mailing list is better, one does not have to 
panic and open individual tickets because of a global problem... which 
are quite recurring...


if I read here that others have the same problem, I have no reason to 
open an individual ticket. Answering dozens of the same tickets also 
takes time, doesn't it?


- Daniel
-
To unsubscribe from this mailing list or change your subscription options, 
please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. 
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/

[atlas] Re: RIPE Atlas Infra IP Rages

[Daniel Suchy via ripe-atlas]

On 8/19/24 3:50 PM, Nick Hilliard wrote:

Milad Afshari wrote on 19/08/2024 14:32:

Thanks for your messages.
I'm exactly looking for the RIPE controller infrastructure IP 
addresses, explaining my use case might be a bit tough, but consider a 
situation where I need to provide specific routes for my probes 
towards the controller nodes to ensure they have stable network 
connectivity.


the RIPE NCC uses AS, so the ip address blocks announced on this ASN 
can be looked up here:


https://irrexplorer.nlnog.net/asn/AS

These address blocks haven't changed since the Atlas project started, so 
they're stable in practice. But the RIPE NCC have never committed to 
keeping the controllers on these IPs, so it's possible they could change 
in future.


Probe connects to controller, which aren't always within AS.

There was similar question ~2yrs back [1], and here we can deduce that 
controllers are in different AS, not only within AS.


- Daniel

[1] 
https://www.ripe.net/ripe/mail/archives/ripe-atlas/2022-January/004900.html


-
To unsubscribe from this mailing list or change your subscription options, 
please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. 
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/

Re: [atlas] Probe DHCPv6 support

[Daniel Suchy via ripe-atlas]

On 5/9/23 16:44, Philip Homburg wrote:

Does OpenWRT out of the box support DHVPv6? Did you ever try that? If it does, 
it may
help the Atlas team to just add the relevant OpenWRT packages.


Sure, it does (also prefix delegation works here).

- Daniel

--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] Probe 24434 down but pingable

[Daniel Suchy via ripe-atlas]

Isn't simply dead/corrupted USB flash? (as I see, you're using 
tl-mr3020; there're such issues sometimes).


There's article how to fix that...
https://labs.ripe.net/author/philip_homburg/troubleshooting-ripe-atlas-probes-usb-sticks/

On 12/30/22 10:04, Dave wrote:

Hi,

One of my probes is pingable but the status is disconnected for over a 
day. Could it be that it has troubles with DNS over IPv6 and that it is 
not smart enough to fall back to IPv4?


https://atlas.ripe.net/probes/24434/#tab-general 



Thanks,
Dave



--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] Proposal: Remove support for non-public measurements [ONLY-PUBLIC]

[Daniel Suchy via ripe-atlas]

Hello,
I support Gert here, network operators (LIRs) can have valid reasons to 
make some their measurements non-public. So I don't support removal of 
this feature. It's a bad idea...


If some probe host has problem with that, why don't mark such probes as 
not-available for private measurements (this can be implemented easily)? 
And I think there will be only minority of probes marked like that. 
Majority of hosts will not care at all...


And keep in mind that Atlas is funded by LIRs and their money. All the 
big-data infrastructure (and also making of hardware probes) costs real 
(and not small) money. Existence of rivate measurements might be one 
reason, why LIRs allow spending money for this useful project. Probe 
hosting is only small piece in expenses within this project...


- Daniel

On 12/16/22 19:13, Gert Doering wrote:

Hi,

On Thu, Dec 15, 2022 at 10:41:42AM -0800, Steve Gibbard wrote:

Atlas, and the RIPE NCC, have two fairly separate constituencies:  researchers 
and operators.


This.

Operators (like me) are willing to host Atlas anchors and probes, and
thus contribute to the system.

I might be troubleshooting something in our network where I have no
interest in making the results public.  So I value the option to have
non-public measurements.

There's no "right to see all measurements" here - if someone wants to
see something, they are free to run their own measurements with their
own credits.  What I do with my credits (which do not come for free)
and who can see the results should be my decision.

Gert Doering
 -- NetMaster




--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas