<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 8/10/2010 9:54 PM, <a class="moz-txt-link-abbreviated" href="mailto:pritam.ghosh@wipro.com">pritam.ghosh@wipro.com</a> wrote:
<blockquote
cite="mid:39189D563C2E9145952369A51775BA50C4F2D9@KOL-SLK-MBX01.wipro.com"
type="cite">
<pre wrap="">Dear Roland,
Thanks for the reply. No, I don't have any V4 space.
Also, If I publish a Web-portal to an IPv6 address through DNS AAAA
record, will I be able to access the portal from Ipv4 only machines .i.e
without enabling dual-stack in the end-user system?
</pre>
</blockquote>
<br>
Pritam - there are some commercial gateway products that claim to
translate between IPv4 and IPv6 networks, acting as a form of proxy.<br>
You could try putting one of these (or maybe you'll need more if
your IPv6 network is large) at the edge of your network, with your
IPv6 network on the inside, and the IPv6 + IPv4 Internet on the
outside.<br>
Depending on how you have built your BGP link, you may need to
locate this gateway within your provider's datacentre, at the Airtel
end of the BGP link, since you have no IPv4 routing information
passing across the BGP link . I expect you will need an IPv4 address
from your provider's space to allocate to the interface facing your
provider.<br>
<br>
This may solve the ability for your user machines accessing IPv4
locations as well as IPv6 locations.<br>
<br>
To make your IPv6-only web-portal accessable from the rest of the
IPv4 world, you will need to advertise it in DNS with IPv4 A
records. You may be able to get away with a single IPv4 address,
which your provider may be able to allocate to you.<br>
If you can't get even one real IPv4 address, then perhaps you can
host your website on a commercial hosting platform outside your
network, or rent a dedicated server in an outsourced datacentre
offering, which will have real IPv4 addresses that can be published
in DNS, and real IPv4 connectivity.<br>
<br>
Here are links to a couple of products that claim to be able to do
the translation - I haven't used them, don't know if they will work
for you, I expect you are facing a lot of testing and trialling.<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.vantronix.com/products/ipv6/">http://www.vantronix.com/products/ipv6/</a><br>
<a class="moz-txt-link-freetext" href="http://www.f5.com/products/big-ip/feature-modules/ipv6-gateway.html">http://www.f5.com/products/big-ip/feature-modules/ipv6-gateway.html</a><br>
<br>
To access IPv4 websites, you could try the DNS suffix trick
described at <a href="http://www.sixxs.net/tools/gateway/">SixXS</a>
adding '.sixxs.org' to every website address. This won't help you
with inbound IPv4 traffic though.<br>
<br>
Hope this helps a little.<br>
<br>
Paul.<br>
<br>
<br>
<pre class="moz-signature" cols="86">--
Paul Brooks | Mob +61 414 366 605
Layer 10 Advisory | Ph +61 2 9402 7355
-------------------------------------------------------
Layer 10 - telecommunications strategy & network design</pre>
</body>
</html>