Re: RIPE is just more fun.
Michael Greb wrote: Barrett Lyon wrote: On Fri, Oct 26, 2007 at 03:42:27PM -0400, Leo Bicknell wrote: http://www.youtube.com/watch?v=_y36fG2Oba0 I yanked the mp3 out of the youtube flv: http://blyon.com/routers_died.mp3 -Barrett Better, now we just need a higher quality MP3 from the source :/ I've put the MP3 (the best quality we've got, unfortunately... had we known what to expect, we'd have increased the encoding quality a bit) up at http://www.mcvax.org/~jhma/ripe55song.mp3. Regards, James Sometimes it's much cheaper and easier to make people think that something works rather than actually make it work. After all, the result is, in all important aspects, the same. -- Douglas Adams
Re: BGP terminology question
NetSecGuy wrote: I understand AS is RIS itself, is this some kind of misconfig on their end? It seems to be announcing it's entire table every 5 minutes. This started late Friday and ended a few hours ago. FYI, AS is the RIPE NCC's production AS; the RIS project uses AS12654. There seems to be a difference between the behaviours of Cisco and Juniper routers when encountering the RIS's default keepalive value of 0. Cisco routers (and Zebra/Quagga boxes) seem to operate quite happily without keepalive processing while Junipers seem to tear down and restart the session after the holdtime expires -- result: 170,000 or so additional updates every holdtime-and-a-bit seconds. [Aside: shouldn't the session be refused at startup if a mutually agreeable keepalive value can't be negotiated rather than being allowed to flap like this?] This problem seems to occur when any RIS peer migrates from Cisco to Juniper. The only difference this time is that both ASes are operated by (different groups within) the RIPE NCC. James
