North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: IPv6 vs IPv4 (Re: Sprint NOC? Are you awake now?)

  • From: Jeroen Massar
  • Date: Tue Sep 02 19:02:14 2003

-----BEGIN PGP SIGNED MESSAGE-----

Jared Mauch wrote:

> (btw, for those of you who think that IPv6 isn't in use, you may now
> safely ignore this thread).

Then I will safely respond to it in that case ;)

> On Tue, Sep 02, 2003 at 04:34:18PM -0400, Nenad Pudar wrote:
> > My enviroment is far to be broken my friend.
> > This is not question about me or my environoment this question about 
> > your site ,I can always mange to get such a sites if I want but I am not 
> > sure that some other people are even awre what the problem is.
> > I think that still majority of ipv6 connections is through 6 bone and 
> > there you do have a latency and
> > evrybody using the same dns for ipv4 and ipv6 should re-think it over

I think you should rather paste some traceroutes or use GRH
to find out where the problem is. Check http://www.sixxs.net/tools/grh/
for some nice diagnostic tools.

And you might want to read Minimal IPv6 Peering by Robert Kie�ling:
http://ip6.de.easynet.net/ipv6-minimum-peering.txt

> 	i would say that I serve a moderate number of web pages
> a day off my web server.  (warning, big!)  here are some
> statistics: http://puck.nether.net/stats.html
> 
> 	this is the first complaint i've received of accessing
> puck via ipv6 (aside from when i was running a buggy kernel that would
> cause it to stop responding to the v6 address periodically).

<SNIP>

And it works fine here behind 6bone and RIPE space.
(Oh and yes this mail should reach puck over IPv6 :)

I do have to note that there is quite a big amount of latency at least from Intouch:
2001:418::/32   2001:6e0::2     8954 33 2914

 7  2001:418:3f4:0:2a0:24ff:fe83:53d8 (2001:418:3f4:0:2a0:24ff:fe83:53d8)  327.307 ms  308.8 ms  308.631 ms

BIT on the other hand as a direct link to Verio...

2001:418::/32 > 2001:7b8::290:6900:1cc6:d800     12859 2914  

 6  2001:418:3f4:0:2a0:24ff:fe83:53d8  146.572 ms  298.737 ms  146.726 ms
13  puck.nether.net (204.42.254.5)  144.612 ms  146.984 ms  129.067 ms

Almost the same latency :)

> 	Either that, or ifconfig down your ipv6 interface or remove
> the autoconf from your machine as necessary until you have a chance
> to test it.  In the mean time, you can visit the webpage here:
> http://204.42.254.5/netops/  I try to always use / referencing
> urls, so it should work just fine for you.  If you notice a url
> that does not just reference /, please let me know.

A smallish hint here:

$ORIGIN example.com.
www		AAAA	2001:db8::1
		A	10.100.13.42
www.ipv6	AAAA	2001:db8::1
www.ipv4	A	10.100.13.42

This way one always has a "forced" fallback to a certain service
Though for HTTP one prolly has to add them to the virtual hosts.
Internet Explorer tends to nicely fall back from IPv6 to IPv4
after a certain timeout depending on how fast an icmp unreach
comes back etc and prolly other factors. I haven't tested it
with the new Opera 7.20b on Windows though which btw does IPv6 ;)
I also don't know how Mozilla handles it as it doesn't do
IPv6 on Windows... and I have no X box to test it at this moment...

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / [email protected] / http://unfix.org/~jeroen/

iQA/AwUBP1Ug1imqKFIzPnwjEQKeMgCeIAcj8vDU7KnvLo7kiEz9fBhjXWUAnA9G
GItH+RCakIiTVYE8SZ2M9VYv
=ZA0L
-----END PGP SIGNATURE-----