Slashdot Mirror


Comcast Begins Native IPv6 Deployment To End Users

First time accepted submitter Daaelarius writes "Comcast has begun deployment of Native IPv6 access to end users. The deployment is starting out small with a single market, but is expected to expand rapidly. They have provided ... more in depth technical details." Finally; native dual-stack IPv6 for home customers. Perhaps we can avoid a post-exhaustion future of NAT-upon-NAT and use restrictions.

4 of 326 comments (clear)

  1. Re:Yeah right by vlm · · Score: 5, Insightful

    not being directly connectable (ie., behind NAT)

    WRONG.

    on ipv4 NAT is generally implemented as a stateful firewall that also rewrites addresses.

    There is absolutely nothing preventing a firewall on ipv6 that is stateful, that leaves addresses alone.

    The security gain comes from the stateful firewall, not the rewriting addresses.

    --
    "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
  2. Re:Yeah right by Bill,+Shooter+of+Bul · · Score: 3, Insightful

    If my toaster is smart enough to realize that the toast is burning, and communicate that fact to another device, it should be capable of not burning the toast in the first place.

    --
    Well.. maybe. Or Maybe not. But Definitely not sort of.
  3. Re:Yeah right by tchuladdiass · · Score: 3, Insightful

    And what makes you think that the IPv6 off-the-shelf routers won't default to a stateful firewall? In fact, I can't see any vendor not enabling that by default, and advertizing it in big bold letters (not the techno-jargon, but "Buy this box and keep the hackers out"). And the ISPs are likely to include such functionality in their cable/DSL modem, since they could benefit from fewer zombies on the network.

  4. Re:Yeah right by GPLHost-Thomas · · Score: 5, Insightful

    That's reverse thinking. If you need a firewall, setup a firewall, don't setup NAT instead.