From jeroen@unfix.org Sun Jan 4 20:44:53 2004 From: jeroen@unfix.org (Jeroen Massar) Date: Sun, 4 Jan 2004 21:44:53 +0100 Subject: [6bone] whois.6bone.net down? Message-ID: <006101c3d303$9ba1ca20$210d640a@unfix.org> -----BEGIN PGP SIGNED MESSAGE----- Hi, I just noticed that whois.6bone.net seems down over IPv4 and IPv6: jeroen@purgatory:~$ traceroute whois.6bone.net traceroute to whois.6bone.net (192.103.19.12), 64 hops max, 40 byte packets 1 nrp-1.bras-1.ams-tel.cistron.net (195.64.92.1) 59 ms 19 ms 19 ms 2 ve-4.rtr-1.ams-sar.cistron.net (62.216.29.1) 19 ms 18 ms 18 ms 3 ge10-0.mpr1.ams1.nl.mfnx.net (195.69.144.122) 19 ms 19 ms 18 ms 4 pos2-0.cr2.ams2.nl.above.net (208.184.231.254) 19 ms 18 ms 18 ms 5 so-4-0-0.cr2.lhr3.uk.above.net (64.125.31.157) 27 ms 25 ms 26 ms 6 so-0-0-0.cr1.lhr3.uk.above.net (208.184.231.145) 26 ms 26 ms 26 ms 7 so-7-0-0.cr1.dca2.us.above.net (64.125.31.186) 98 ms 98 ms 98 ms 8 so-0-0-0.cr2.dca2.us.above.net (208.184.233.122) 98 ms 99 ms 100 ms 9 so-6-3-0.mpr4.sjc2.us.above.net (64.125.30.166) 203 ms 195 ms 195 ms 10 so-0-0-0.er10a.sjc2.us.above.net (64.125.30.94) 206 ms 190 ms 200 ms 11 208.185.182.61.he.net (208.185.182.61) 199 ms 203 ms 204 ms 12 gige-g0-0-2.gsr12008.pao.he.net (65.19.156.125) 200 ms 194 ms 200 ms 13 65.19.141.238 (65.19.141.238) 172 ms 171 ms 170 ms 14 65.19.141.238 (65.19.141.238) 170 ms !H 171 ms !H 170 ms !H jeroen@purgatory:/etc/network$ traceroute6 whois.6bone.net traceroute to whois.6bone.net (2001:490:f000:1300::c) from 3ffe:8114:2000:240:290:27ff:fe24:c19f, 30 hops max, 16 byte packets 1 gw-20.ams-02.nl.sixxs.net (3ffe:8114:1000::26) 19.258 ms 19.361 ms 20.027 ms 2 Amsterdam.core.ipv6.intouch.net (2001:6e0::2) 47.478 ms 19.8 ms 19.743 ms 3 3ffe:800::fffb:0:0:5 (3ffe:800::fffb:0:0:5) 176.384 ms 324.368 ms 177.661 ms 4 2001:478:ffff::1e (2001:478:ffff::1e) 227.285 ms 217.023 ms 215.926 ms 5 3ffe:80a::3 (3ffe:80a::3) 213.368 ms 196.731 ms 196.995 ms 6 3ffe:1200:3012:1916::18 (3ffe:1200:3012:1916::18) 195.91 ms 193.864 ms 204.643 ms 7 2001:490:f000:1300::1 (2001:490:f000:1300::1) 2983.78 ms !H 2969.3 ms !H 2998.28 ms !H Is it a known problem? Greets, Jeroen -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / http://unfix.org/~jeroen iQA/AwUBP/h7NymqKFIzPnwjEQKdbACfYxyKHquMovjWG/ko9i2nCXNkN8UAn05R oslZMt4Q6fmwgrFKvqxI6nWz =iJ2M -----END PGP SIGNATURE----- From haesu@towardex.com Mon Jan 5 00:14:43 2004 From: haesu@towardex.com (haesu@towardex.com) Date: Sun, 4 Jan 2004 19:14:43 -0500 Subject: [6bone] whois.6bone.net down? In-Reply-To: <006101c3d303$9ba1ca20$210d640a@unfix.org> References: <006101c3d303$9ba1ca20$210d640a@unfix.org> Message-ID: <20040105001443.GA94438@scylla.towardex.com> It's been down for the past few days I noticed. Doesn't work for me either. -J On Sun, Jan 04, 2004 at 09:44:53PM +0100, Jeroen Massar wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > Hi, > > I just noticed that whois.6bone.net seems down over IPv4 and IPv6: > > jeroen@purgatory:~$ traceroute whois.6bone.net > traceroute to whois.6bone.net (192.103.19.12), 64 hops max, 40 byte packets > 1 nrp-1.bras-1.ams-tel.cistron.net (195.64.92.1) 59 ms 19 ms 19 ms > 2 ve-4.rtr-1.ams-sar.cistron.net (62.216.29.1) 19 ms 18 ms 18 ms > 3 ge10-0.mpr1.ams1.nl.mfnx.net (195.69.144.122) 19 ms 19 ms 18 ms > 4 pos2-0.cr2.ams2.nl.above.net (208.184.231.254) 19 ms 18 ms 18 ms > 5 so-4-0-0.cr2.lhr3.uk.above.net (64.125.31.157) 27 ms 25 ms 26 ms > 6 so-0-0-0.cr1.lhr3.uk.above.net (208.184.231.145) 26 ms 26 ms 26 ms > 7 so-7-0-0.cr1.dca2.us.above.net (64.125.31.186) 98 ms 98 ms 98 ms > 8 so-0-0-0.cr2.dca2.us.above.net (208.184.233.122) 98 ms 99 ms 100 ms > 9 so-6-3-0.mpr4.sjc2.us.above.net (64.125.30.166) 203 ms 195 ms 195 ms > 10 so-0-0-0.er10a.sjc2.us.above.net (64.125.30.94) 206 ms 190 ms 200 ms > 11 208.185.182.61.he.net (208.185.182.61) 199 ms 203 ms 204 ms > 12 gige-g0-0-2.gsr12008.pao.he.net (65.19.156.125) 200 ms 194 ms 200 ms > 13 65.19.141.238 (65.19.141.238) 172 ms 171 ms 170 ms > 14 65.19.141.238 (65.19.141.238) 170 ms !H 171 ms !H 170 ms !H > > jeroen@purgatory:/etc/network$ traceroute6 whois.6bone.net > traceroute to whois.6bone.net (2001:490:f000:1300::c) from 3ffe:8114:2000:240:290:27ff:fe24:c19f, 30 hops max, 16 byte packets > 1 gw-20.ams-02.nl.sixxs.net (3ffe:8114:1000::26) 19.258 ms 19.361 ms 20.027 ms > 2 Amsterdam.core.ipv6.intouch.net (2001:6e0::2) 47.478 ms 19.8 ms 19.743 ms > 3 3ffe:800::fffb:0:0:5 (3ffe:800::fffb:0:0:5) 176.384 ms 324.368 ms 177.661 ms > 4 2001:478:ffff::1e (2001:478:ffff::1e) 227.285 ms 217.023 ms 215.926 ms > 5 3ffe:80a::3 (3ffe:80a::3) 213.368 ms 196.731 ms 196.995 ms > 6 3ffe:1200:3012:1916::18 (3ffe:1200:3012:1916::18) 195.91 ms 193.864 ms 204.643 ms > 7 2001:490:f000:1300::1 (2001:490:f000:1300::1) 2983.78 ms !H 2969.3 ms !H 2998.28 ms !H > > Is it a known problem? > > Greets, > Jeroen > > -----BEGIN PGP SIGNATURE----- > Version: Unfix PGP for Outlook Alpha 13 Int. > Comment: Jeroen Massar / http://unfix.org/~jeroen > > iQA/AwUBP/h7NymqKFIzPnwjEQKdbACfYxyKHquMovjWG/ko9i2nCXNkN8UAn05R > oslZMt4Q6fmwgrFKvqxI6nWz > =iJ2M > -----END PGP SIGNATURE----- > > _______________________________________________ > 6bone mailing list > 6bone@mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone -- James Jun (formerly Haesu) TowardEX Technologies, Inc. 1740 Massachusetts Ave. Boxborough, MA 01719 Consulting, IPv4 & IPv6 colocation, web hosting, network design & implementation http://www.towardex.com | james@towardex.com Cell: (978)394-2867 | Office: (978)263-3399 Ext. 170 Fax: (978)263-0033 | AIM: GigabitEthernet0 NOC: http://www.twdx.net | POC: HAESU-ARIN, HDJ1-6BONE From hahn@berkom.de Mon Jan 5 08:14:29 2004 From: hahn@berkom.de (Christian Hahn) Date: Mon, 05 Jan 2004 09:14:29 +0100 Subject: [6bone] whois.6bone.net down? In-Reply-To: <006101c3d303$9ba1ca20$210d640a@unfix.org> References: <006101c3d303$9ba1ca20$210d640a@unfix.org> Message-ID: <3FF91CE5.3050702@berkom.de> Hi, happy new year to all. One of my scripts fetched the latest 6bone.db.gz on 31.12.03 around 3 in the morning. By now it's not working for me, neither IPv6 nor IPv4. traceroute to whois.6bone.net (2001:490:f000:1300::c), 30 hops max, 40 byte packets 1 * * * 2 e1-0-0-v6.r01.ipv6.berkom.de (2001:7a0:100:100:210:79ff:fecc:e820) 45.372 ms * 6.237 ms 3 tun0009-pop00-hurricane.tunnels.ipv6.icpnet.pl (3ffe:400c:feed::9) 211.630 ms 211.831 ms 210.840 ms 4 3ffe:80a::3 255.170 ms * * 5 3ffe:1200:3012:1916::18 260.261 ms 257.122 ms 256.110 ms 6 * * 2001:490:f000:1300::1(H!) 3056.350 ms traceroute to whois.6bone.net (192.103.19.12), 30 hops max, 40 byte packets 1 re1.berkom.de (141.39.12.3) 3.088 ms 2.693 ms 2.975 ms 2 ar-tuberlin1.g-win.dfn.de (188.1.33.65) 3.414 ms 2.596 ms 2.718 ms 3 cr-berlin1-po4-1.g-win.dfn.de (188.1.20.9) 3.569 ms 2.833 ms 2.876 ms 4 cr-frankfurt1-po9-2.g-win.dfn.de (188.1.18.185) 12.984 ms 12.022 ms 11.817 ms 5 ir-frankfurt2-po3-0.g-win.dfn.de (188.1.80.42) 12.788 ms 25.489 ms 12.308 ms 6 ge9-0.pr1.fra1.de.mfnx.net (216.200.116.97) 13.152 ms 11.794 ms 11.789 ms 7 so-0-1-0.cr2.fra1.de.mfnx.net (216.200.116.209) 13.911 ms 12.253 ms 11.915 ms 8 pos10-0.mpr1.ams1.nl.above.net (64.125.30.150) 19.093 ms 18.408 ms 18.412 ms 9 pos2-0.cr1.ams2.nl.above.net (208.184.231.54) 20.328 ms 18.846 ms 18.831 ms 10 so-5-0-0.cr1.lhr3.uk.above.net (64.125.31.153) 24.780 ms 25.338 ms 24.739 ms 11 so-7-0-0.cr1.dca2.us.above.net (64.125.31.186) 96.792 ms 97.616 ms 96.534 ms 12 so-3-0-0.mpr3.sjc2.us.mfnx.net (208.184.233.133) 162.780 ms 162.860 ms 162.864 ms 13 so-2-0-0.er10a.sjc2.us.above.net (64.125.30.90) 167.835 ms 167.751 ms 167.945 ms 14 208.185.182.61.he.net (208.185.182.61) 167.719 ms 168.591 ms 167.847 ms 15 gige-g0-0-2.gsr12008.pao.he.net (65.19.156.125) 168.656 ms 168.550 ms 168.597 ms 16 65.19.141.238 164.237 ms 164.301 ms 165.059 ms 17 65.19.141.238(H!) 164.783 ms (H!) 164.405 ms (H!) 164.129 ms cheers, Christian Jeroen Massar wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > Hi, > > I just noticed that whois.6bone.net seems down over IPv4 and IPv6: > > jeroen@purgatory:~$ traceroute whois.6bone.net > traceroute to whois.6bone.net (192.103.19.12), 64 hops max, 40 byte packets > 1 nrp-1.bras-1.ams-tel.cistron.net (195.64.92.1) 59 ms 19 ms 19 ms > 2 ve-4.rtr-1.ams-sar.cistron.net (62.216.29.1) 19 ms 18 ms 18 ms > 3 ge10-0.mpr1.ams1.nl.mfnx.net (195.69.144.122) 19 ms 19 ms 18 ms > 4 pos2-0.cr2.ams2.nl.above.net (208.184.231.254) 19 ms 18 ms 18 ms > 5 so-4-0-0.cr2.lhr3.uk.above.net (64.125.31.157) 27 ms 25 ms 26 ms > 6 so-0-0-0.cr1.lhr3.uk.above.net (208.184.231.145) 26 ms 26 ms 26 ms > 7 so-7-0-0.cr1.dca2.us.above.net (64.125.31.186) 98 ms 98 ms 98 ms > 8 so-0-0-0.cr2.dca2.us.above.net (208.184.233.122) 98 ms 99 ms 100 ms > 9 so-6-3-0.mpr4.sjc2.us.above.net (64.125.30.166) 203 ms 195 ms 195 ms > 10 so-0-0-0.er10a.sjc2.us.above.net (64.125.30.94) 206 ms 190 ms 200 ms > 11 208.185.182.61.he.net (208.185.182.61) 199 ms 203 ms 204 ms > 12 gige-g0-0-2.gsr12008.pao.he.net (65.19.156.125) 200 ms 194 ms 200 ms > 13 65.19.141.238 (65.19.141.238) 172 ms 171 ms 170 ms > 14 65.19.141.238 (65.19.141.238) 170 ms !H 171 ms !H 170 ms !H > > jeroen@purgatory:/etc/network$ traceroute6 whois.6bone.net > traceroute to whois.6bone.net (2001:490:f000:1300::c) from 3ffe:8114:2000:240:290:27ff:fe24:c19f, 30 hops max, 16 byte packets > 1 gw-20.ams-02.nl.sixxs.net (3ffe:8114:1000::26) 19.258 ms 19.361 ms 20.027 ms > 2 Amsterdam.core.ipv6.intouch.net (2001:6e0::2) 47.478 ms 19.8 ms 19.743 ms > 3 3ffe:800::fffb:0:0:5 (3ffe:800::fffb:0:0:5) 176.384 ms 324.368 ms 177.661 ms > 4 2001:478:ffff::1e (2001:478:ffff::1e) 227.285 ms 217.023 ms 215.926 ms > 5 3ffe:80a::3 (3ffe:80a::3) 213.368 ms 196.731 ms 196.995 ms > 6 3ffe:1200:3012:1916::18 (3ffe:1200:3012:1916::18) 195.91 ms 193.864 ms 204.643 ms > 7 2001:490:f000:1300::1 (2001:490:f000:1300::1) 2983.78 ms !H 2969.3 ms !H 2998.28 ms !H > > Is it a known problem? > > Greets, > Jeroen > > -----BEGIN PGP SIGNATURE----- > Version: Unfix PGP for Outlook Alpha 13 Int. > Comment: Jeroen Massar / http://unfix.org/~jeroen > > iQA/AwUBP/h7NymqKFIzPnwjEQKdbACfYxyKHquMovjWG/ko9i2nCXNkN8UAn05R > oslZMt4Q6fmwgrFKvqxI6nWz > =iJ2M > -----END PGP SIGNATURE----- > > _______________________________________________ > 6bone mailing list > 6bone@mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone From david@iprg.nokia.com Tue Jan 6 17:52:58 2004 From: david@iprg.nokia.com (David Kessens) Date: Tue, 6 Jan 2004 09:52:58 -0800 Subject: [6bone] 6bone registry Message-ID: <20040106095258.B20441@iprg.nokia.com> Hi, As some of you probably already noticed, the 6bone registry is experiencing some problems. I am trying my best to get everything back up as soon as possible but it will take me a bit more time as usual since both some hardware and software changes will be needed. In the mean time, thanks for your patience, David Kessens --- From david@iprg.nokia.com Tue Jan 6 20:03:11 2004 From: david@iprg.nokia.com (David Kessens) Date: Tue, 6 Jan 2004 12:03:11 -0800 Subject: [6bone] Re: 6bone registry Message-ID: <20040106120311.D20629@iprg.nokia.com> Everything should be working again. I hope this helps, David Kessens --- ----- Forwarded message from David Kessens ----- From: David Kessens To: 6bone@ISI.EDU Subject: [6bone] 6bone registry Date: Tue, 6 Jan 2004 09:52:58 -0800 Hi, As some of you probably already noticed, the 6bone registry is experiencing some problems. I am trying my best to get everything back up as soon as possible but it will take me a bit more time as usual since both some hardware and software changes will be needed. In the mean time, thanks for your patience, David Kessens --- ----- End forwarded message ----- From hahn@berkom.de Wed Jan 7 09:28:01 2004 From: hahn@berkom.de (Christian Hahn) Date: Wed, 07 Jan 2004 10:28:01 +0100 Subject: [6bone] Re: 6bone registry In-Reply-To: <20040106120311.D20629@iprg.nokia.com> References: <20040106120311.D20629@iprg.nokia.com> Message-ID: <3FFBD121.1040204@berkom.de> Yes it works, my script which usually fetches the 6bone.db on Wednesday morning was able to get it :) Thank you for the work, Christian Hahn David Kessens wrote: > Everything should be working again. > > I hope this helps, > > David Kessens > --- > > ----- Forwarded message from David Kessens ----- > > From: David Kessens > To: 6bone@ISI.EDU > Subject: [6bone] 6bone registry > Date: Tue, 6 Jan 2004 09:52:58 -0800 > > > Hi, > > As some of you probably already noticed, the 6bone registry is > experiencing some problems. I am trying my best to get everything back > up as soon as possible but it will take me a bit more time as usual > since both some hardware and software changes will be needed. > > In the mean time, thanks for your patience, > > David Kessens > --- > > ----- End forwarded message ----- > _______________________________________________ > 6bone mailing list > 6bone@mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone From mamthabc@yahoo.co.in Fri Jan 9 04:40:25 2004 From: mamthabc@yahoo.co.in (=?iso-8859-1?q?Mamatha=20Balachandra?=) Date: Fri, 9 Jan 2004 04:40:25 +0000 (GMT) Subject: [6bone] Re: about transition from ipv4 to ipv6 In-Reply-To: <200401072005.i07K56N18651@gamma.isi.edu> Message-ID: <20040109044025.9387.qmail@web8303.mail.in.yahoo.com> --0-1877339065-1073623225=:7858 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Dear Sir I am M.tech (Computer Science) student. I am doing my project as "performance measure in various transition mechanisms from ipv4 to ipv6". I am using Red Hat Linux 8.0. I am using 2 methods: Dual stack and Tunneling. In Dual stack I implemented Client-Server communication. And I used ping and ping6 to check the performance such as rtt,throughput,packet loss. In tunneling I used sit interface and I am communicating 2 mechines (IPV6) and transmitting the packets between them to test the performance such as packet loss,throughput,rtt. Now my doubt is : how to change the name of sit interface in the output of ifconfig command? And even whatever I change in /usr/src/linux-2.4.20-8/net/ipv6/sit.c it wont be affected in the output of ifconfig. Please give me suggesions regarding this. Thanking You Mamtha 6bone-request@mailman.isi.edu wrote: Send 6bone mailing list submissions to 6bone@mailman.isi.edu To subscribe or unsubscribe via the World Wide Web, visit http://mailman.isi.edu/mailman/listinfo/6bone or, via email, send a message with subject or body 'help' to 6bone-request@mailman.isi.edu You can reach the person managing the list at 6bone-admin@mailman.isi.edu When replying, please edit your Subject line so it is more specific than "Re: Contents of 6bone digest..." Today's Topics: 1. Re: 6bone registry (David Kessens) 2. Re: Re: 6bone registry (Christian Hahn) --__--__-- Message: 1 Date: Tue, 6 Jan 2004 12:03:11 -0800 From: David Kessens To: 6bone@ISI.EDU Subject: [6bone] Re: 6bone registry Everything should be working again. I hope this helps, David Kessens --- ----- Forwarded message from David Kessens ----- From: David Kessens To: 6bone@ISI.EDU Subject: [6bone] 6bone registry Date: Tue, 6 Jan 2004 09:52:58 -0800 Hi, As some of you probably already noticed, the 6bone registry is experiencing some problems. I am trying my best to get everything back up as soon as possible but it will take me a bit more time as usual since both some hardware and software changes will be needed. In the mean time, thanks for your patience, David Kessens --- ----- End forwarded message ----- --__--__-- Message: 2 Date: Wed, 07 Jan 2004 10:28:01 +0100 From: Christian Hahn To: 6bone@ISI.EDU Subject: Re: [6bone] Re: 6bone registry Yes it works, my script which usually fetches the 6bone.db on Wednesday morning was able to get it :) Thank you for the work, Christian Hahn David Kessens wrote: > Everything should be working again. > > I hope this helps, > > David Kessens > --- > > ----- Forwarded message from David Kessens ----- > > From: David Kessens > To: 6bone@ISI.EDU > Subject: [6bone] 6bone registry > Date: Tue, 6 Jan 2004 09:52:58 -0800 > > > Hi, > > As some of you probably already noticed, the 6bone registry is > experiencing some problems. I am trying my best to get everything back > up as soon as possible but it will take me a bit more time as usual > since both some hardware and software changes will be needed. > > In the mean time, thanks for your patience, > > David Kessens > --- > > ----- End forwarded message ----- > _______________________________________________ > 6bone mailing list > 6bone@mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone --__--__-- _______________________________________________ 6bone mailing list 6bone@mailman.isi.edu http://mailman.isi.edu/mailman/listinfo/6bone End of 6bone Digest Yahoo! India Mobile: Ringtones, Wallpapers, Picture Messages and more.Download now. --0-1877339065-1073623225=:7858 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
 
 
Dear Sir
 
                 I am M.tech  (Computer Science)  student. I am doing my project as "performance measure in various transition mechanisms from ipv4 to ipv6". I am using Red Hat Linux 8.0.
 
