Відео

Listening to this in 2024, still on ipv4

Congrats' Digi Romania!

@as198570

RIPE NCC, You're awesome! Let's be friends, okay?

Still find myself on IPv6 migration projects in 2024 FFS 😱 ... so linked them to this video. 🤣

Thanks.

wow this is amazing where do i signup

Thank you for the beneficial talk Dr Qasim. Very informative!

First like :)

👍

2024 ... and we're finally, perhaps, seriously considering general IPv6 adoption (AWS etc...). And still revisiting this video for kicks and giggles. Thank-you for always making my day a little better!

This doesn’t work for IPv6 by design…

super explanation better than bard

Ufffff it backfired 😭

hi ripe. Is this a opensource web based RPKI implementation or it's a custom web app? Tnx

🤔 'PromoSM'

Can I apply even I am from Philippines? Willing to relocate at Amsterdam

Здравствуйте, а запись выложите?

The worst explanation ever

Klasse jungs! Weiter so - hört sich auf 0% Lautstärke gut an!🎶😎

10000000 like 👍

Nice socks!

Wow very nice❤️

This was really useful, thanks so much Suzanne and team! And congratulations on these wins!

Is there a community or forum where we can discuss probe issues?

This seems a bit insecure. Too easy to spoof router advertisement messages. I'm sure the vendors will release features similar to IP ARP inspection, IP Source Guard, and DHCP snooping to stop those kinds of attacks.

Why are there so many C Lint warning when compiling all this (including mixes between char* and char**, and unchecked buffer overflows using sprintf without length limits? Can(t this cause security issues and attacks on running probes to harvest them to perform DDoS attacks or installing spambots? In summary, is that package really safe, given it is running with root privilege with full internet access to perform worldwide tests?

I have a Atlas Probe v4. But since about one year, the micro-USB power cable is fused on the micro-USB connector, it can no longer be unplugged at all. Apparently, this was caused by a firmware update issue, causing the probe to consume much more than the 500mA max for which it was designed. The prob stopped working but could be rebooted and after it could finally get the corrected firmware version (apparently during boot, the CPU runs constantly at max speeed and max consumption, including when it is still attempting to download again a new firmware update: if the server is not responding immediately, the probe runs in a very tight loop; the CPU governor is not effective to regulate, the internal kernel is still running in single process mode, in the boottime preloader, and is unable to react to CPU power governing events: the probe can consuime more than 2A, and the micro-USB connector will start overheating, causing delivering the maximum 10 watts through tiny surfaces that may be partially touching the connector, which are not gold plated to maximize the effective surface, and the tin alloys will fuse, after that the surface of contact increases and the power density on contact decreases and can support the ~8-10 watts through it). But since then it has been working correctly without the power problem. on atlas.ripe.net, now it seems that the probe runs successfully (however the red LED behing the holes is very long to start blinking after a boot, even if atlas.ripe.net shows that it is connected and running, the green led is difficult to see it is on, because the red LED just beside is very shiny, and it seems to be really too bright and consuming more than expected. That red LED however will start linking about 10 minutes after successful boot. Is it possible that this non flashing red LED is causing the excessive power consumption at boot time? Wasn't there a hardware design problem in probe v4 (with a missing resistor to limit the current)?

Thanks :)

Good job and nice explanations Nathalie

Thanks much for your help

Now, actually so close to 2023, I remember and listen especially to the lyrics. After all, that was over 15 years ago and some of it has lost none of its relevance.

Hi Michel, why do you mention at 01:49 that a 2A adapter is required? I measured my V5 probe’s consumption and it never gets higher than 250 mA. It works great powered from a USB 2.0 port. Which can supply 500 mA. The V4 probe came with a 1A adapter, the V5 did not come with an adapter. Where did this 2A requirement come from?

Can you show me the tutorial or the article explaining about 464XLAT

Hi there! I need to tshoot a soft probe running on OpenWrt. It is up but at some time it just stops making measurements. The way I've found to solve the issue is to cicle disable/stop/enable/start the service. I wrote an email to ripe but received bot like answers. Thanks in advance

very good, it worked for me! An important point to be mentioned is that the docker instance needs to have access to the internet, with a port released, otherwise rip will not see the probe

Watching over Native IPv6 from my ISP Bahnhof and the communication operator Kurbit/Borlänge-energi ❤️

I'm too lazy, where is the part where they talk about Kiwifarms?

Explaination was to the point with great visuals. Really impressed by the technology used for making those slides. What did you guys use to make them?

Thanks :)

Very very cool

ｐｒｏｍｏｓｍ ✋

listening in htttp/3

Great job Ewan, summarizing in a highly comprehensive manner the complex world of Internet Registry.

Thank you! I was afraid the Internet will go down in the first days of war but it proved to be resilient

Pseudo Feminism is the cancer of the society and only promoting women and insulting men is a kind of Pseudo Feminism that everyone should keep in their mind.