This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Possible issue with DNS/tests getting stuck?
- Previous message (by thread): [atlas] Possible issue with DNS/tests getting stuck?
- Next message (by thread): [atlas] Possible issue with DNS/tests getting stuck?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Fri Jan 27 13:53:45 CET 2012
On 1/27/12 13:33 , Kyriacos Sakkas wrote: > > I have a statically configured probe, FW version 4270. If the internet > connection goes down/flaps the probe seems to get confused and stops > communicating (is shown as Down) even when the connection is back up and > stable, but can actually be pinged etc from inside and outside my > network fine. > > I have a second probe that is on DHCP (FW 4280) on a different network, > this one seems not to have the same issue, don't know which is the > important differentiator. > > Wondering if anyone has similar issues and a solution other than switch > it off and on again. > > Firmware version 4270 has an issue where if the connection to the controller goes down, it may not come back until the probe reboots. This fixed in 4280. It looks like your probe is now upgrading to 4280. Philip Homburg ps. it helps if you list probe ids when talking about specific probes. It saves me the time to figure out who you are and what probes you own.
- Previous message (by thread): [atlas] Possible issue with DNS/tests getting stuck?
- Next message (by thread): [atlas] Possible issue with DNS/tests getting stuck?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]