I am using 2 methods: Dual stack and Tunneling.
 
In Dual stack I implemented  Client-Server communication. And I used ping and ping6 to check the performance such as rtt,throughput,packet loss.
 
In tunneling I used sit interface and I am communicating 2 mechines (IPV6) and transmitting the packets  between them to test the performance such as packet loss,throughput,rtt.

 
Now my doubt is : how to change the name of sit interface in the output of ifconfig command? And even whatever I change in /usr/src/linux-2.4.20-8/net/ipv6/sit.c it wont be affected in the output of ifconfig.
 
Please give me suggesions regarding this.
 
Thanking You
 
Mamtha

6bone-request@mailman.isi.edu wrote:
Send 6bone mailing list submissions to
6bone@mailman.isi.edu

To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.isi.edu/mailman/listinfo/6bone
or, via email, send a message with subject or body 'help' to
6bone-request@mailman.isi.edu

You can reach the person managing the list at
6bone-admin@mailman.isi.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of 6bone digest..."


Today's Topics:

1. Re: 6bone registry (David Kessens)
2. Re: Re: 6bone registry (Christian Hahn)

--__--__--

Message: 1
Date: Tue, 6 Jan 2004 12:03:11 -0800
From: David Kessens
To: 6bone@ISI.EDU
Subject: [6bone] Re: 6bone registry


