D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-657 => Topic started by: Hollowlog on March 28, 2014, 03:32:42 PM
-
IPv6 was enabled by Comcast a couple days ago & I'm having trouble connecting to IPv6 web sites. It is set to Autoconfiguration(SLAAC/DHCPv6) per Comcast. Any suggestions?
-
- Link>What Firmware (http://forums.dlink.com/index.php?topic=47512.0) version is currently loaded? Found on the routers web page under status.
Internet Service Provider and Modem Configurations
- What ISP Service do you have? Cable or DSL?
- What ISP Modem Mfr. and model # do you have?
-
Hi Hollowlog,
a bit more details could be quite useful...
E.g.:
What type of IPv6 access is it? Native, 6rd, ... ? A screenshot of your router IPv6 settings? What kind of trouble do you have: Can never connect, cannot connect sometimes, cannot connect from the router, cannot connect from any or only some clients behind the router, ...? Can you show us the IPv6 configuration of one of your clients (e.g. an "ipconfig /all" it is a Windows OS)?
PT
-
Comcast Cable offers native IPv6. I have an Arris WBM760A cable modem. My router is a DIR-657-hardware ver.A1 firmware ver. 1.02. I have 4 access points/switches connected to the router:#1-Linksys E2000 with Tomato firmware(DHCP turned off) #2-DIR-657(DHCP turned off) #3- Netgear GS-108(8 port switch) #4-DIR-651(DHCP turned off). The 651 is for WIFI only. The E2000 & both DIR-657s have IPv6 enabled. I have 1 Win7, 1 Vista, & 2 XP PCs. 1 XP is wireless.
2 days ago I discovered my isp had IPv6 enabled in my area. I was getting 2601:xxxxxxx on all but my wireless PC. After about 2 hours none of my PCs had 2601 addresses. At first I had my E2000 as the main router. When IPv6 failed I made the DIR-657 the main router & still no IPv6. On the XP & Vista I bypassed the access point & connected directly to the router but still no IPv6. When connected directly from my Vista PC to the modem I get a 2001:xxxxxxx address. I'm not sure if I should have IPv6 enabled on the access points.
I can't figure out how to paste my ipconfig & router screenshots into my post.
-
Hi,
to keep things simple it would be useful to leave your 2nd hierarchy devices aside and directly plug a client (e.g. Windows 7) into your 1st hierarchy router DIR-657.
You can use a free image upload service like http://postimage.org/ (http://postimage.org/) and a free imaging software like XnView (http://www.xnview.com/en/xnview/#downloads) to produce and upload screenshots and take their URL here for reference using the "Insert Image" button.
In this way you should show us e.g. your "IPv6 Connection Information" (Status | IPv6) within your DIR-657 box
(http://s29.postimg.org/dmeoq2enr/IPv6_Conn_Info.png)
and your IPv6 setup (Setup | IPv6 | Manual IPv6 Internet Connection Setup).
Windows 7 IPv6 configuration is shown within a command prompt using the command "ipconfig /all". You can copy and paste the command output as text directly or you take a screenshot and post it as picture here.
PT
-
IPv6 connection type: Autoconfiguration (Slaac/DHCPv6)
Network Status: Connected
Wan IPv6 Address: 2001:xxxxxxxxxxxxxxxxxxxxxxxxx/64
IPv6 default gateway: fe80::1edf:fff:fe02:57e2
Lan IPv6 Address: 2601:xxxxxxxxxxxxxxxxxxxxxxxxx/64
Lan IPv6 Link-Local Address: fe80:1e7e:e5ff:fe32:23aa:/64
Primary DNS Address: None
Secondary DNS Address: None
DHCP-PD: Enabled
IPv6 network assigned by DHCP-PD: 2601:x:xxxx:xxx::/64
My DIR-657 stats are listed above.
-
Looks okay, are these conditions stable over a longer time period? Can you successfully ping6 any IPv6 capable Internet sites from within your router (Tools | SYSTEM CHECK)?
Can you show us the IPv6 configuration of your directly connected Win7 PC?
-
Hi again,
perhaps one additional remark concerning your 2nd hierarchy devices #1, #2 and #4:
If you use the WAN uplinks of these devices for connecting to your 1st hierarchy router DIR-657 (directly or via your switch device #3), this ends up with a NAT cascade which works with IPv4 but most probably not with IPv6!
As there is no NAT with IPv6, in a setup like this your devices must support features of the "IPv6 Home Networking Architecture" which is under development only (see here (http://datatracker.ietf.org/wg/homenet/)).
Hence, the only way to include your 2nd hierarchy devices for use with IPv6 is to operate them as bridges by connecting a LAN port of any of those devices to a LAN port of your 1st hierarchy router DIR-657 (directly or via your switch device #3) - From what you said ("I have 4 access points/switches connected to the router ...") I guess this is what you have? If so switch off IPv6 (and DHCPv4, as you already did) on those 2nd hierarchy devices - only use them as dumb switches/bridges. They only need a manually configured IPv4 address for management access out of the IPv4 range of your 1st hierarchy router DIR-657.
PT
-
All of the switches are connected with lan ports only. DHCP is disabled on all but the 657 router. On the DIR-657 being used as a switch I have IPv6 set to Local Connection Only. I don't see any option to actually switch off IPv6.
-
After having no luck trying to get my DIR-657 enabled for IPv6, I started using my old Linksys E2000 with Tomato firmware & I'm now getting IPv6 on my XP,Vista & WIN 7 PCs. The DIR-657 will go on the shelf until someone can tell me how to get it working.
-
Comcast Cable offers native IPv6. I have an Arris WBM760A cable modem. My router is a DIR-657-hardware ver.A1 firmware ver. 1.02. I have 4 access points/switches connected to the router:#1-Linksys E2000 with Tomato firmware(DHCP turned off) #2-DIR-657(DHCP turned off) #3- Netgear GS-108(8 port switch) #4-DIR-651(DHCP turned off). The 651 is for WIFI only. The E2000 & both DIR-657s have IPv6 enabled. I have 1 Win7, 1 Vista, & 2 XP PCs. 1 XP is wireless.
2 days ago I discovered my isp had IPv6 enabled in my area. I was getting 2601:xxxxxxx on all but my wireless PC. After about 2 hours none of my PCs had 2601 addresses. At first I had my E2000 as the main router. When IPv6 failed I made the DIR-657 the main router & still no IPv6. On the XP & Vista I bypassed the access point & connected directly to the router but still no IPv6. When connected directly from my Vista PC to the modem I get a 2001:xxxxxxx address. I'm not sure if I should have IPv6 enabled on the access points.
I can't figure out how to paste my ipconfig & router screenshots into my post.
Firmware version 1.02 does not support IPv6. See the second post in this thread for the acknowledgment of the issue: http://forums.dlink.com/index.php?topic=54204.0 (http://forums.dlink.com/index.php?topic=54204.0)
To fix the issue, roll back to Firmware version 1.01. It can be found here: http://support.dlink.com/ProductInfo.aspx?m=DIR-657 (http://support.dlink.com/ProductInfo.aspx?m=DIR-657)
Downgrade firmware using this process: http://forums.dlink.com/index.php?topic=42457.0 (http://forums.dlink.com/index.php?topic=42457.0)
-
Thanks for posting about that JDW, I had forgotten about that post. ::)
Let us know if downgrading helps Hollowlog...
-
I'll try rolling back the firmware. I was following Comcast's recommendation to first upgrade the firmware to the newest version & then setup IPv6. I don't have time to do it tonight. I'll keep you updated.
-
;)
-
I'll try rolling back the firmware. I was following Comcast's recommendation to first upgrade the firmware to the newest version & then setup IPv6. I don't have time to do it tonight. I'll keep you updated.
I installed fimware ver. 1.01 & IPv6 is up & running. Thanks to JDW & everyone else that responded.
I wish someone from D-Link would contact Comcast & tell them to stop recommending a firmware update.
-
Glad downgrading helped.
This is an issue with the newer FW. I'll add it to the list of issues with IPv6 and mark it as a work around for this model router.
Please get any support information for the 657 from this location:
http://support.dlink.com/ProductInfo.aspx?m=DIR-657 (http://support.dlink.com/ProductInfo.aspx?m=DIR-657)
Please visit again if you need anything.
Enjoy.
-
Had the same issue with Time Warner . I Purchased a shiny new DOCSIS 3.0 modem this afternoon specifically for getting IPv6 and wasted a few hours pulling my remaining hairs out trying to get it to work.
I googled and found this thread. I'd like to say THANK YOU !!!! Reverting to the v1.01 fw solved my problem. :)
-
Thanks for sharing. I've passed this along to D-Link for review. I hope that they can do something for any future releases however since the Amplify line of routers is getting older now, they may not unless there is a security problem that prompts for a new release as these head into Phase out status. I'll do what I can to let them know about the issues.
If v1.01 is working for you, keep it loaded and enjoy.
Had the same issue with Time Warner . I Purchased a shiny new DOCSIS 3.0 modem this afternoon specifically for getting IPv6 and wasted a few hours pulling my remaining hairs out trying to get it to work.
I googled and found this thread. I'd like to say THANK YOU !!!! Reverting to the v1.01 fw solved my problem. :)