XPost: comp.os.linux.networking   
   From: rjk@greenend.org.uk   
      
   Noob  writes:   
   > Obviously, the STB is not able to talk directly   
   > to ipv6.google.com since it does not support IPv6.   
   >   
   > I see several work-arounds. The server could be dual   
   > stack, and provide ALSO an IPv4 address, but 1) IPv4   
   > address space is running out and 2) the STB might be   
   > confused by the IPv6 addresses in the DNS reply, even   
   > if it should just ignore them.   
   >   
   > The modem, which is already performing NAT, could   
   > "rewrite" the DNS packets, and somehow map a few   
   > IPv6 addresses to unused "virtual" IPv4 addresses.   
   >   
   > Is this what NAT-PT proposed?   
      
   I think so.  There's also an RFC describing some of the problems with   
   it.  Ultimately the only right answer is: the STB must be upgraded to   
   support IPv6.   
      
   In the meantime you may be able to persuade it to use application-level   
   gateways.  For instance, an IPv4-only host accessing the web via a web   
   proxy on a dual-stack host would be able to see IPv6-only web sites.   
      
   --   
   http://www.greenend.org.uk/rjk/   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)