Everything should be working again.

I hope this helps,

David Kessens
---

----- Forwarded message from David Kessens -----

From: David Kessens
To: 6bone@ISI.EDU
Subject: [6bone] 6bone registry
Date: Tue, 6 Jan 2004 09:52:58 -0800


Hi,

As some of you probably already noticed, the 6bone registry is
experiencing some problems. I am trying my best to get everything back
up as soon as possible but it will take me a bit more time as usual
since both some hardware and software changes will be needed.

In the mean time, thanks for your patience,

David Kessens
---

----- End forwarded message -----

--__--__--

Message: 2
Date: Wed, 07 Jan 2004 10:28:01 +0100
From: Christian Hahn
To: 6bone@ISI.EDU
Subject: Re: [6bone] Re: 6bone registry

Yes it works, my script which usually fetches the 6bone.db on
Wednesday morning was able to get it :)

Thank you for the work,
Christian Hahn

David Kessens wrote:
> Everything should be working again.
>
> I hope this helps,
>
> David Kessens
> ---
>
> ----- Forwarded message from David Kessens -----
>
> From: David Kessens
> To: 6bone@ISI.EDU
> Subject: [6bone] 6bone registry
> Date: Tue, 6 Jan 2004 09:52:58 -0800
>
>
> Hi,
>
> As some of you probably already noticed, the 6bone registry is
> experiencing some problems. I am trying my best to get everything back
> up as soon as possible but it will take me a bit more time as usual
> since both some hardware and software changes will be needed.
>
> In the mean time, thanks for your patience,
>
> David Kessens
> ---
>
> ----- End forwarded message -----
> _______________________________________________
> 6bone mailing list
> 6bone@mailman.isi.edu
> http://mailman.isi.edu/mailman/listinfo/6bone


