Unfortunately it works only after I unplug and plug back WAN cable. If I do it right after reboot it does not work. All symptoms are quite similar to the ones described in the first post on Netgear forum: http://forum1.netgear.com/showthread.php?t=89422
Joined: 13 Mar 2014 Posts: 856 Location: Montreal, QC
Posted: Sat Aug 02, 2014 18:32 Post subject:
Interesting MrDoh who is the other person with the wan issue has a TM-722G.
I wonder if Kong has an idea why these issues are happening with these modems and not the surfboards. Tomato does not seem affected by the issue
*** pure speculation on my part. When MrDoh was testing ipv6 via dhcp-pd any script that started dhcp6c at startup caused the loss of wan connectivity, requiring a cable pull. If I remember correctly He was able to aquire ipv4 and ipv6 when dhcp6c was started manually via CLI.
I wonder if a delayed dhcp6c startup would be the answer to the issue. Also curious what the full tomato logs show
Interesting MrDoh who is the other person with the wan issue has a TM-722G.
I wonder if Kong has an idea why these issues are happening with these modems and not the surfboards. Tomato does not seem affected by the issue
*** pure speculation on my part. When MrDoh was testing ipv6 via dhcp-pd any script that started dhcp6c at startup caused the loss of wan connectivity, requiring a cable pull. If I remember correctly He was able to aquire ipv4 and ipv6 when dhcp6c was started manually via CLI.
I wonder if a delayed dhcp6c startup would be the answer to the issue. Also curious what the full tomato logs show
Only problem I know is, that some modems have trouble with the mac address change at boot, these modems are just buggy and don't handle it right, if that occurs, then usually it helps to first power up the router, then the modem, then connect them.
And it is not just an IPV6 problem, a lot of people(with only ipv4) contacted me on this before and in 90% of the cases upgrading the modems firmware was enough to fix it. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Before R7000 I was using ASUS RT-N66U with the stock firmware and never had issue with IPv6. While modem is definitely a suspect, it also seems that router could be causing problem as well.
Before R7000 I was using ASUS RT-N66U with the stock firmware and never had issue with IPv6. While modem is definitely a suspect, it also seems that router could be causing problem as well.
Yes and there are probably workarounds for the problem if it works with tomato, but first I have to implement the basics and since my and BrainSlayer both have no IPV6 from ISP we need a few advanced users that can deliver a few infos and debug the stuff I implement. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Before R7000 I was using ASUS RT-N66U with the stock firmware and never had issue with IPv6. While modem is definitely a suspect, it also seems that router could be causing problem as well.
Yes and there are probably workarounds for the problem if it works with tomato, but first I have to implement the basics and since my and BrainSlayer both have no IPV6 from ISP we need a few advanced users that can deliver a few infos and debug the stuff I implement.
Hi. I'm in Ireland on vacation, and haven't actually had a chance to try the new releases yet. However, yes, ipv6 works for me both with tomato and even the new stock Netgear debug firmware I've been using with the R7000, so I know it does work if implemented properly.
When I get back from vacation in a couple of weeks, I'll be trying the newest release then, and see what happens *smile*.
Isn't Tomato open source? As in can't how it is implementing IPV6 be reviewed? Not copied, not talking about pirating it. But can't it be examined so how it is implementing IPV6 be one way to evaluate how DD-WRT is doing IPV6? Since one seems to be working better then the other.
I hesitate to say "better" but not sure which work do use. _________________ Jim
Netgear R7000
Kong's 24800M OC to 1200,800
Previously:
Asus RT-N66U
Linksys E3000
Linksys WRT54GS Version 2.1
Buffalo WHR-HP-G54
Linksys WRT54G Version 1.1
ask your providers offering native ipv6. it is working fine. cant talk bout kongs latest, cause i dont have it, but it uses the same componets as i do about a year "manually"
since there is no new mipsel build ( KONG and BS ), i cannot help with any debugging.
And BS latest bricks RT-N66U, so i do not believe, next one will do better _________________ RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
Running 24760M (on my Buffalo WZR-1750DHP) and simply did Setup > IPV6 > Enable and "DHCPv6 with PD" on my Comcast connection and... it just works. Or at least it seems to.
No custom config entered, and I'm assuming DHCPv6/PD is the right option with Comcast, yes (or should I be using "Native IPv6 from ISP"?)
All my computers get IPv6 addresses now, and tests work. The only way I can see my router's IPv6 address is by SSHing into it... Am I correct in assuming that there's nothing (yet) in the UI to show this on the web interface?
And lastly... I have 3 DD-WRT boxes here... one acting as a router (this one), and then two others running DD-WRT but with the WAN connection disabled, essentially in "Access Point Only" mode (all connected via Ethernet backbone). What is the best way to enable IPv6 on those boxes? I'm running the same 24760M build, but I fear if I enable IPv6 on that the same way it will grab a new /64, right? Or am I confused?
Joined: 13 Mar 2014 Posts: 856 Location: Montreal, QC
Posted: Mon Aug 04, 2014 14:42 Post subject:
DaveTheNerd wrote:
Running 24760M (on my Buffalo WZR-1750DHP) and simply did Setup > IPV6 > Enable and "DHCPv6 with PD" on my Comcast connection and... it just works. Or at least it seems to.
No custom config entered, and I'm assuming DHCPv6/PD is the right option with Comcast, yes (or should I be using "Native IPv6 from ISP"?)
All my computers get IPv6 addresses now, and tests work. The only way I can see my router's IPv6 address is by SSHing into it... Am I correct in assuming that there's nothing (yet) in the UI to show this on the web interface?
And lastly... I have 3 DD-WRT boxes here... one acting as a router (this one), and then two others running DD-WRT but with the WAN connection disabled, essentially in "Access Point Only" mode (all connected via Ethernet backbone). What is the best way to enable IPv6 on those boxes? I'm running the same 24760M build, but I fear if I enable IPv6 on that the same way it will grab a new /64, right? Or am I confused?
Joined: 25 Dec 2010 Posts: 295 Location: Twin Cities, MN
Posted: Mon Aug 04, 2014 14:47 Post subject:
DaveTheNerd wrote:
Running 24760M (on my Buffalo WZR-1750DHP) and simply did Setup > IPV6 > Enable and "DHCPv6 with PD" on my Comcast connection and... it just works. Or at least it seems to.
No custom config entered, and I'm assuming DHCPv6/PD is the right option with Comcast, yes (or should I be using "Native IPv6 from ISP"?)
All my computers get IPv6 addresses now, and tests work. The only way I can see my router's IPv6 address is by SSHing into it... Am I correct in assuming that there's nothing (yet) in the UI to show this on the web interface?
And lastly... I have 3 DD-WRT boxes here... one acting as a router (this one), and then two others running DD-WRT but with the WAN connection disabled, essentially in "Access Point Only" mode (all connected via Ethernet backbone). What is the best way to enable IPv6 on those boxes? I'm running the same 24760M build, but I fear if I enable IPv6 on that the same way it will grab a new /64, right? Or am I confused?
Some of these IPv6 test sites are complaining that ICMPv6 packets are being filtered. http://ipv6-test.com/pingtest/ specifically shows that I can't respond to ICMPv6 pings that are WAN-generated pings (I can definitely respond to them from my LAN, FWIW).
Seems from the IPv6 spec that ICMPv6 is a pretty important thing as we move forward... is it being intentionally disabled in DD-WRT for some reason I'm not yet grokking?[/url]
Last edited by DaveTheNerd on Mon Aug 04, 2014 20:25; edited 1 time in total
Joined: 13 Mar 2014 Posts: 856 Location: Montreal, QC
Posted: Mon Aug 04, 2014 18:01 Post subject:
DaveTheNerd wrote:
Some of these IPv6 test sites are complaining that ICMPv6 packets are being filtered. http://ipv6-test.com/pingtest/ specifically shows that I can't respond to ICMPv6 pings that are WAN-generated pings (I can definitely respond to them from my LAN, FWIW).
Seems from the IPv6 spec that IMVPv6 is a pretty important thing as we move forward... is it being intentionally disabled in DD-WRT for some reason I'm not yet grokking?[/url]
Correct the default firewall blocks all icmpv6 forwarding to clients behind the router. Most people feel more secure in having this traffic blocked however rfc4890 and the rfcs mentioned within state that all hosts should permit some of icmpv6 traffic to pass. Failing to do so can have some negative implications with ipv6, however most home users will probably not notice.
Somewhere back on page 5 or so I posted a slightly modified rfc4990 reference script which can be used with ddwrt.
Note ipv6 via ddwrt webif is brand new and kong is working on implementing various ipv6 components.