Hi, Today we'll upgrade some of the central components of the system, including the UI. Please don't be surprised about service interruptions. Regards, Robert
On 2010.12.08. 9:05, Robert Kisteleki wrote:
Hi,
Today we'll upgrade some of the central components of the system, including the UI. Please don't be surprised about service interruptions.
Regards, Robert
The upgrade is now finished. Some of the new features are listed below. Internal stuff: * most of the NTP problems have been solved by the new firmware version 3900 * probes can use IPv6 to connect to the central infrastructure, provided that their assigned controller also supports it. We'll be deploying IPv6 on more controllers in the near future. UI stuff: * We replaced the geo mapping backend, which solves most (if not all) of the "my town is not found" issues * One can now enlarge the probe registration and re-geolocate dialogs so it's easier to pick your exact spot on the map * The "probe status" page now loads the sections separately, and it loads a bit faster. You can reload each section separately using the small button on the right hand side of the section header. * We added an uptime graph to visualise the probe's uptime. Small connectivity gaps (disconnect periods) don't really show up on this, as they are are much shorter than the connected periods, but one can see bigger downtimes (if they happen). * We have better IPv4/IPv6 reporting in the top section We also added some internal enhancements so that we can have more/better reporting in the future. These changes are not (yet) visible to the users. Regards, Robert
On 8 Dec 2010, at 05:46, Robert Kisteleki wrote:
On 2010.12.08. 9:05, Robert Kisteleki wrote:
Hi,
Today we'll upgrade some of the central components of the system, including the UI. Please don't be surprised about service interruptions.
Regards, Robert
The upgrade is now finished. Some of the new features are listed below.
Internal stuff: * most of the NTP problems have been solved by the new firmware version 3900 * probes can use IPv6 to connect to the central infrastructure, provided that their assigned controller also supports it. We'll be deploying IPv6 on more controllers in the near future.
that's nice! Will it do both IPv4 and IPv6 when available? From where my probe is, the IPv4 and the IPv6 path to amsterdam (or anywhere else) are quite different and so will the measurements be Joao
On 08.12 08:51, Joao Damas wrote:
that's nice! Will it do both IPv4 and IPv6 when available? From where my probe is, the IPv4 and the IPv6 path to amsterdam (or anywhere else) are quite different and so will the measurements be
The probes have always measured IPv6 when available. The new feature is that they can now talk to the RIPE Atlas infrastructure and report their results using IPv6. The rsults will be the same whether reported via IPv4 or IPv6, I would hope. ;-) :-) ;-) The funny thing is that it took much less effort than anticipated to make this happen. Hence it happened earlier than planned. Daniel
ah, OK, read it differently. Thanks for the clarification On 8 Dec 2010, at 09:20, Daniel Karrenberg wrote:
On 08.12 08:51, Joao Damas wrote:
that's nice! Will it do both IPv4 and IPv6 when available? From where my probe is, the IPv4 and the IPv6 path to amsterdam (or anywhere else) are quite different and so will the measurements be
The probes have always measured IPv6 when available. The new feature is that they can now talk to the RIPE Atlas infrastructure and report their results using IPv6. The rsults will be the same whether reported via IPv4 or IPv6, I would hope. ;-) :-) ;-)
The funny thing is that it took much less effort than anticipated to make this happen. Hence it happened earlier than planned.
Daniel
On 12/08/10 11:46, Robert Kisteleki wrote:
The upgrade is now finished. Some of the new features are listed below.
Is it just me, or doesn't the new UI work well with Google Chrome? I can make it to the 'My probes' page, but when I click on one, nothing happens. Works well with Firefox though. -- Marco
On 2010.12.08. 16:54, Marco Davids (SIDN) wrote:
On 12/08/10 11:46, Robert Kisteleki wrote:
The upgrade is now finished. Some of the new features are listed below.
Is it just me, or doesn't the new UI work well with Google Chrome?
I can make it to the 'My probes' page, but when I click on one, nothing happens.
Works well with Firefox though.
-- Marco
We rolled out some changes today which also touched the JavaScript libraries behind the pages. The problem should be solved if you reload the page with the browser's reload button. I think it works in FF because you opened up the Atlas page in FF just now, therefore "reloaded" the page. HTH, Robert
onsdag 08 december 2010 17:13:59 skrev Robert Kisteleki:
On 2010.12.08. 16:54, Marco Davids (SIDN) wrote:
On 12/08/10 11:46, Robert Kisteleki wrote:
The upgrade is now finished. Some of the new features are listed below.
Is it just me, or doesn't the new UI work well with Google Chrome?
I can make it to the 'My probes' page, but when I click on one, nothing happens.
Works well with Firefox though.
-- Marco
We rolled out some changes today which also touched the JavaScript libraries behind the pages. The problem should be solved if you reload the page with the browser's reload button.
I think it works in FF because you opened up the Atlas page in FF just now, therefore "reloaded" the page.
For me it didn't work with google chrome (7.0.517.8 dev) until I actively logged out and logged in again. /bengan
Hi, On 12/08/2010 11:46 AM, Robert Kisteleki wrote:
On 2010.12.08. 9:05, Robert Kisteleki wrote: * We have better IPv4/IPv6 reporting in the top section
the two probes on which I have access (156, currently don't know the other id) say for IPv6: Gateway: Undetermined/Unknown DNS Resolver: Undetermined/Unknown The probes have IPv6 connectivity so it should know it's gateway. Because a third probe of a colleague also shows undetermined/unknown I'm guessing this isn't yet implemented, right? (If this should work and you need the other probe ids to check something I can provide them next week) Second question: Can the probe get IPv6 resolvers over dhcpv6? If this should work I'm going to look at deploying dhcpv6 just for the probes. ;)
Regards, Robert
Thanks, Florian
On 10.12 17:57, Florian Obser wrote:
...
Gateway: Undetermined/Unknown DNS Resolver: Undetermined/Unknown
The probes have IPv6 connectivity so it should know it's gateway.
Indeed it does.
Because a third probe of a colleague also shows undetermined/unknown I'm guessing this isn't yet implemented, right? (If this should work and you need the other probe ids to check something I can provide them next week)
You are right, we intended 'undetermined' to mean that we do not have it implemented. It is on our list but not regarded as high priority. That whole section is intended to help debugging connectivity problems. Since there do not appear to be many of those it moved to a lower priority.
Second question: Can the probe get IPv6 resolvers over dhcpv6? If this should work I'm going to look at deploying dhcpv6 just for the probes. ;)
We have not implemented dhcpv6. Remember we are running uCLinux on a box with 8MB RAM and no MMU. How important is this? Daniel
On 12/11/2010 02:06 PM, Daniel Karrenberg wrote:
On 10.12 17:57, Florian Obser wrote: [...]
Second question: Can the probe get IPv6 resolvers over dhcpv6? If this should work I'm going to look at deploying dhcpv6 just for the probes. ;)
We have not implemented dhcpv6. Remember we are running uCLinux on a box with 8MB RAM and no MMU. How important is this?
Yes, I understand that. As to "important" I don't know, probably not. My motivation is something like: "ripe gave me two pieces of equipment it's my job to keep it running and provide it the best environment I can." The web interface indicated that the probe might be able to resolve over IPv6 so I started looking into how to provide the resolver. Teh googles seems to indicate that dhcpv6 is the way to go. Apparently one can also transport resolver information in router advertisements. I'm a static address configuration server guy so I have no idea what I'm talking about here ;) Anyway, before spending an hour or so to get dhcphv6 to work I asked first to find out if this has even a chance to work. On the other hand I'm personally very interested in running a v6 only network. It turns out it's a bit more complicated then just publishing AAAA records ;) That's why I'm always looking if some new piece of equipment or software can work in my v6 only network. However it's probably more useful to not artificially cut the probe of from the v4 internet.
Daniel
Thanks, Florian -- I remember yesterday, but the memory is in my head now. Was yesterday real? Or is it only the memory that is real?
participants (6)
-
Bengt Gördén -
Daniel Karrenberg -
Florian Obser -
Joao Damas -
Marco Davids (SIDN) -
Robert Kisteleki