Unintentionally received IPv6



  • I have some question regarding on IPv6. Currently I have an ISP that i am subscribing that provide the following IPv6 address.
    Ethernet adapter Ethernet:

    Connection-specific DNS Suffix  . :
      Description . . . . . . . . . . . : Intel(R) Ethernet Connection I218-LM
      Physical Address. . . . . . . . . : 20-1A-06---__
      DHCP Enabled. . . . . . . . . . . : Yes
      Autoconfiguration Enabled . . . . : Yes
      IPv6 Address. . . . . . . . . . . : fd1c:81df:a24d:0:b103:b998:ce64:14f5(Preferred)
      IPv6 Address. . . . . . . . . . . : fd9a:ae3b:8b7::2ca(Preferred)
      Lease Obtained. . . . . . . . . . : Thursday, June 9, 2016 6:21:35 PM
      Lease Expires . . . . . . . . . . : Monday, July 17, 2152 12:56:08 AM
      IPv6 Address. . . . . . . . . . . : fd9a:ae3b:8b7:0:b103:b998:ce64:14f5(Preferred)
      Temporary IPv6 Address. . . . . . : fd1c:81df:a24d:0:95da:c256:423a:3b83(Preferred)
      Temporary IPv6 Address. . . . . . : fd9a:ae3b:8b7:0:95da:c256:423a:3b83(Preferred)
      Link-local IPv6 Address . . . . . : fe80::b103:b998:ce64:14f5%3(Preferred)
      IPv4 Address. . . . . . . . . . . : 10.1.1.83(Preferred)
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Lease Obtained. . . . . . . . . . : Thursday, June 9, 2016 6:21:35 PM
      Lease Expires . . . . . . . . . . : Thursday, June 9, 2016 8:21:32 PM
      Default Gateway . . . . . . . . . : 10.1.1.254
      DHCP Server . . . . . . . . . . . : 10.1.1.254
      DHCPv6 IAID . . . . . . . . . . . : 52435462
      DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-F6-9D-18-20-1A-06-13-47-3E
      DNS Servers . . . . . . . . . . . : fd9a:ae3b:8b7::1
                                          10.1.1.254
      NetBIOS over Tcpip. . . . . . . . : Enabled

    I have configure only PPPoE IPv4 and set IPv6 to None. So i am wondering/puzzle why do i received the IPv6 in my LAN as this cause some inconvenience to my environment as I will be resolving IPv6 DNS first before IPv4.

    My current setup
    2.3.1-RELEASE-p1 (amd64)
    AMD G-T40E Processor
    2 CPUs: 1 package(s) x 2 core(s)



  • They all look like local addresses to me, not ones assigned from your ISP.

    https://en.wikipedia.org/wiki/Unique_local_address

    Prefixes in the fd00::/8 range have similar properties as those of the IPv4 private address ranges:

    They are not allocated by an address registry and may be used in networks by anyone without outside involvement.
    They are not guaranteed to be globally unique.

    https://en.wikipedia.org/wiki/Link-local_address

    In the Internet Protocol Version 6 (IPv6), the address block fe80::/10 has been reserved for link-local unicast addressing.[3] To conform to standard /64 addressing on subnets, the actual link local addresses are assigned with the prefix fe80::/64.
    


  • Change to a more competent ISP that knows either to provide a real IPv6 connection that works or nothing at all. You should never receive fd00::/8 addresses from ISP DHCPv6 or router advertisements.



  • well i would appreciate if I know how to prevent getting IPv6. Even if my ISP does provide proper IPv6 address I would have problem in getting External DNS from IPv6 rather than local DNS so I can resolved my local web server which is not accessible on the Internet.



  • You can disable IPv6 protocol on Windows by going through each interface properties and unchecking "Internet Protocol Version 6 (TCP/IPv6)" checkbox.

    Then disable the remaining IPv6 facilities on Windows by running:

    netsh interface ipv6 set teredo disabled
    netsh interface ipv6 isatap set state disabled
    netsh interface ipv6 6to4 set state disabled
    

    On elevated command prompt (cmd.exe as admin)


  • Rebel Alliance Global Moderator

    Or simple solution on windows is just add this reg key and it should all be gone.

    elevated prompt
    reg add hklm\system\currentcontrolset\services\tcpip6\parameters /v DisabledComponents /t REG_DWORD /d 255
    reboot

    Top put it back how you found it
    reg delete hklm\system\currentcontrolset\services\tcpip6\parameters\ /v DisabledComponents /f
    reboot

    When you get ready to use ipv6, the netsh commands jorgeO posted allow you to turn off the 3 different transition methods ms thought in their infinite wisdom it was a good idea to turn all 3 at the same time… JFC they think their user base is just complete morons..

    the reg key above will turn it all off and even the teredo and isatap and 6to4 interfaces will be gone.