Stories
Slash Boxes
Comments

SoylentNews is people

posted by n1 on Thursday May 05 2016, @06:36PM   Printer-friendly
from the not-yet dept.

APNIC reminds us that "there are now a large number of ISPs, data centres, cloud services, and software that now support IPv6" and "enabling IPv6 can be as simple as clicking a button on your WiFi router."

I turned it on, with Comcast I received an IPv6 route but no DNS server. Fortunately, Google Public DNS has unmemorable addresses, which I was able to configure manually.

2001:4860:4860::8888
2001:4860:4860::8844

It works. "There's only one thing left for you to do: Turn it on!"

[ ed: What are the alternatives to Google's Public DNS? ]


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Insightful) by TheGratefulNet on Thursday May 05 2016, @06:39PM

    by TheGratefulNet (659) on Thursday May 05 2016, @06:39PM (#342163)

    sorry, not willing to run dual-stack at home. zero reason. I get an ipv4 dhcp addr and it works fine with my firewall, router, nat setup, etc.

    works fine. I can ping any site I want.

    go sell ipv6 to the carriers. let them figure it out.

    (I worked at a smartphone tech company a few yrs ago and we counted on samsung having a good ipv6 stack for android. of course, samsung can't program its way out of a paper bag without bugs and errors, so ipv6 was a pain in the ass. if big old sammy can't get it right, why should I even care about taking on more problems?)

    --
    "It is now safe to switch off your computer."
    Starting Score:    1  point
    Moderation   +2  
       Insightful=2, Total=2
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4  
  • (Score: 1) by daaelar on Thursday May 05 2016, @06:44PM

    by daaelar (5403) on Thursday May 05 2016, @06:44PM (#342167)

    Samsung isn't writing the v6 stack for their android phones, Google is. Google supports RFC 2460 and 6101, but unfortunately is refusing to support 3315. That means SLAAC works fine, but DHCPv6 doesn't. That all has to do with Google, though. And for the record, IPv6 in the home has been exploding with new home gateways and sites supporting the stack. I'm reading this site via native v6 right now and it's working very well.

    • (Score: 4, Informative) by Scruffy Beard 2 on Thursday May 05 2016, @06:52PM

      by Scruffy Beard 2 (6030) on Thursday May 05 2016, @06:52PM (#342172)

      That reminds me: for a few months I had native ISP-provided IPv6 (IPv4 only at the moment).

      It appears that the Gnome Network Manager does not support SLAC: only DHCPv6. That meant my Android and machine with no network manager just worked, while Linux Mint did not.

      Not sure if it is gnome network manager because: the about message has a non-functional network at cinnamon dot org e-mail address and the words "Network Manager Applet".

    • (Score: 2, Touché) by daaelar on Thursday May 05 2016, @06:53PM

      by daaelar (5403) on Thursday May 05 2016, @06:53PM (#342173)

      Bah, that should have said RFC 6106, not 6101

    • (Score: 2) by TheGratefulNet on Thursday May 05 2016, @06:57PM

      by TheGratefulNet (659) on Thursday May 05 2016, @06:57PM (#342176)

      I don't remember if we had issues with nexus phones or if it was just samsungs. we bet on samsung and we lost. they could not deliver a quality ipv6 phone stack. the details escape me as it was a few yrs ago and I was more on the unix side than the phone/android side.

      still, the one who SHIPS HARDARE is where the buck stops. so I would still blame samsung. they are big enough that they have funds and resources to fix killer bugs.

      as for ipv6 at home, I still see no need until I'm forced. what do I gain, exactly, by changing things and HAVING to run dual stacks? I simply don't see any benefit for the effort involved.

      perhaps on a brand new setup; but to update old working ones? if it aint broke, the saying goes....

      --
      "It is now safe to switch off your computer."
  • (Score: 3, Interesting) by Scruffy Beard 2 on Thursday May 05 2016, @06:45PM

    by Scruffy Beard 2 (6030) on Thursday May 05 2016, @06:45PM (#342168)

    Not if you want to use VOIP.

    At the moment I am contemplating tunnelling to my Asterisk server that has ports forwarded to it. I suspect going straight to my VOIP provider would have less latency, but I can not receive incoming calls while using NAT.

    • (Score: 2) by tibman on Thursday May 05 2016, @08:06PM

      by tibman (134) Subscriber Badge on Thursday May 05 2016, @08:06PM (#342207)

      Doesn't port forwarding solve this? Or worst case, DMZ *shudders*

      --
      SN won't survive on lurkers alone. Write comments.
      • (Score: 2) by Scruffy Beard 2 on Thursday May 05 2016, @08:13PM

        by Scruffy Beard 2 (6030) on Thursday May 05 2016, @08:13PM (#342213)

        No port-forwarding does not work because I do not get a public IP address from my mobile provider.

        I called and asked about IPv6. They will do it if I upgrade to a business plan with a higher minimum monthly commitment.

        • (Score: 2) by frojack on Friday May 06 2016, @02:25AM

          by frojack (1554) on Friday May 06 2016, @02:25AM (#342366) Journal

          Voip handles non public IPs via STUN servers [voip-info.org].

          --
          No, you are mistaken. I've always had this sig.
          • (Score: 0) by Anonymous Coward on Friday May 06 2016, @07:09AM

            by Anonymous Coward on Friday May 06 2016, @07:09AM (#342458)

            We are talking about *incoming* connections. STUN is not going to help you there.

            TURN does this, but requires turning the incoming connection into an outgoing one - which means the host receiving the connection needs to know when to expect a connection. That mean always having a different connection open for signalling. I'm guessing that's what he meant by tunneling through his asterisk server.

            • (Score: 2) by frojack on Friday May 06 2016, @03:07PM

              by frojack (1554) on Friday May 06 2016, @03:07PM (#342577) Journal

              We are talking about *incoming* connections. STUN is not going to help you there.
              TURN does this, but requires turning the incoming connection into an outgoing one - which means the host receiving the connection needs to know when to expect a connection.

              You are right of course. I linked the wrong page as well.

              http://www.voip-info.org/wiki/view/TURN [voip-info.org]

              The thing is, MOST VOIP/SIP providers (even free ones) supply TURN services on their systems precisely because such a vast portion of the net is behind NAT routers, and just about always has been. NAT traversal hasn't been a problem for Voip or Sip for some time now, and TURN was in place in one form or another since LONG before the relevant RFCs were formalized.

              Most providers have TURN/STUN/ICE all bundled into one server on their network. Incoming calls are just automatically routed to what ever network you happen to be on at the moment. Even cellular networks.

              If the OP has a problem its probably because his Asterisk server is behind a double nat (his and his ISPs), but even this is not a problem with any (free) external TURN service configured in his asterisk box. If

              --
              No, you are mistaken. I've always had this sig.
    • (Score: 2) by edIII on Thursday May 05 2016, @09:43PM

      by edIII (791) on Thursday May 05 2016, @09:43PM (#342256)

      While I've not configured it myself, I believe Asterisk has supported IPv6 since 1.8. PJSIP in Asterisk 11 does support IPv6, and there is information out there on how to set it up and configure it.

      --
      Technically, lunchtime is at any moment. It's just a wave function.
  • (Score: 0) by Anonymous Coward on Thursday May 05 2016, @06:58PM

    by Anonymous Coward on Thursday May 05 2016, @06:58PM (#342177)

    Had to turn off ipv6 on some friends' equipment for awhile. Local service providers hand out ipv6 addresses but don't actually route them, and their technical staff doesn't understand it enough to do anything.

    On the plus side, for 30-45 minutes of work I talked an ISP into 30 days free service to compensate for them not having internet for 2-3 days. Got paid with home-cooked dinner and $50. :)