Almost got IPv6 tunneling working....


Recommended Posts

Im trying to setup IPv6 tunneling (Hurricane Electric) with DD-WRT but the test sort of fails....

post-460145-0-25477900-1349903267_thumb.

There is the results

On my PC everything seems to be passing fine

post-460145-0-26025300-1349903299_thumb.

What things could be going wrong?

Pinging a IPv6 address just gives General Error, nothing else

Link to comment
Share on other sites

I don't see a ipv6 gateway?? Kind of hard to go anywhere without a gateway

post-14624-0-31099800-1349923516.png

Where is your DNS as well? Oh -- you just did ipconfig not /all

Link to comment
Share on other sites

I don't see a ipv6 gateway?? Kind of hard to go anywhere without a gateway

If the ISP supports IPv6 sans tunneling (such as Comcast HSI with a D3 modem) then there will be a conflict with HE.

I have such a modem (ARRIS WBM-760A) that supports IPv6 via the default settings; however, due to my *router* being IPv6-hostile (NETGEAR WNR3500v1 doesn't support DD-WRT or the improved firmware of the WNR3500v2/3500L due to a chipset change), I can't use an HE tunnel for IPv6. When I truly *need* IPv6, I switch to a direct-to-modem connection - then, IPv6 works just dandy.

It's not a Windows issue, either, as this is with any version of Windows since XP, or any other IPv6-ready OS.

I'm hoping to get a WNDR3700 from Staples (currently on sale for $79.99 before trade-in).

Link to comment
Share on other sites

"If the ISP supports IPv6 sans tunneling (such as Comcast HSI with a D3 modem) then there will be a conflict with HE."

Where do you people come up with this stuff?? BS plain and simple -- does not matter if your ISP hands you a dualstack IPv6 or not -- you can still create a HE tunnel over your IPv4 address.

Did you even look at his settings? he has NO ipv6 gateway ;)

  • Like 1
Link to comment
Share on other sites

Can you ping hosts from the router? and have you installed radvd or similar? (to announce the IPv6 router to your network)

Also, make sure the MTU is correct, I've had issues with that in the past.

Link to comment
Share on other sites

Well its kind of odd that I got assigned a IPv6 IP by my router (I know I did not set that IP static wise) but did not get assigned a gateway.

Not home right now, so Ill get back to you in about 10 hours :p

Link to comment
Share on other sites

No not really - ipv6 works completely different. Dhcp does not hand out gateway in ipv6, shoot you don't even have to have dhcp hand out the ipv6 address ;)

People think its just some more numbers and letters added to the address, and then it works the same -- no not even close ipv6 is a complete new ballgame.

Link to comment
Share on other sites

No I didn't say he had to set it manually. Router discover should pick it up, but he prob as something not quite right there.

Just noticed on his routes -- he added default route -- but that is not in the same prefix

edit: Just looked a little deeper, where did you get your IPv6 IP range from to setup?? That didn't look like a HE range to me.

inet6num: 2001:0DB8::/32

netname: IPV6-DOC-AP

descr: IPv6 prefix for documentation purpose

country: AP

admin-c: HM20-AP

tech-c: HM20-AP

status: ALLOCATED PORTABLE

remarks: This address range is to be used for documentation

remarks: purpose only. For more information please see

Not sure how your going to go anywhere with that address?

Link to comment
Share on other sites

No not really - ipv6 works completely different. Dhcp does not hand out gateway in ipv6, shoot you don't even have to have dhcp hand out the ipv6 address ;)

People think its just some more numbers and letters added to the address, and then it works the same -- no not even close ipv6 is a complete new ballgame.

By dhcp, I ment radvd. Mixed up terms there sorry.

Anyways, I got back here and internet was VERY slow so I disabled IPv6 on my router and its speedy again.

Link to comment
Share on other sites

I'd say that's probably unrelated (considering IPv6 wasn't even working on your internal network), My HE endpoint is in LA so I have a fair bit of latency, but it's still not that bad (Hell, YouTube ran over IPv6 for me for a while, and it actually sped up video loading)

Can you show your config for the HE tunnel on your router? and any diagnostic information from it (ping ipv6.google.com, etc.)

Link to comment
Share on other sites

I'd say that's probably unrelated (considering IPv6 wasn't even working on your internal network), My HE endpoint is in LA so I have a fair bit of latency, but it's still not that bad (Hell, YouTube ran over IPv6 for me for a while, and it actually sped up video loading)

Can you show your config for the HE tunnel on your router? and any diagnostic information from it (ping ipv6.google.com, etc.)

Like I said, I kinda left it there be; Everything disabled.

Link to comment
Share on other sites

Well for starters he was never anywhere close to having it setup.

He did not have an ipv6 address that is even valid, let alone from HE. 2001:0DB8::/32

Not sure what guide he used, maybe they were documenting what how to set it up with the documentation prefix he used and he used that vs what he should of used per his he tunnel info given on the HE site when he created his tunnel.

Link to comment
Share on other sites

Yup that must of been the guide

He must of missed this part


interface br0
{
   AdvSendAdvert on;
   prefix 2001:db8:9:10ee::/64
   {
   };
};
Notice that prefix is same text ?Routed /64? under your tunnel details.

Notice that prefix is same text ?Routed /64? under your tunnel details.

The guy using it in his guide is fine - in fact that is what the prefix is suppose to be used for, documentation ;)

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.