IPV6 stateless Address autoconfig N66

[wintermancer]

Question1 : how can I get the N66 to provide IPv6 Stateless Address Auto-configuration on the LAN, especially, if my ISP does not support IPV6 on the WAN?

Can the N66 global IPV6 address prefix be configured on the LAN interface so that it can be given to clients upon request from the LAN side? I don't see an option to do so.

What I think I see is that IPV6 auto-config only works if it gets the prefix from the Wan side. Since my ISP (Uverse) does not support this, then this is not possible.

Question 2: I also get this mysterious 2001:a01:100::2 in the list of dns-servers issued by the N66 dhcp. If I ping that address, I get no reply. I see no way to disable it and so it must be an automatic setting in the N66. Right now, I have only one server on the LAN hardcoded with a 2001:a01:100::30 and ::31 address. So why does the N66 say ::2 is a dns-server?


TY!

 

[jlake]

I don't have Uverse, but I have AT&T dsl. IPv6 is not available in my area so I had to use the 6rd tunnel. To get the 6rd tunnel working on the Asus RT-N66U, I put the "Connection type" on Tunnel 6rd, then I put the "DHCP option" on disable. From there I could configure the 6rd tunnel manually. I used tunnel MTU of 1472, but honestly I never did test it to see what happened if I left it on "0". I probably should have tried it.

Is your Uverse gateway in bridge mode? Or have you placed the Asus router in the Uverse gateway's DMZ? My AT&T DSL modem/router is in bridge mode, so I didn't have to worry about that. Which Uverse gateway do you have?

The settings I used for the manual 6rd tunnel configuration are in the first link below.

I don't need ipv6 right now so I disabled my 6rd tunnel. I did test it using comcast ipv6 speed test and it gave me my normal latency and speed (same as IPv4).....so it was working fine.

If I had to use ipv6 DNS, I would probably just use Google public dns, but I never did bother to enter them. My default AT&T DNS is on google's whitelist, so it worked fine......probably slower but fine.

http://www.att.com/esupport/article.jsp?sid=KB414401&cv=801#fbid=A3JPyshSCAd

ipv6.speedtest.comcast.net

http://www.internetsociety.org/depl...s-works-with-ipv6-can-help-in-your-migration/

http://netalyzr.icsi.berkeley.edu/

Edit: Since I don't have Uverse, I have no idea if any of the above will help you.

 

[wintermancer]

Pass thru on the RG

Hi, Jake. To answer your question I have a Model 3800HGV-B Residential Gateway, and I have set it to pass-thru mode and let the my router (the N66 for the moment) handle security for the LAN.

I am not interested in doing IPV6 to the Internet but rather just getting IPV6 to work correctly on the inside LAN. With the Asus N66 off, all the Win 7 clients communicate via IPV6 link local (since there is no rotuer to provide the IPV6 prefix). When I turn the N66 on, now they communicate using IPV4.

Can you tell me how to ping the IPV6 LAN interface on the N66? Is there such an interface on the LAN side. Could be, but I cannot find mention of it.

Thanks.

 

[jlake]

I'm not real savvy when it comes to IPv6. Maybe someone else can steer you in the right direction. Plus I'm still using WinXPpro on all my computers.

In the link below, the guy ended up going with a business class router.

http://community.linksys.com/t5/Wir.../m-p/452183?comm_cc=HSus&comm_lang=en#M212048

 

[wintermancer]

Thanks for answering.

I installed the latest dd-wrt firmware on the ASUS RT-N66u. Not a nightmare to install but pretty much undocumented and problematic. But finally I am running dd-wrt.

The problem is that dd-wrt does not always work configure correctly or work as expected. There is a steep learning curve to using it and I am at the bottom of the hill looking up. Cann't figure out a single thing yet.

I did look at your link. Of course I would love to have the $400 CISCO 881 - I'm sure its what I would buy if it was say $200.

Hope somebody knows how to fix NAT, IPV6 stateless config, DHCPV6 on dd-wrt. So many problems with it. But my windows 7 clients are now communicating with link-local IPV6 as they should. With the ASUS firmware, they were resorting to IPV4.

 

[wintermancer]

dd-wrt ipv6 stateless auto config

Well, little by little, I am using dd-wrt to fix issues.

1. I did not understand that the add button on the NAT Forwarding screen just added blank lines and erased your temporary entry. Must click apply to add a nat entry. Add blank lines before entering data. Good.

2. System/Management - enable ipv6, enable radvd, and then add a radvd script like this for just ipv6 lan stateless config:

interface br0 {
AdvSendAdvert on;
AdvLinkMTU 1280;
MinRtrAdvInterval 3;
MaxRtrAdvInterval 10;
prefix 2001:a01:100:/64 {
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
};

This came from hxxp://www.jonisdumb.com/2011/01/dd-wrt-ipv6-to-your-local-network.html . Thank-you!