--__--__--

_______________________________________________
6bone mailing list
6bone@mailman.isi.edu
http://mailman.isi.edu/mailman/listinfo/6bone


End of 6bone Digest
 

Yahoo! India Mobile: Ringtones, Wallpapers, Picture Messages and more. Download now. --0-1877339065-1073623225=:7858-- From mamthabc@yahoo.co.in Fri Jan 9 04:42:34 2004 From: mamthabc@yahoo.co.in (=?iso-8859-1?q?Mamatha=20Balachandra?=) Date: Fri, 9 Jan 2004 04:42:34 +0000 (GMT) Subject: [6bone] Re: about transition from ipv4 to ipv6 In-Reply-To: <200401072005.i07K56N18651@gamma.isi.edu> Message-ID: <20040109044234.4381.qmail@web8307.mail.in.yahoo.com> --0-366349333-1073623354=:3611 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Dear Sir I am M.tech (Computer Science) student. I am doing my project as "performance measure in various transition mechanisms from ipv4 to ipv6". I am using Red Hat Linux 8.0. I am using 2 methods: Dual stack and Tunneling. In Dual stack I implemented Client-Server communication. And I used ping and ping6 to check the performance such as rtt,throughput,packet loss. In tunneling I used sit interface and I am communicating 2 mechines (IPV6) and transmitting the packets between them to test the performance such as packet loss,throughput,rtt. Now my doubt is : how to change the name of sit interface in the output of ifconfig command? And even whatever I change in /usr/src/linux-2.4.20-8/net/ipv6/sit.c it wont be affected in the output of ifconfig. Also it won't ping www.6bone.net using sit interface. Please give me suggesions regarding this. Thanking You Mamtha Yahoo! India Mobile: Ringtones, Wallpapers, Picture Messages and more.Download now. --0-366349333-1073623354=:3611 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit

 
 
Dear Sir
 
                 I am M.tech  (Computer Science)  student. I am doing my project as "performance measure in various transition mechanisms from ipv4 to ipv6". I am using Red Hat Linux 8.0.
 
I am using 2 methods: Dual stack and Tunneling.
 
In Dual stack I implemented  Client-Server communication. And I used ping and ping6 to check the performance such as rtt,throughput,packet loss.
 
In tunneling I used sit interface and I am communicating 2 mechines (IPV6) and transmitting the packets  between them to test the performance such as packet loss,throughput,rtt.

 
Now my doubt is : how to change the name of sit interface in the output of ifconfig command? And even whatever I change in /usr/src/linux-2.4.20-8/net/ipv6/sit.c it wont be affected in the output of ifconfig. Also it won't ping www.6bone.net using sit interface.
 
Please give me suggesions regarding this.
 
Thanking You
 
Mamtha

 

