From old_mc_donald at hotmail.com Fri Oct 1 05:14:52 2004 From: old_mc_donald at hotmail.com (Gav) Date: Fri Oct 1 05:19:31 2004 Subject: [6bone] Supported Browsers References: <1096610585.17680.198.camel@lemy.ipv6.uni-muenster.de> Message-ID: Ok, thanks for all replies, am testing some of the others out, Christian Schild wrote :- | Please note that Netscape is based on Mozilla and therefore supports | IPv6 for some time now. IPv6 support in Netscapes older versions is | limited to unix platforms, but the latest version 7.2 talks IPv6 also on | Windows platforms (even the mail client does). Yep, thanks, I tested in 7.1 which is not that old, and it could not access my site nor sixxs,kame etc whereas the others all could. I will update to 7.2x . (Never used NS email client) Thanks. Gav... --- Checked for Viruses (Viri) , Gav... Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.771 / Virus Database: 518 - Release Date: 28/09/2004 From haesu at towardex.com Mon Oct 4 20:30:16 2004 From: haesu at towardex.com (James) Date: Mon Oct 4 20:31:41 2004 Subject: [6bone] Popular ways to automate IPv6 prefix filters Message-ID: <20041005033016.GA58374@scylla.towardex.com> Hi, I'm looking to hear some experiences from IPv6 operators today, who, if any are employing any methods to automate IPv6 bgp route filtering (e.g. RADB in IPv4, or RIPEdb, etc). I am particularly interested in hearing from any US or North American based operators if they do this right now with their production peers / transit providers. If so, I'm interested to hear which database they use to filter their customers or peers and any other interesting insight information. I know ALTDB for one now supports inet6num entries, but I am just not sure what the current popular methods are with respect to automated IPv6 filters at US regions. Basically I'm looking at setting up some Merit IRRd based registry for inet6num filtering at AS30071 for automating filtering with some of our members, and possibly use any popular databases out there today that support IPv6 to publish our inet6 information for BGP filtering as needed. Thanks for info! -J -- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net From dr at cluenet.de Wed Oct 27 02:42:44 2004 From: dr at cluenet.de (Daniel Roesen) Date: Wed Oct 27 02:45:32 2004 Subject: [6bone] Working contacts for T-Net.hu? They're going berserk Message-ID: <20041027094244.GB11835@srv01.cluenet.de> Low, does anyone have _working_ contacts for T-Net.hu AS29657 who can actually _fix_ things there? I've tried to contact them to fix up outdated prefix length filters with no success now for many weeks, but now they are finally going berserk: telnet grh.sixxs.net sh bgp neigh 3ffe:401c:0:3:20c:ceff:fe05:da0e routes They are announcing over half of all IPv6 BGP routes with their own AS as origin... One of the many examples where an unresponsive 6bone site hurts global IPv6 production connectivity. :-( Regards, Daniel -- CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0 From dr at cluenet.de Wed Oct 27 04:01:44 2004 From: dr at cluenet.de (Daniel Roesen) Date: Wed Oct 27 04:03:40 2004 Subject: [6bone] Working contacts for T-Net.hu? They're going berserk In-Reply-To: <20041027094244.GB11835@srv01.cluenet.de> References: <20041027094244.GB11835@srv01.cluenet.de> Message-ID: <20041027110144.GA13064@srv01.cluenet.de> On Wed, Oct 27, 2004 at 11:42:44AM +0200, Daniel Roesen wrote: > telnet grh.sixxs.net > sh bgp neigh 3ffe:401c:0:3:20c:ceff:fe05:da0e routes > > They are announcing over half of all IPv6 BGP routes with their own > AS as origin... Looks like this has been fixed now... Regards, Daniel -- CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0 From jeroen.valcke at belnet.be Wed Oct 27 04:14:03 2004 From: jeroen.valcke at belnet.be (Jeroen Valcke) Date: Wed Oct 27 04:15:39 2004 Subject: [6bone] Returning 6Bone IPv6 address space Message-ID: <20041027111403.GA23896@jeroen.fw.belnet.be> Dear, For a while now we (BELNET) stopped using our 6BONE IPv6 address space. I was advised to remove our data from the 6BONE whois database. Our colleague who used to maintain the 6BONE whois database has left and we have no record of the password to use for the updates. How can we solve this problem? Kind regards, -Jeroen- -- Jeroen Valcke From jeroen at unfix.org Wed Oct 27 04:33:36 2004 From: jeroen at unfix.org (Jeroen Massar) Date: Wed Oct 27 04:35:36 2004 Subject: [6bone] Returning 6Bone IPv6 address space In-Reply-To: <20041027111403.GA23896@jeroen.fw.belnet.be> References: <20041027111403.GA23896@jeroen.fw.belnet.be> Message-ID: <1098876816.3590.180.camel@firenze.zurich.ibm.com> On Wed, 2004-10-27 at 13:14 +0200, Jeroen Valcke wrote: > Dear, > > For a while now we (BELNET) stopped using our 6BONE IPv6 address space. Since 2003-11-01 05:10:39 as far as I can see with GRH ;) I've marked it as returned in GRH so you won't see a red color there anymore. > I was advised to remove our data from the 6BONE whois database. When you are not using certain prefixes anymore you should remove those indeed. But as there is a *lot* of "historical" information in that registry it isn't really that bad if it remains. We always have things like these in there for instance: inet6num: 3FFE::/24 netname: ONLINE descr: IPv6 Network of online.org.ua country: UA admin-c: EAG-6BONE tech-c: EAG-6BONE notify: admin@online.org.ua mnt-by: ONLINE-MNT changed: admin@online.org.ua 20030628 source: 6BONE I am quite sure they never got a /24 ;) But 6bone will stop to exist 6/6/6 fortunately thus it is not a huge problem, as long as it does not cause any operational problems of course. > Our colleague who used to maintain the 6BONE whois database has left and > we have no record of the password to use for the updates. How can we > solve this problem? Contact David Kessens (david@iprg.nokia.com), he can fix that for you. Though I guess he will also read this message. Greets, Jeroen -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 240 bytes Desc: This is a digitally signed message part Url : http://mailman.isi.edu/pipermail/6bone/attachments/20041027/329eddb6/attachment.bin From dr at cluenet.de Wed Oct 27 05:09:19 2004 From: dr at cluenet.de (Daniel Roesen) Date: Wed Oct 27 05:11:38 2004 Subject: [6bone] Working contacts for T-Net.hu? They're going berserk In-Reply-To: <20041027110144.GA13064@srv01.cluenet.de> References: <20041027094244.GB11835@srv01.cluenet.de> <20041027110144.GA13064@srv01.cluenet.de> Message-ID: <20041027120919.GB13967@srv01.cluenet.de> On Wed, Oct 27, 2004 at 01:01:44PM +0200, Daniel Roesen wrote: > On Wed, Oct 27, 2004 at 11:42:44AM +0200, Daniel Roesen wrote: > > telnet grh.sixxs.net > > sh bgp neigh 3ffe:401c:0:3:20c:ceff:fe05:da0e routes > > > > They are announcing over half of all IPv6 BGP routes with their own > > AS as origin... > > Looks like this has been fixed now... And I have to add, that my claim that this specific case hurted global routing was plain wrong. Apologies. Neither does T-Net have any BGP downstreams, nor did T-Net announce those routes to their upstreams/peers. T-Net provides an unfiltered IBGP view to GRH, not a view a downstream customer would see. Best regards, Daniel -- CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0