I think you're missing the point that ipv4-space to ipv6-space traffic cannot happen unless the chillispot/coovachilli hotspot system supports it. you cannot just say "get a router has ipv6 support, and runs standard chillispot, it would be fine" because it doesn't work like that. ipv6 is not backwards compatible with ipv4, hence the need for dual-stacking. In the period where there are sites hosted on ipv4 addresses and other sites on ipv6 we need to provide our users the ability to connect to both systems. Once the ipv4 addresses have died out we still need to provide our users ipv6 addressing all the way to their system.
IPv4 NAT is not sufficient to map a public ipv6 address/subnet to our 192.168.182.0/24 range because:
1. ipv4 nat doesn't know how to map the networks and never will,
2. NAT is obsolete as stipulated by the ipv6 working group, and therefore there is no such thing as IPv6Nat (and there NEVER will be!),
3. the two networks are incompatible with each other,
4. if the client is given an ipv4 address only they will assume that they aren't connected to ipv6 networks and therefore will not issue AAAA requests to DNS,
5. even if they issued an AAAA request and received 2a00:1450:400c:c01::69 in response the routing tables in their host OS will complain that there is no route adequate for the network in question, (see point 3)
6. if somehow you could trick the routing tables in the client's OS to forward the packet to 192.168.182.1 we return to problem 1 & 2.
Edited by winkleburyctr, 05 February 2012 - 11:42 PM.