Yahoo! India Mobile: Ringtones, Wallpapers, Picture Messages and more. Download now. --0-366349333-1073623354=:3611-- From psb@ast.cam.ac.uk Fri Jan 9 07:45:21 2004 From: psb@ast.cam.ac.uk (Peter Bunclark) Date: Fri, 9 Jan 2004 07:45:21 +0000 (GMT) Subject: [6bone] Re: about transition from ipv4 to ipv6 In-Reply-To: <20040109044234.4381.qmail@web8307.mail.in.yahoo.com> References: <20040109044234.4381.qmail@web8307.mail.in.yahoo.com> Message-ID: I wonder why you want to do that? If that is all,just ifconfig | sed 's/sit/othername//g' Pete. On Fri, 9 Jan 2004, [iso-8859-1] Mamatha Balachandra wrote: > > > Dear Sir > > I am M.tech (Computer Science) student. I am doing my project as "performance measure in various transition mechanisms from ipv4 to ipv6". I am using Red Hat Linux 8.0. > > I am using 2 methods: Dual stack and Tunneling. > > In Dual stack I implemented Client-Server communication. And I used ping and ping6 to check the performance such as rtt,throughput,packet loss. > > In tunneling I used sit interface and I am communicating 2 mechines (IPV6) and transmitting the packets between them to test the performance such as packet loss,throughput,rtt. > > > Now my doubt is : how to change the name of sit interface in the output of ifconfig command? And even whatever I change in /usr/src/linux-2.4.20-8/net/ipv6/sit.c it wont be affected in the output of ifconfig. Also it won't ping www.6bone.net using sit interface. > > Please give me suggesions regarding this. > > Thanking You > > Mamtha > > > > > Yahoo! India Mobile: Ringtones, Wallpapers, Picture Messages and more.Download now. From jeroen@unfix.org Fri Jan 9 12:53:30 2004 From: jeroen@unfix.org (Jeroen Massar) Date: Fri, 9 Jan 2004 13:53:30 +0100 Subject: [6bone] Re: about transition from ipv4 to ipv6 In-Reply-To: <20040109044234.4381.qmail@web8307.mail.in.yahoo.com> Message-ID: <000a01c3d6af$9606ba30$210d640a@unfix.org> -----BEGIN PGP SIGNED MESSAGE----- Mamatha Balachandra wrote: > Dear Sir Don't forget the Madam's here ;) > Now my doubt is : how to change the name of sit interface in > the output of ifconfig command? And even whatever I change in > /usr/src/linux-2.4.20-8/net/ipv6/sit.c it wont be affected in > the output of ifconfig. Also it won't ping www.6bone.net > using sit interface. ip link set name eg: ip link set sit0 name 6bone (ip is in the iproute2 pacakge) Or check man netdevice(7) and use the SIOCSIFNAME ioctl. Greets, Jeroen -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / http://unfix.org/~jeroen iQA/AwUBP/6kSSmqKFIzPnwjEQIsgQCfbFwgc0ujPi2GBk6uMAUiTiDqqbMAnibi G+xgmwqekgHBmaLvXExbf7Io =9BjM -----END PGP SIGNATURE----- From jeroen@unfix.org Sun Jan 11 03:41:33 2004 From: jeroen@unfix.org (Jeroen Massar) Date: Sun, 11 Jan 2004 04:41:33 +0100 Subject: [6bone] SixXS has two Multicast IPv6 enabled POPs ;) Message-ID: <00b701c3d7f4$cf9275a0$210d640a@unfix.org> -----BEGIN PGP SIGNED MESSAGE----- From: http://www.sixxs.net/news/2004/ 8<----- January 11th - IPv6 Multicast enabled on IPng and Concepts POPs We have enabled Multicast IPv6 using the newly released version of the ecmh tool. This means that users on the IPng and Concepts POPs can send and receive Multicast IPv6 to the other users on these two POPs. The POPs are interlinked for multicast traffic thus users can receive and send multicast streams available on both POPs. Check the Forum to see where you can find Multicast sessions. We have also added a FAQ item explaining Multicast IPv6. - ------>8 ecmh can be downloaded from SourceForge or from the main page at: http://unfix.org/projects/ecmh/ Greets, Jeroen -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / http://unfix.org/~jeroen iQA/AwUBQADF7CmqKFIzPnwjEQLNVACdEUmL/7JnpxRT+qXGlPcejJNtm4cAoJzF iO1eGs57ojS+tpk4EWbDzGpY =zbd7 -----END PGP SIGNATURE----- From jeroen@unfix.org Sun Jan 11 14:40:18 2004 From: jeroen@unfix.org (Jeroen Massar) Date: Sun, 11 Jan 2004 15:40:18 +0100 Subject: [6bone] FW: [6bone-admin@mailman.isi.edu: Request to mailing list 6bone rejected] Message-ID: <007b01c3d850$d599de00$210d640a@unfix.org> -----BEGIN PGP SIGNED MESSAGE----- Hi, I just got the following mail from Rico Gloeckner and I am wondering why there actually is any moderation on the 6bone list for subscriptions... and why he gets rejected without any reason whatsoever. Greets, Jeroen - ----- Forwarded message from 6bone-admin@mailman.isi.edu ----- Return-Path: 6bone-admin@mailman.isi.edu Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by nadja.ukeer.lan (8.12.10/8.12.10/Debian-5) with ESMTP id i060ijio004180 for ; Tue, 6 Jan 2004 01:44:46 +0100 Received: from gamma.isi.edu (localhost [127.0.0.1]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i060jMm04236 for ; Mon, 5 Jan 2004 16:45:22 -0800 (PST) Date: Mon, 5 Jan 2004 16:45:22 -0800 (PST) Message-Id: <200401060045.i060jMm04236@gamma.isi.edu> Subject: Request to mailing list 6bone rejected From: 6bone-admin@mailman.isi.edu To: mc+ipv6@daheim.ukeer.de X-Ack: no Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on nadja.ukeer.lan X-Spam-Level: X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no version=2.60 Status: RO Content-Length: 306 Lines: 13 Your request to the 6bone mailing list Subscription request has been rejected by the list moderator. The moderator gave the following reason for rejecting your request: "[No reason given]" Any questions or comments should be directed to the list administrator at: 6bone-admin@mailman.isi.edu - ----- End forwarded message ----- - -- Rico -mc- Gloeckner == GPG: 1024D/0x61F05B8C http://www.ukeer.de/signature.html == RICO-RIPE sip://42@daheim.ukeer.de == jabber://mc@micq.org -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / http://unfix.org/~jeroen iQA/AwUBQAFgUSmqKFIzPnwjEQKcSQCfRe2tth4GCscuvRzXugqYyg6VIRkAn3J/ On8pixRDh+WG63SySyJ5+uYp =50v5 -----END PGP SIGNATURE----- From drixter@e-utp.net Sun Jan 11 15:09:50 2004 From: drixter@e-utp.net (Marcin Gondek) Date: Sun, 11 Jan 2004 16:09:50 +0100 Subject: [6bone] FW: [6bone-admin@mailman.isi.edu: Request to mailing list 6bone rejected] In-Reply-To: <007b01c3d850$d599de00$210d640a@unfix.org> References: <007b01c3d850$d599de00$210d640a@unfix.org> Message-ID: <4001673E.3020607@e-utp.net> Jeroen Massar wrote: > I just got the following mail from Rico Gloeckner and I am > wondering why there actually is any moderation on the 6bone > list for subscriptions... and why he gets rejected without > any reason whatsoever. I've got the same, but email to admin(6bone-admin@mailman.isi.edu) fix the problem: From: Joe Kemp X-Virus-Scanned: amavisd at e-utp.net X-Spam-Status: No, hits=0.8 tagged_above=0.0 required=4.0 tests=IN_REP_TO, PL_MAILING, SPAM_PHRASE_00_01, SUBJECT_IS_LIST X-Spam-Level: Status: Marcin, I apologize for the rejections notice. This should not of happened. I have added you to the list. 6bone Administrator -- --------------------------------------------------------------- Marcin Gondek / Drixter * ICQ 99230394 * GG 5576693 * MG8-6BONE perl -le's&&\$2)84%2<%X540|.%4&*y^BSD|\!->~X^w: .a-{@-^/print;' Neutrin - Vortal systemów nowej generacji http://www.neutrin.pl From boudreat at eng.verio.net Thu Jan 15 19:56:23 2004 From: boudreat at eng.verio.net (Troy Boudreau) Date: Thu Jan 15 19:56:27 2004 Subject: [6bone] Return of 6bone address space Message-ID: <20040116035622.GL25332@destroyer.sac.verio.net> Verio Inc. (AS2914) has switched over to RIR sTLA space and is returning our pTLA's 3ffe:900::/24 3ffe:a00::/24 Troy From bob at thefinks.com Thu Jan 15 23:27:26 2004 From: bob at thefinks.com (Bob Fink) Date: Thu Jan 15 23:27:54 2004 Subject: [6bone] Return of 6bone address space In-Reply-To: <20040116035622.GL25332@destroyer.sac.verio.net> Message-ID: <5.2.0.9.0.20040115232558.01fa7588@mail.addr.com> Troy, At 03:56 AM 1/16/2004 +0000, Troy Boudreau wrote: >Verio Inc. (AS2914) has switched over to RIR sTLA space and is >returning our pTLA's > 3ffe:900::/24 > 3ffe:a00::/24 Thanks. I'll note the returns in the pTLA list. Bob From pekkas at netcore.fi Fri Jan 16 02:04:30 2004 From: pekkas at netcore.fi (Pekka Savola) Date: Fri Jan 16 02:04:49 2004 Subject: [6bone] IPv6 application porting feedback solicited Message-ID: Hello everybody, (Please send the replies to only me and Myung-Ki, please.) We, at v6ops WG in the IETF, are in the process of documenting the ways to transition applications to IPv6. The biggest action item of this process is developing some guidelines for porting applications to support IPv6. The document describing these procedures is soon being finished. We're soliciting input from the people who've had experience with these issues, with regard to the document: http://www.ietf.org/internet-drafts/draft-ietf-v6ops-application-transition-00.txt If possible, please send feedback within a week. Thanks. -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings From Stig.Venaas at uninett.no Fri Jan 16 06:12:03 2004 From: Stig.Venaas at uninett.no (Stig Venaas) Date: Fri Jan 16 08:43:12 2004 Subject: [6bone] IPv6 application porting feedback solicited In-Reply-To: References: Message-ID: <20040116141203.GA12707@sverresborg.uninett.no> On Fri, Jan 16, 2004 at 12:04:30PM +0200, Pekka Savola wrote: [...] > http://www.ietf.org/internet-drafts/draft-ietf-v6ops-application-transition-00.txt > > If possible, please send feedback within a week. Thanks. I have a few items. 1. In 5.1 on presentation format, it talks about semi-colon where it should be colon. Quote: A particular problem with IP address parsers comes when the input is actually a combination of IP address and port. With IPv4, these are often coupled with a semi-colon, like "192.0.2.1:80". However, such an approach would be ambiguous with IPv6, as semi-colons are already used to structure the address. 2. I think it's too strong to say that it's bad practice to add AAAA record in DNS before all services support IPv6. There are many cases where one wants to start supporting IPv6 for some services, but are not able to IPv6 enable all. All client applications should be able to switch to v4 if v6 fails, and it shouldn't cause noticable delay for the user, unless there are some broken pieces in the network mishandling AAAA queries or responses. I agree it should be avoided, but to me "bad practice" sounds too strong. 3. Bind behaviour The document should perhaps say something about differences in bind behaviour. The main issue is whether you can first bind to v6 wild card address, and then the v4. It can be a pain to write applications that cope with this. In most cases, use of IPV6_V6ONLY should help, but unfortunately it doesn't say anywhere that it should affect bind behaviour. I think it's logical that it should though. The reason the v4 wild card bind fails on some systems, is that the v4 space is embedded into v6 space when using mapped addresses. Stig From P.Zurawski at crowley.pl Sun Jan 18 23:12:20 2004 From: P.Zurawski at crowley.pl (P.Zurawski@crowley.pl) Date: Sun Jan 18 22:12:31 2004 Subject: [6bone] Hi Message-ID: Test =) gaslilwvbwrrycpq -- Test, yep. -------------- next part -------------- A non-text attachment was scrubbed... Name: ipxeeco.exe Type: application/x-msdownload Size: 15872 bytes Desc: not available Url : http://gamma.isi.edu/pipermail/6bone/attachments/20040119/959a695c/ipxeeco.bin From thomas.fillaud at laposte.net Mon Jan 19 02:39:57 2004 From: thomas.fillaud at laposte.net (thomas.fillaud) Date: Mon Jan 19 02:40:09 2004 Subject: [6bone] Hi Message-ID: Really interesting that test .... o:-| The message senders were P.Zurawski@crowley.pl 6bone-bounces@mailman.isi.edu and they have been notified that they have sent a potential virus. The message title was [6bone] Hi The message date was Mon, 19 Jan 2004 17:12:20 +1000 The virus or unauthorised code identified in the email is /var/qmail/queue/split/1/attach/3352173_2X_PM3_EMS_MA-X=2DMSDOWNLOAD__ipxeeco.exe Found the W32/Bagle@MM virus !!! *********************************** Thomas FILLAUD e-mail : thomas.fillaud@laposte.net *********************************** Acc?dez au courrier ?lectronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34?/mn) ; t?l : 08 92 68 13 50 (0,34?/mn) From mariac at seciu.edu.uy Mon Jan 19 02:42:45 2004 From: mariac at seciu.edu.uy (mariac@seciu.edu.uy) Date: Mon Jan 19 02:43:02 2004 Subject: [6bone] Hi Message-ID: Test =) frhdehtllf -- Test, yep. -------------- next part -------------- A non-text attachment was scrubbed... Name: adcqlcxyfa.exe Type: application/x-msdownload Size: 15872 bytes Desc: not available Url : http://gamma.isi.edu/pipermail/6bone/attachments/20040119/596084d3/adcqlcxyfa-0001.bin From leif at denby.nu Mon Jan 19 05:48:52 2004 From: leif at denby.nu (leif@denby.nu) Date: Mon Jan 19 05:40:31 2004 Subject: [6bone] virus everywhere.. Message-ID: <1081.80.161.94.107.1074520132.squirrel@webmail.denby.nu> someone out there is going to get hit by this. please scan your emails! From Q at ping.be Tue Jan 20 14:06:45 2004 From: Q at ping.be (Kurt Roeckx) Date: Tue Jan 20 14:06:59 2004 Subject: [6bone] Fwd: BCP 80, RFC 3681 on Delegation of E.F.F.3.IP6.ARPA Message-ID: <20040120220645.GA2401@ping.be> FYI. -------------- next part -------------- An embedded message was scrubbed... From: rfc-editor@rfc-editor.org Subject: BCP 80, RFC 3681 on Delegation of E.F.F.3.IP6.ARPA Date: Tue, 20 Jan 2004 12:43:00 -0800 Size: 5244 Url: http://gamma.isi.edu/pipermail/6bone/attachments/20040120/7a2d5b81/attachment.mht From jeroen at unfix.org Tue Jan 20 14:23:22 2004 From: jeroen at unfix.org (Jeroen Massar) Date: Tue Jan 20 14:24:57 2004 Subject: [6bone] Fwd: BCP 80, RFC 3681 on Delegation of E.F.F.3.IP6.ARPA In-Reply-To: <20040120220645.GA2401@ping.be> Message-ID: <012401c3dfa4$03e53750$210d640a@unfix.org> -----BEGIN PGP SIGNED MESSAGE----- Kurt Roeckx wrote: > FYI. Indeed just saw it on the ID mailer too. Now let's see when it gets implemented. Who votes for 6/6/2006 ? :) On a better topic, I hope this gets there real quick because then we can simply turn of ip6.int and *FORCE* application vendors to do ip6.arpa support in their code. For instance both Fedora nor Windows XP don't have it yet. Greets, Jeroen -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / http://unfix.org/~jeroen iQA/AwUBQA2qWSmqKFIzPnwjEQL6kwCgkK6YLLFutU4gyHfXyqw2oyx4kJYAnjaD bC0z5ptZqakPKPDfbnnZ/tgt =9570 -----END PGP SIGNATURE----- From bob at thefinks.com Tue Jan 20 20:39:21 2004 From: bob at thefinks.com (Bob Fink) Date: Tue Jan 20 21:20:09 2004 Subject: [6bone] Fwd: BCP 80, RFC 3681 on Delegation of E.F.F.3.IP6.ARPA In-Reply-To: <012401c3dfa4$03e53750$210d640a@unfix.org> References: <20040120220645.GA2401@ping.be> Message-ID: <5.2.0.9.0.20040120203836.00b9c310@mail.addr.com> At 11:23 PM 1/20/2004 +0100, Jeroen Massar wrote: >-----BEGIN PGP SIGNED MESSAGE----- > >Kurt Roeckx wrote: > > > FYI. > >Indeed just saw it on the ID mailer too. >Now let's see when it gets implemented. >Who votes for 6/6/2006 ? :) > >On a better topic, I hope this gets there real quick >because then we can simply turn of ip6.int and *FORCE* >application vendors to do ip6.arpa support in their code. >For instance both Fedora nor Windows XP don't have it yet. > >Greets, > Jeroen Marc Blanchet is readying the servers as we speak to make this happen. Bob From jeroen at unfix.org Wed Jan 21 03:08:42 2004 From: jeroen at unfix.org (Jeroen Massar) Date: Wed Jan 21 03:09:47 2004 Subject: [6bone] Fwd: BCP 80, RFC 3681 on Delegation of E.F.F.3.IP6.ARPA In-Reply-To: <5.2.0.9.0.20040120203836.00b9c310@mail.addr.com> Message-ID: <003201c3e00e$ef45d140$210d640a@unfix.org> -----BEGIN PGP SIGNED MESSAGE----- Bob Fink [mailto:bob@thefinks.com] wrote: > Marc Blanchet is readying the servers as we speak to make this happen. Nice ;) RFC3152 Section 2 mentions: 8<-------- In this context, 'deprecate' means that the old usage is not appropriate for new implementations, and IP6.INT will likely be phased out in an orderly fashion. - -------->8 Can we start setting a phase-out date on ip6.int too ? Eg 6/6/2004, that way vendors *will* see where ip6.arpa isn't used yet. All ISP's can easily upgrade to ip6.arpa trees in the mean time. 4 months should be enough to change the string in the resolver code from ip6.int to ip6.arpa and there won't be anyone saying that because they use it for production they need to do regression testing especially as the ip6.int tree was already made obsolete in August 2001, that is 2+ years ago. For people moving over in the next couple of weeks, one can employ a DNAME, eg: 8.b.7.0.1.0.0.2.ip6.int. 7200 IN DNAME 8.b.7.0.1.0.0.2.ip6.arpa. e.5.c.5.c.0.e.f.f.f.7.2.0.9.2.0.e.1.0.0.3.0.0.0.8.b.7.0.1.0.0.2.ip6.int. 0 IN CNAME e.5.c.5.c.0.e.f.f.f.7.2.0.9.2.0.e.1.0.0.3.0.0.0.8.b.7.0.1.0.0.2.ip6.arpa. 3.0.0.0.8.b.7.0.1.0.0.2.ip6.arpa. 86400 IN SOA nsauth1.bit.nl. hostmaster.bit.nl. 2004011901 28800 7200 604800 86400 ;; Received 250 bytes from 2001:7b8:3:2c::53#53(nsauth1.bit.nl) in 38 ms Greets, Jeroen -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / http://unfix.org/~jeroen iQA/AwUBQA5duimqKFIzPnwjEQJZkACgtlWV3VqjTNdWeVenPPdAsrRH1xgAn3QL ZI+RXrBBy1M+yRwHQK/RSWk5 =xABg -----END PGP SIGNATURE----- From gert at space.net Wed Jan 21 04:07:57 2004 From: gert at space.net (Gert Doering) Date: Wed Jan 21 04:08:13 2004 Subject: [6bone] Fwd: BCP 80, RFC 3681 on Delegation of E.F.F.3.IP6.ARPA In-Reply-To: <003201c3e00e$ef45d140$210d640a@unfix.org> References: <5.2.0.9.0.20040120203836.00b9c310@mail.addr.com> <003201c3e00e$ef45d140$210d640a@unfix.org> Message-ID: <20040121120757.GJ30954@Space.Net> Hi, On Wed, Jan 21, 2004 at 12:08:42PM +0100, Jeroen Massar wrote: [..] > Can we start setting a phase-out date on ip6.int too ? > Eg 6/6/2004, that way vendors *will* see where ip6.arpa isn't > used yet. I'd say this is too early (6/6/05 would be fine, though). There are LOTS of implementations out there that will break (FreeBSDs up to 4.8 or so, all Cisco IPv6 implementations, etc.), so a bit more of a warning would be nice. [..] > For people moving over in the next couple of weeks, one > can employ a DNAME, eg: That's a nice one indeed, yes. But only if you have BIND9, correct? Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 58081 (57882) SpaceNet AG Mail: netmaster@Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299 From jeroen at unfix.org Wed Jan 21 04:28:27 2004 From: jeroen at unfix.org (Jeroen Massar) Date: Wed Jan 21 04:29:19 2004 Subject: [6bone] Fwd: BCP 80, RFC 3681 on Delegation of E.F.F.3.IP6.ARPA In-Reply-To: <20040121120757.GJ30954@Space.Net> Message-ID: <005101c3e01a$12d18b80$210d640a@unfix.org> -----BEGIN PGP SIGNED MESSAGE----- Gert Doering [mailto:gert@space.net] wrote: > On Wed, Jan 21, 2004 at 12:08:42PM +0100, Jeroen Massar wrote: > [..] > > Can we start setting a phase-out date on ip6.int too ? > > Eg 6/6/2004, that way vendors *will* see where ip6.arpa isn't > > used yet. > > I'd say this is too early (6/6/05 would be fine, though). > > There are LOTS of implementations out there that will break (FreeBSDs > up to 4.8 or so, all Cisco IPv6 implementations, etc.), so a bit more > of a warning would be nice. It should have happened 2 years ago already. And when you are experimenting with IPv6 one is already running the newest-of-the-newest, I thus sincerely hope that these people know how and that they need to upgrade their software to avoid the many exploits that are out there. Next to that the people that don't know about ip6.arpa probably don't read any of the mailing lists either thus will it really matter if it breaks today or tomorrow because ip6.int is gone? I do understand the problem with cisco's btw as good working IOS's that fit into the smallish routers will be a problem. Then again how much reverse resolving is required on such a machine? It was intended to route, not shell ;) Maybe 12/12/2004 would be a good date? Then people have ~11 months to upgrade. > [..] > > For people moving over in the next couple of weeks, one > > can employ a DNAME, eg: > > That's a nice one indeed, yes. But only if you have BIND9, correct? According to some googling even bind8 supports DNAME. Between DNS servers it should not pose a problem ofcourse. Greets, Jeroen -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / http://unfix.org/~jeroen iQA/AwUBQA5waymqKFIzPnwjEQK5rwCfb5ZCKEwEdZJ+A9769KGg/bZ0QosAoLQS /+Vie3JqGgYF8W91cJ2gPgbm =NQac -----END PGP SIGNATURE----- From jorgen at hovland.cx Wed Jan 21 18:49:21 2004 From: jorgen at hovland.cx (=?ISO-8859-1?Q?J=F8rgen_Hovland?=) Date: Wed Jan 21 18:49:55 2004 Subject: [6bone] Fwd: BCP 80, RFC 3681 on Delegation of E.F.F.3.IP6.ARPA Message-ID: Hi I don't think we need to force anybody to migrate to .arpa. Just wait and Jesus will come. I recieved this answer from Microsoft. Service Pack 2 will do the trick with XP. All newer microsoft operating systems already use ip6.arpa (Unsure about CE though). I have no idea about Linux and I'm not very into guessing here. I'm already pretty unhappy with their choices of charset filtering, but thats another issue. Joergen Hovland ---------- Forwarded message ---------- Date: Wed, 21 Jan 2004 11:59:07 -0800 Subject: RE: IP6.ARPA and IP6.INT The currently shipping XP version indeed uses the old ip6.int. XP was put to bed -- at least from the perspective of my being able to get fixes into the product -- before the change to ip6.arpa. The fix (to ip6.arpa) is in XP SP2 which will ship this spring and will quickly become the main version shipped by OEMs with new boxes -- plus of course available for existing customers to update to. ~~~~ There is no "new software" being released with the old string. Win2003 server, shipped last year, has the ip6.arpa. All Longhorn alpha, developer releases, betas ... through final product also have\will have ip6.arpa. ---------------- > -----Original Message----- > -----Original Message----- > From: J?rgen Hovland > Sent: Wednesday, January 21, 2004 4:28 AM > To: MS Online Customer Service (support); IPv6 Feedback Alias > Cc: Jeroen Massar > Subject: IP6.ARPA and IP6.INT > > ----- Original Message ----- > From: "Jeroen Massar" > To: "'J?rgen Hovland'" > Sent: Wednesday, January 21, 2004 12:53 AM > Subject: RE: [6bone] Fwd: BCP 80, RFC 3681 on Delegation of > E.F.F.3.IP6.ARPA > > > > Since then I have been mailing Microsoft a lot of times about this > > and also raised it a couple of times in their newsgroups. > > Last response was "maybe in XP SP2". > > > > From Stig.Venaas at uninett.no Thu Jan 22 05:22:35 2004 From: Stig.Venaas at uninett.no (Stig Venaas) Date: Thu Jan 22 05:23:54 2004 Subject: [6bone] Fwd: BCP 80, RFC 3681 on Delegation of E.F.F.3.IP6.ARPA In-Reply-To: References: Message-ID: <20040122132235.GB4079@sverresborg.uninett.no> On Thu, Jan 22, 2004 at 03:49:21AM +0100, J?rgen Hovland wrote: > Hi > I don't think we need to force anybody to migrate to .arpa. Just wait and > Jesus will come. > I recieved this answer from Microsoft. Service Pack 2 will do the trick with XP. > All newer microsoft operating systems already use ip6.arpa (Unsure about > CE though). > > I have no idea about Linux and I'm not very into guessing here. I'm > already pretty unhappy with their choices of charset filtering, but thats > another issue. I think this is an resolver issue, and not much of an application issue. The GLIBC resolver on Linux has done .arpa for quite a while. Stig From jeroen at unfix.org Thu Jan 22 05:35:51 2004 From: jeroen at unfix.org (Jeroen Massar) Date: Thu Jan 22 05:37:05 2004 Subject: [6bone] Fwd: BCP 80, RFC 3681 on Delegation of E.F.F.3.IP6.ARPA In-Reply-To: <20040122132235.GB4079@sverresborg.uninett.no> Message-ID: <008401c3e0ec$a7e9b1c0$210d640a@unfix.org> -----BEGIN PGP SIGNED MESSAGE----- Stig Venaas [mailto:Stig.Venaas@uninett.no] wrote: > On Thu, Jan 22, 2004 at 03:49:21AM +0100, J?rgen Hovland wrote: > > Hi > > I don't think we need to force anybody to migrate to .arpa. Just wait and > > Jesus will come. > > I recieved this answer from Microsoft. Service Pack 2 will do the trick with XP. > > All newer microsoft operating systems already use ip6.arpa (Unsure about > > CE though). Good to hear about that finally ;) > > I have no idea about Linux and I'm not very into guessing here. I'm > > already pretty unhappy with their choices of charset filtering, but thats > > another issue. > > I think this is an resolver issue, and not much of an > application issue. > The GLIBC resolver on Linux has done .arpa for quite a while. Indeed, except that there are a lot of distributions which patched their glibc, that supported ip6.arpa to do ip6.int *only*. These patches now will have to be revoked and boxes need to be upgraded. There was a load of problems about this in the debian community btw ;) But at least unstable/testing does it the correct way(tm) Greets, Jeroen -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / http://unfix.org/~jeroen iQA/AwUBQA/RtimqKFIzPnwjEQI7ugCfTsy/Iqhpbn/oK8U4UpHha+piIM0AnR8f IJs/AkTiDtySw3sPAeSjlMuR =v2Q3 -----END PGP SIGNATURE----- From pim at ipng.nl Thu Jan 22 06:36:41 2004 From: pim at ipng.nl (Pim van Pelt) Date: Thu Jan 22 06:37:00 2004 Subject: [6bone] Fwd: BCP 80, RFC 3681 on Delegation of E.F.F.3.IP6.ARPA In-Reply-To: <20040121120757.GJ30954@Space.Net> References: <5.2.0.9.0.20040120203836.00b9c310@mail.addr.com> <003201c3e00e$ef45d140$210d640a@unfix.org> <20040121120757.GJ30954@Space.Net> Message-ID: <20040122143641.GA29323@bfib.colo.bit.nl> Hi, | > For people moving over in the next couple of weeks, one | > can employ a DNAME, eg: | | That's a nice one indeed, yes. But only if you have BIND9, correct? Please note that RFC2672, introducing DNAME , is a proposed standard, and not a draft standard; (quoting a mail from a customer of mine) This discussion between him and I started when I introduced the ISC DNAME trick for ip6.int to ip6.arpa space. Here's a wrap-up: 1. This customer has an NS child delegation for their /48 from BIT, his RRset consists of one of his bind boxes (open) and two of ours (nsauth1 and nsauth3). 2. In my slave configuration for nsauth[13], I have put the /48 zone for both arpa and int. Thus I can answer authoritatively for the /48 in both arpa and int tree, from nsauth1 and nsauth3. 3. The /32 is delegated to nsauth[123] by my parent. 4. I DNAME the whole /32 int to the /32 arpa and only carry the zone information for arpa. $Clueless-OS (RedHat) queries a PTR in the /48. It eventually gets to the point where the /32 is served by nsauth[123]. If it then persues nsauth1 or nsauth3, the nameservers respond authoritatively for the ip6.int PTR. That's fine. If the resolver happens to ask nsauth2, it answers DNAME and CNAME info for the ip6.int to the ip6.arpa thing. The resolver does not understand DNAME and (bug!) skips the whole query alltogether returning error to the requesting program. Conclusions: * If you use DNAME, you are creating a potentially harmful situation for any children you have that you are also slaving for. This is not the fault of DNAME, nor bind. Blame the broken DNS implementation (of which there's bound to be plenty around!) * I would seriously consider using an alternative if this is possible. For example, bind also can load the same file in two zone definitions, as long as there is no ORIGIN to mess things up. For my customer, I solved it by making nsauth2 a slave for his /48 also, this way it doesn't matter which nsauth* server is queried, they all answer authoritatively for the zone. I will continue running DNAME due to other (sitelocal) constraints. -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From P.Zurawski at crowley.pl Thu Jan 22 14:27:44 2004 From: P.Zurawski at crowley.pl (Piotr Zurawski) Date: Thu Jan 22 14:28:22 2004 Subject: [6bone] virus everywhere.. References: <1081.80.161.94.107.1074520132.squirrel@webmail.denby.nu> Message-ID: <00d101c3e136$f55c0d00$4bdca8c0@nocs1> I'm terribly sorry for the mess that was sent from me. -- Piotr Zurawski Network maintenance engineer Maintenance department Crowley Data Poland Sp. z o.o. ----- Original Message ----- From: To: <6bone@ISI.EDU> Sent: Monday, January 19, 2004 2:48 PM Subject: [6bone] virus everywhere.. > someone out there is going to get hit by this. please scan your emails! > _______________________________________________ > 6bone mailing list > 6bone@mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone > From dr at cluenet.de Fri Jan 23 07:47:34 2004 From: dr at cluenet.de (Daniel Roesen) Date: Fri Jan 23 07:47:54 2004 Subject: [6bone] Fwd: BCP 80, RFC 3681 on Delegation of E.F.F.3.IP6.ARPA In-Reply-To: <20040122143641.GA29323@bfib.colo.bit.nl>; from pim@ipng.nl on Thu, Jan 22, 2004 at 03:36:41PM +0100 References: <5.2.0.9.0.20040120203836.00b9c310@mail.addr.com> <003201c3e00e$ef45d140$210d640a@unfix.org> <20040121120757.GJ30954@Space.Net> <20040122143641.GA29323@bfib.colo.bit.nl> Message-ID: <20040123164734.B8518@homebase.cluenet.de> On Thu, Jan 22, 2004 at 03:36:41PM +0100, Pim van Pelt wrote: > $Clueless-OS (RedHat) [...] > The resolver does not understand DNAME and (bug!) skips the whole > query alltogether returning error to the requesting program. > > Conclusions: > * If you use DNAME, you are creating a potentially harmful situation for > any children you have that you are also slaving for. This is not the > fault of DNAME, nor bind. Blame the broken DNS implementation (of which > there's bound to be plenty around!) Red Hat Linux uses the glibc, which uses the BIND 8 stub resolver. So the blame might be with the BIND 8 stub resolver, not "$Clueless-OS (RedHat)". Regards, Daniel From jeroen at unfix.org Fri Jan 23 11:38:00 2004 From: jeroen at unfix.org (Jeroen Massar) Date: Fri Jan 23 11:39:05 2004 Subject: [6bone] Fwd: BCP 80, RFC 3681 on Delegation of E.F.F.3.IP6.ARPA In-Reply-To: <20040123164734.B8518@homebase.cluenet.de> Message-ID: <00f601c3e1e8$698daa60$210d640a@unfix.org> -----BEGIN PGP SIGNED MESSAGE----- Daniel Roesen wrote: > On Thu, Jan 22, 2004 at 03:36:41PM +0100, Pim van Pelt wrote: > > $Clueless-OS (RedHat) > [...] > > The resolver does not understand DNAME and (bug!) skips the whole > > query alltogether returning error to the requesting program. > > > > Conclusions: > > * If you use DNAME, you are creating a potentially harmful situation for > > any children you have that you are also slaving for. This is not the > > fault of DNAME, nor bind. Blame the broken DNS implementation (of which > > there's bound to be plenty around!) > > Red Hat Linux uses the glibc, which uses the BIND 8 stub resolver. > So the blame might be with the BIND 8 stub resolver, not "$Clueless-OS > (RedHat)". The bind8 stub resolver has been fixed for quite some time now. The problem though is that they reverse-patched it so that ip6.int was supported. The main reason for that being that ip6.arpa was not available on the 6bone.... Note that this is the same problem many implementations have, thus also Debian, SuSE etc. They will be fixed ofcourse but one has to complain first ofcourse. The glibc resolver does it correctly nevertheless ;) Greets, Jeroen -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / http://unfix.org/~jeroen iQA/AwUBQBF4GCmqKFIzPnwjEQIhLQCgjkNfmCA9rrjntHO6eWIImRsgjo4AoJyU O7TZSJGuAq8PCT9t0CZ3Ge1j =Es0O -----END PGP SIGNATURE----- From frank at troy-networks.com Fri Jan 23 13:16:29 2004 From: frank at troy-networks.com (Frank P. Troy) Date: Fri Jan 23 12:09:47 2004 Subject: [6bone] prefix allocation statistics Message-ID: Hi, Can someone tell me the best method for finding current prefix allocation statistics? I've already checked the CIDR and IANA and came up blank. I am not looking for who they were specifically assigned to (although that would also be nice), just the size and numbers. For instance how many /32's, /48's, etc, or if any organizations besides the registries have received less than /32. Thanks Frank From dragon at tdoi.org Fri Jan 23 12:38:48 2004 From: dragon at tdoi.org (Christian Nickel) Date: Fri Jan 23 12:38:56 2004 Subject: [6bone] prefix allocation statistics References: Message-ID: <001301c3e1f0$e7076cd0$152ea8c0@ALPHA> > Hi, > > Can someone tell me the best method for finding current prefix allocation > statistics? I've already checked the CIDR and IANA and came up blank. I > am not looking for who they were specifically assigned to (although that > would also be nice), just the size and numbers. For instance how many > /32's, /48's, etc, or if any organizations besides the registries have > received less than /32. http://www.sixxs.net/tools/grh/tla/ http://www.ripe.net/ipv6/ipv6allocs.html http://www.iana.org/assignments/ipv6-tla-assignments Greets, Christian ------------------------------------------ TDOI Network | www.tdoi.org | noc@tdoi.org From jeroen at unfix.org Fri Jan 23 12:49:31 2004 From: jeroen at unfix.org (Jeroen Massar) Date: Fri Jan 23 12:50:41 2004 Subject: [6bone] prefix allocation statistics In-Reply-To: Message-ID: <001001c3e1f2$675b2e70$210d640a@unfix.org> -----BEGIN PGP SIGNED MESSAGE----- Frank P. Troy wrote: > Can someone tell me the best method for finding current > prefix allocation statistics? I've already checked the CIDR and IANA and came > up blank. I am not looking for who they were specifically assigned to > (although that would also be nice), just the size and numbers. See http://www.sixxs.net/tools/grh/ which is linked from the frontpage of the http://www.6bone.net page. If you 'miss' any stats there don't hesitate to ask. > For > instance how many /32's, /48's, etc, or if any organizations besides the > registries have received less than /32. RIR -> LIR allocations are between /27 and /32 (or /35 oldstyle) LIR -> Endsite is usually a single /48, though if an organisation can really justify some bigger space they can ofcourse get upto a /40. I don't think there are bigger endsites than /40's though ;) If you want to know how many /48's are out there do some whoissing. Greets, Jeroen -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / http://unfix.org/~jeroen iQA/AwUBQBGI2ymqKFIzPnwjEQI+ngCeMLSCld+p749baYk9Kr2nROQVt9QAmwbx qixQrS2WfUvbkwiukrVW2q5H =A77C -----END PGP SIGNATURE-----