<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFCC" text="#000000">
Hi<br>
<br>
Ok, this is a bit more complicated than I would have thought. But
then I have IPv4 with 5 public addresses and a 4over6 tunnel, that
essentially does what I need and is also what I can get.<br>
<br>
In this country, no ISP is offering native IPv6 and getting more
than one IPv4 is rare, this might be one of the reasons.<br>
<br>
I use DLINK DIR-825, they *should* be able to connect to native IPv6,
with the unofficial 2.05EU firmware they seem to work. The tunnel is
very stable.<br>
<br>
Please find a solution, so ISPs in this country can start using IPv6
as well.<br>
<br>
<br>
<div class="moz-cite-prefix">On 23/11/12 16:46, Benoit Panizzon
wrote:<br>
</div>
<blockquote cite="mid:201211231646.40253.benoit.panizzon@imp.ch"
type="cite">
<pre wrap="">Hi Sten
</pre>
<blockquote type="cite">
<pre wrap="">Just a thought, to me it looks like you are deploying IPv6 the same way
as IPv4? One address at a time to each costumer.
I believe the idea is that each customer gets a prefix/64 and will
assign IPs from that as needed.
</pre>
</blockquote>
<pre wrap="">
We use all scenarios in our lab.
- Non-Temporary Addresses
- Temporary Addresses
- Prefixes
If a customer connects a Windows 7 client to his modem, Windows 7 does not
request a prefix, but just one address.
If a customer connects one of the very few existing IPv6 aware CPE routers to
his modem, it will hopefully correctly request a prefix. (works that way with
Mikrotik routers)
If a customer connects a unix box with ISC dhcp Client to his modem and does a
-N -N -T -T -T -P -P -P -P then he will request two non-temp, three temp and
four prefixes :-)
The modem 'intercepts' the DHCP6 solicit message from the client connected
behind the modem and adds vendor specific information (option 17) enterprise
ID from CableLabs (ID 4491), and among other suboption 1026 which contains the
Cmac Address of that cable modem. Those Cmac Addresses are registered at the
CMTS and our provisioning system known which customer got which Cmac address.
(Traffic shaping and telephony is also done on the modem). So this is the
element identifying the customer.
</pre>
<blockquote type="cite">
<pre wrap="">In that case you will need to keep track of the prefixes as any host
using that prefix must belong to that customer? Would this satisfy the
legal requirements?
</pre>
</blockquote>
<pre wrap="">
Sure, if I find a way of logging Suboption 1026 which is also added to prefix
requests I'm fine :-)
</pre>
<blockquote type="cite">
<pre wrap="">Using a 6over4 tunnel today, I get a prefix/64 and it is my task to
build any address using that prefix the way it pleases me, even if I may
have 100s of hosts.
</pre>
</blockquote>
<pre wrap="">
We don't operate mass-tunnels. We want to deploy native ipv6 to the broadband
customer.
Mit freundlichen Grüssen
Benoit Panizzon
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
</pre>
</body>
</html>