RE: IPv6 Home Use to stimulate deployment over IPv4-NAT

["Jeroen Massar" <jeroen@unfix.org>]

Alain Durand wrote:

<SNIP>

> Even better, this could be implemented on a different
> box than the actual v4 exit router!
> The connection scenario would then be the following:
> 
>                     v4 Internet
>                         |
>                         |
>                         |
> 
>                        CPE
>                  v4 acces router
>                      v4 NAT
>                         |
>                         |
>           ------------------------------------------   Home lan
>               |                |           |
>            v6 access         Host1       Host2
>              router
>       (Tunnel Broker client)
> 
> 
> That way folks who do not want to (or can not)replace their CPE
> just have to add another box in the home network to provide
> v6 connectivity to the entire home lan.

Which one can do now by simply installing eg the freenet6 client
onto one of the existing windows/*nix boxes which will advertise
the IPv6 prefix onto the local subnet. The only trick here is
to have the CPE forward proto-41 to your v6-gate or using Teredo.
Btw 'just have to add' is sometimes expensive for some people.

> Now, as it has been pointed out, this is a typical case
> where the access router is a client to a tunnel broker.
> The question is what can we do to simplify the tunnel
> set-up from the router to the tunnel broker.
> If we decide to go that route, a tunnel set up protocol
> like the one Marc Blanchet was suggesting now become
> a interesting solution
> 
> The configuration of the v6 access router would require:
> - providing the IPv4 address (or name) of the IPS Tunnel Broker
> - providing the credentials negatiated out of band with the ISP (e.g. 
> username/passwd)
> - specifying the encapsulation mode: IPv6/IPv4 or IPv6/UDP/IPv4 or 
> IPv6/PPP/IPv4
> - specifying the IPv6 security policy
> 
> Yes, there is manual configuration involved, but I think it is minimal
> and not too different to what home users do today to configure their
> DSL router.

Which would usually result in a clickety-click Windows interface to
configure one of the machines to be the gateway.
Which should be doable for most users as long as there is some nice
document available with per-dialog screenshots. Then again... ;)
One thing that must be done in these clients is to check wether
there is native connectivity already because if there is one should
not be using a tunnel (6in4,6to4,isatap,teredo,...).

Greets,
 Jeroen