Re: Did your BGP crash today?
On Mon, 2010-08-30 at 10:58 +0200, Thomas Mangin wrote: > http://www.faqs.org/rfcs/rfc4271.html section 4.2 > > So unless you know something I don't, I believe you are totally mistaken :) updates serve as implicit keepalives. in that same section: "Hold Time: The calculated value indicates the maximum number of seconds that may elapse between the receipt of successive KEEPALIVE and/or UPDATE messages from the sender." also check section 6.5: "If a system does not receive successive KEEPALIVE, UPDATE, and/or NOTIFICATION messages [...]" --Daniel
Re: Cogent input
On Jun 11, 2009, at 5:28 PM, Raymond Dijkxhoorn wrote: Not from what i have been told, but hey i am not working there. We got a v6 transit offer as pilot from them so perhaps they are moving towards live service Would not be strange in this current stage... same thing here. routing table still looks pretty empty though: dan...@jun1.bit-2a> show route aspath-regex ".* 174 .*" table inet6.0 | match BGP | count Count: 0 lines --Daniel.
Re: Google Over IPV6
On Fri, 2009-03-27 at 08:18 -0400, Robert D. Scott wrote: > Any one making use of Google IPV6? yes. We participate in the Google IPv6 trial program so our recursors get records for www.google.com and so far it's been great, no issues whatsoever. dan...@jun1> traceroute www.google.com traceroute6 to www.l.google.com (2001:4860:a003::68) from 2001:7f8:1::a501:2859:2, 64 hops max, 12 byte packets 1 pr61.ams04.net.google.com (2001:7f8:1::a501:5169:1) 2.388 ms 1.798 ms 1.712 ms 2 2001:4860::23 (2001:4860::23) 8.664 ms 8.480 ms 8.364 ms 3 2001:4860:a003::68 (2001:4860:a003::68) 8.624 ms 8.639 ms 8.719 ms Regards, Daniel.
Re: Google Over IPV6
On Fri, 2009-03-27 at 09:34 -0400, Steven M. Bellovin wrote: > It's working for me, too, though I noticed that tcptraceroute (at least > the version I have) doesn't do well with ipv6.google.com. seems to work fine from over here: # tcptraceroute6 www.google.com 80 traceroute to www.google.com (2001:4860:a003::68) from 2001:7b8:3:30::, port 80, from port 62699, 30 hops max, 60 byte packets 1 2001:7b8:3:30::2 (2001:7b8:3:30::2) 0.505 ms 0.246 ms 0.228 ms 2 pr61.ams04.net.google.com (2001:7f8:1::a501:5169:1) 1.664 ms 1.619 ms 1.641 ms 3 2001:4860::23 (2001:4860::23) 220.972 ms 174.560 ms 120.445 ms 4 2001:4860:a003::68 (2001:4860:a003::68) 9.101 ms [open] 9.196 ms 9.055 ms # tcptraceroute6 -V traceroute6: TCP & UDP IPv6 traceroute tool 0.9.3 ($Rev: 483 $) --Daniel.
Re: AAAA on various websites, but they all forgot to enable them on their nameservers....
On Wed, Jun 8, 2011 at 11:28, Jeroen Massar wrote: > It is really nice that folks where able to put records on their > websites for only 24 hours, but they forgot to put in the glue on their > nameservers. agreed, but still better than juniper.net at the moment, glue seems to be completely gone at ultradns :P --Daniel.
