nanog mailing list archives
Re: turning on comcast v6
From: Mark Andrews <marka () isc org>
Date: Thu, 12 Dec 2013 12:11:35 +1100
In message <CAKr6gn11nLzELbeMKksWAZuR6Tm0A6_kSsJDeF3d=9_N6p0ijA () mail gmail com> , George Michaelson writes:
I am probably closer to consumer behaviour at home than most of you. I don't regard my home router as a vehicle for hackery beyond clue I can find on the end user public lists and rarely if ever even apply that, and I run stock factory billion code on my billion ADSL2+ home gateway. I just enabled the ADSL2+ profile which had IPv6 and restarted. It came up immediately with a /56 and I haven't touched it since. I have been using it to SSH back home quite comfortably with an almost unmodified ACLset to permit port 22 inbound. This is on Internode, in Australia. So, while I fully acknowledge the reality is that for a lot of people, cable and other complex head-end systems needed change and the experience of going dual-stack can be painful, I want to assert IT DOESNT HAVE TO BE and I am proof by example It just worked.
And it should "just work" if you have two router daisy chained. PD was designed to allow this to work. The home router vendors had all the protocols required to make it work. They choose not to implement a working solution. It isn't that hard to supply a take a PD request on one interface and make a upstream request if you don't have unassigned space to hand out then return the response add routing table entries to keep it all working. One can do more complicated stuff than that like running a routing protocol but static routes also work. It may not be optimal but there was nothing stopping those other vendors from coding the support. Most home routers already do stuff like that in IPv4 for DNS servers and other protocol elements. They take what they have learnt from upstream as supply it downstream. Mark
On Thu, Dec 12, 2013 at 8:01 AM, Mark Andrews <marka () isc org> wrote:In message <A026246E-F884-47F0-9225-AFAA87CD35B1 () steffann nl>, Sander Steffann writes:Hi, Op 11 dec. 2013, om 20:46 heeft Kinkaid, Kyle <kkinkaid () usgs gov> het volgende geschreven:I'm curious, do you know of a consumer-grade router which supports DHCPv6-PD?I have tested a whole bunch of them more than a year ago. I can remember seeing IPv6 DHCPv6-PD client support on gear from AVM Fritz!box, D-Link, Draytek, Zyxel, Linksys, Asus, Thompson/Technicolor and I must be forgetting a few as well. Most of them weren't very advanced, but they worked to get IPv6 connectivity in the house. What I am missing these days is DHCPv6-PD server support to re-delegate parts of the prefix it got from the ISP downstream to other home routers. As far as I know AVM Fritz!box is the only one that does that today.And the need for it was obvious when all the other boxes were being developed. Daisy chaining routers has been part of home setups for many, many years if only to get configuration control because the ISP router is not configurable enough. There was no reason to think that this would change with IPv6.Cheers, Sander-- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka () isc org--047d7b10ccc3ea2d0c04ed4a023d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">I am probably closer to consumer behaviour at home than mo= st of you. I don't regard my home router as a vehicle for hackery beyon= d clue I can find on the end user public lists and rarely if ever even appl= y that, and I run stock factory billion code on my billion ADSL2+ home gate= way.<div> <br></div><div>I just enabled the ADSL2+ profile which had IPv6 and restart= ed. It came up immediately with a /56 and I haven't touched it since. I= have been using it to SSH back home quite comfortably with an almost unmod= ified ACLset to permit port 22 inbound.</div> <div><br></div><div>This is on Internode, in Australia.</div><div><br></div=<div>So, while I fully acknowledge the reality is that for a lot of people=, cable and other complex head-end systems needed change and the experience= of going dual-stack can be painful, I want to assert IT DOESNT HAVE TO BE = and I am proof by example</div> <div><br></div><div>It just worked.</div></div><div class=3D"gmail_extra"><= br><br><div class=3D"gmail_quote">On Thu, Dec 12, 2013 at 8:01 AM, Mark And= rews <span dir=3D"ltr"><<a href=3D"mailto:marka () isc org" target=3D"_blan= k">marka () isc org</a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"><br> In message <<a href=3D"mailto:A026246E-F884-47F0-9225-AFAA87CD35B1@steff= ann.nl">A026246E-F884-47F0-9225-AFAA87CD35B1 () steffann nl</a>>, Sander St= effann<br> writes:<br> <div><div class=3D"h5">> Hi,<br> ><br> > Op 11 dec. 2013, om 20:46 heeft Kinkaid, Kyle <<a href=3D"mailto:kk= inkaid () usgs gov">kkinkaid () usgs gov</a>> het<br> > volgende geschreven:<br> > > I'm curious, do you know of a consumer-grade router which sup= ports<br> > > DHCPv6-PD?<br> ><br> > I have tested a whole bunch of them more than a year ago. I can rememb= er<br> > seeing IPv6 DHCPv6-PD client support on gear from AVM Fritz!box, D-Lin= k,<br> > Draytek, Zyxel, Linksys, Asus, Thompson/Technicolor and I must be<br> > forgetting a few as well. Most of them weren't very advanced, but = they<br> > worked to get IPv6 connectivity in the house. What I am missing these<= br> > days is DHCPv6-PD server support to re-delegate parts of the prefix it= <br> > got from the ISP downstream to other home routers. As far as I know AV= M<br> > Fritz!box is the only one that does that today.<br> <br> </div></div>And the need for it was obvious when all the other boxes were b= eing<br> developed. =A0Daisy chaining routers has been part of home setups for<br> many, many years if only to get configuration control because the<br> ISP router is not configurable enough. =A0There was no reason to think<br> that this would change with IPv6.<br> <br> > Cheers,<br> > Sander<br> <span class=3D"HOEnZb"><font color=3D"#888888">--<br> Mark Andrews, ISC<br> 1 Seymour St., Dundas Valley, NSW 2117, Australia<br> PHONE: <a href=3D"tel:%2B61%202%209871%204742" value=3D"+61298714742">+61 2= 9871 4742</a> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 INTERNET: <a href=3D"mailto:= marka () isc org">marka () isc org</a><br> <br> </font></span></blockquote></div><br></div> --047d7b10ccc3ea2d0c04ed4a023d--
-- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka () isc org
Current thread:
- Re: turning on comcast v6, (continued)
- Re: turning on comcast v6 Jared Mauch (Dec 11)
- Re: turning on comcast v6 Livingood, Jason (Dec 11)
- Re: turning on comcast v6 Kinkaid, Kyle (Dec 11)
- Re: turning on comcast v6 Leo Bicknell (Dec 11)
- Re: turning on comcast v6 Blake Dunlap (Dec 11)
- Re: turning on comcast v6 joel jaeggli (Dec 11)
- Re: turning on comcast v6 Sander Steffann (Dec 11)
- Re: turning on comcast v6 Mark Andrews (Dec 11)
- Re: turning on comcast v6 jimb (Dec 11)
- Re: turning on comcast v6 George Michaelson (Dec 11)
- Re: turning on comcast v6 Mark Andrews (Dec 11)
- Re: turning on comcast v6 Bill Weiss (Dec 13)
- Re: turning on comcast v6 Christopher Morrow (Dec 18)
- Re: turning on comcast v6 Nicholas Oas (Dec 19)
- Re: turning on comcast v6 Rob Seastrom (Dec 11)
- Re: turning on comcast v6 Ryan Wilkins (Dec 12)
- Re: turning on comcast v6 Steve Meuse (Dec 12)
- Re: turning on comcast v6 Randy Bush (Dec 12)
- Re: turning on comcast v6 ML (Dec 19)
- Re: turning on comcast v6 Christopher Morrow (Dec 19)
- Re: turning on comcast v6 Owen DeLong (Dec 19)