Disable IPV6 Dlink Router

[spiderdan]

I've got a Dlink DIR-655 HW Ver C1 FW 3.00. Wireless works fine but I get no internet connectivity on wired. All the wired computers get an IPV6 address while the wireless ones get IPV4. My ISP, to my knowledge, does not support IPV6. I cannot figure out how to disable IPV6 on this router, but I suspect that would solve the issue. Anyone worked with one of these?

ftp://ftp2.dlink.com/PRODUCTS/DIR-655/REVC/DIR-655_REVC_MANUAL_3.01_EN.PDF
Starting on page 45 al the different IPV6 modes are given. I can't find one that just disables IPv6.

 

[MarkW]

All ISP's should now be supporting IPv6. IPv4 is slowly being phased out.

I go to Google and type in MY IP and get this back and yes, I changed some digits in this:

2609:a000:afd0:15:380c:e5e7:b51:a32
Your public IP address

So while I changed nothing, everything here is now IPv6.

 

[InvalidError]

If your ISP does not support IPv6, the router won't be able to get a route advertisement or prefix delegation from the ISP and without either of these, your router won't have an IPv6 prefix to advertise on your LAN.

If the address you are "getting" starts with fe80, that's the link-local address, the IPv6 equivalent of a 10.x.x.x/192.168.x.x subnet and that address is generated automatically by each device's OS through SLAAC. You would get a link-local IPv6 address even if your LAN had no broadband access or router.

 

[spiderdan]

Google gives me this for my IP address
69.135.201.XXX
Your public IP address

Ipconfig gives
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2605:a000:ccc3:101:11eb:6fb3:2e98:a80a(Preferred)
Temporary IPv6 Address. . . . . . : 2605:a000:ccc3:101:a84f:2cbf:3055:ae5d(Preferred)
Link-local IPv6 Address . . . . . : fe80::11eb:6fb3:2e98:a80a%10(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.168.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : fe80::c2a0:bbff:feea:41c7%10
DHCPv6 IAID . . . . . . . . . . . : 234890068
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-66-BA-31-00-23-54-27-2B-B8
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

I imagine I could use IPV6 through some type of tunnel, but I don't really have a need for it on my LAN. Then again, I can't seem to disable it on the router.

 

[MarkW]

Google is showing you what your system presented itself as. So your system was showing IPv4 when it reached Google.

The other info does show that you have both a public IPv6 address and an internal one.

Why would you even want to disable something that is clearly working?

 

[InvalidError]

Based on your IPv6 address, you are with Time Warner. Based on this page:
http://www.timewarnercable.com/en/support/internet/topics/ipv6.html

It seems TWC has enabled IPv6 support for 90% of their subscriber base.

You may also want to update the firmware since the current version is 3.02.05
Does your router manage to get an IPv4 address from the modem? Is the DHCP server enabled on your router? 169.254.x.x is a default address when the computer is unable to get an IPv4 address, which implies there is a problem with the DHCP server.

 

[MarkW]

Google saw him as being 69.135.201.XXX... So that IPv4 stuff is working.

 

[InvalidError]

Google saw him as being 69.135.201.XXX... So that IPv4 stuff is working.

If his LAN IPv4 is 169.254.x.x, then IPv4 is broken on his LAN - his PC is unable to get a v4 address. This also means the only way he could reach an IPv4 address is through a 6-to-4 tunnel.

 

[MarkW]

You keep saying that. Which would be true except for the fact that his IPv4 when he got to Google was 69.135.201.XXX ... No 169.254.xxx.xxx there.

 

[InvalidError]

You keep saying that. Which would be true except for the fact that his IPv4 when he got to Google was 69.135.201.XXX ... No 169.254.xxx.xxx there.

169.254.168.10 is not a valid/routable LAN address, it is a random address under 169.254.168 reserved for devices that have failed to acquire an address over DHCP. If his PC had successfully acquired an IPv4 address, it would have been 192.168.x.x.

Google may have reported a 69.135.201.x address but his PC could not have reached it through direct IPv4 since his PC does not have a valid IPv4 LAN address to talk to the 655 with.

 

[spiderdan]

The router definitely is getting an IPV4 address from the modem and devices on wireless can connect to the internet just fine. Wired devices cannot connect to the internet. As you've pointed out, I'm not getting and IPV4 address through DHCP. I can't really say if DHCP is working for IPV6. Those addresses were listed as "preferred", so maybe it's also some type of default. Or maybe IPV6 is working just fine but it's isolated from the IPV4 internet connection. I am on Time Warner. Can't really say if I'm part of the 10% that doesn;t have IPv6 or maybe something is up with my hardware.

 

[spiderdan]

Well, I updated my firmware to 3.02 and I seem to be getting both an IPV6 and IPV4 address now and I do have internet connectivity. test-ipv6.com even gives me 9/10 for ipv6 readiness. I guess it is normal to have both ipv6 and ipv4 addresses? Thanks All!

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : cinci.rr.com
Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
Physical Address. . . . . . . . . : 00-23-54-27-2B-B8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2605:a000:ccc3:101:11eb:6fb3:2e98:a80a(Preferred)
Temporary IPv6 Address. . . . . . : 2605:a000:ccc3:101:9549:d3d3:6cd4:9ce1(Preferred)
Link-local IPv6 Address . . . . . : fe80::11eb:6fb3:2e98:a80a%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.101(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, August 28, 2015 4:09:44 PM
Lease Expires . . . . . . . . . . : Saturday, August 29, 2015 4:09:43 PM
Default Gateway . . . . . . . . . : fe80::c2a0:bbff:feea:41c7%10
192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 234890068
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-66-BA-31-00-23-54-27-2B-B8
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

 

[InvalidError]

Well, I updated my firmware to 3.02 and I seem to be getting both an IPV6 and IPV4 address now and I do have internet connectivity. test-ipv6.com even gives me 9/10 for ipv6 readiness. I guess it is normal to have both ipv6 and ipv4 addresses? Thanks All!

Yes, it is normal. This is called dual-stack and will likely remain the standard setup for the next 10+ years.

As for DHCP for IPv6, the preferred method of assigning IPv6 addresses on a typical home LAN is SLAAC auto-configuration: the router advertises the available routable IPv6 prefixes and LAN devices generate the remaining 64 bits, checking that whatever they pad them with is unique on the LAN.

WAN devices being able to get an IPv4 while LAN ones cannot is odd but the firmware update appears to have fixed it in this case.