Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[EddieZ]

I've noticed that the DIR can only route an IPv6 tunnel from a single internal IP. So no 2 PC's on the LAN can access IPv6 websites through a tunnel. The router maps the protocol 41 (internet sessions) to the tunnel. Will future firmware be able to route more internal LAN ip's to an IPv6 tunnel address?

[Lycan]

I think thats what the Kernel update we recently had was, updating the NAT for IPv6 support.
I'm sure there will be issues with it at first, but we'll get them worked out. I'll pass your info along to the PM, see if they're aware of it. (they may be, we do have another firmware on it's way.)

[EddieZ]

Thanks. It's not really that big an issue, but I could be a nice step forward in IPv6 compatibility is more clients could have at least a tunneled connection.

I'm still waiting on that new one

[funchords]

I've noticed that the DIR can only route an IPv6 tunnel from a single internal IP. So no 2 PC's on the LAN can access IPv6 websites through a tunnel. The router maps the protocol 41 (internet sessions) to the tunnel. Will future firmware be able to route more internal LAN ip's to an IPv6 tunnel address?

Can you say more about this?  I'm looking forward to learning more about IPv6.

[EddieZ]

Sure.

My ISP has been offering an IPv6 tunnel for a long time now. I finally succeeded in getting IPv6 connectivity through the tunnel working. The direct encapsulation of IPv6 datagrams within IPv4 packets is indicated by IP protocol number 41 (Vista uses Teredo by default).
Tunnel endpoints are determined by using a well-known IPv4 anycast address on the remote side, and embedding IPv4 address information within IPv6 addresses on the local side.

On every client you can do this, using the static LAN address (192.168.x.x). When one of the clients is connected to an external IPv6 site, you can notice a line in the router internet session log:

Local                   NAT                      Internet                   Protocol  State    Dir    Prio   Time out
192.168.0.2          192.168.1.64          194.109.5.241           41           -        Out   32     44             

BUT... if you have configured more clients for IPv6 tunneling (which IPv6 allows simply by upping the sequence number of the IPv6 address), you cannot connect to an IPv6 site from both clients.
Looking at the general log I assume the DIR655 only allows one protocol 41 to be passed through at the time, set to 1 specific internal IP. Why? Because the log will tell you that there is already a connection made to that endpoint (my 655 firewall is already set to the least possible impact).

So I am wondering if future firmware will support multiple encapsulation, from multiple clients/local IP's that is. This will IPv6 enable all machines at home, now there's only one capable (His Master's Machine  )

Funchords,
If your ISP does not support IPv6 tunneling, you can have a look here: http://www.sixxs.net/
This is one of the many 'tunnel brokers' which offer you an IPv6 endpoint to get IPv6 connected.
IPv6 is installed by default in Vista, XP needs some more steps to get IPv6 ready.

More info on IPv6 and Vista/Windows: http://en.wikipedia.org/wiki/IPv6

[Lycan]

I'm still waiting on that new one

They pulled it and are testing a newer build. I'll keep you posted via PM.

[EddieZ]

They pulled it and are testing a newer build. I'll keep you posted via PM.

OK. No rush. thx

[lotacus]

How did you get it setup to use IPv6? Did you let Windows autoassign the ipv6 address or did you plug something in manually? And was there something specific needed to be done (other that "support" ipv6) on the ISP side?

[EddieZ]

When using a IPv6 tunnel (if your ISP is not fully IPv6 compliant) you need to configure/add your IPv6 tunnel manually with the 'NETSH' command (Vista).

[lotacus]

Ok, i'll google that up because I dont want to hounder you on how you did it. I just left everything as auto, as if I were establishing an ipv4 connection.

Be nice to see what the routers entries were for it's routing table, I mean, just to verify that the darn thing is actually compliant with ipv6 tunnling. Looking at some other competitor products, and of course mid-range business switches, it explicitly states and shows IPv6 status and options.

[EddieZ]

Ok, i'll google that up because I dont want to hounder you on how you did it. I just left everything as auto, as if I were establishing an ipv4 connection.

Be nice to see what the routers entries were for it's routing table, I mean, just to verify that the darn thing is actually compliant with ipv6 tunnling. Looking at some other competitor products, and of course mid-range business switches, it explicitly states and shows IPv6 status and options.

For tunneling you don't use the GUI for configuration.

This is my script used:

netsh interface ipv6 add v6v4tunnel IP6Tunnel 192.168.0.2 194.109.x.xxx
; create tunnel from internal IP to ISP tunnel address
netsh interface ipv6 add address IP6Tunnel 2001:xxx:10:xxx::4
; link IPv6 IP to created tunnel
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:xxx:10:xxx::1
; add route from local tunnel address to endpoint
[/unquote]

[lotacus]

The 194.109.x.xxx is the isp's ipv4 address or your dynamic IP address that your creating the tunnel for?
and the IPv6 address you have in there i'm guessing is a static address your giving your interface. the xxx of course being variables or whatever. I think i need to contact the provider to first see if they support ipv6 which I know's teir one won't have a clue about, and find out from them what their endpoint address is.

edit: ok. found a website that's cut and dry about it. looks like i was partially? right.
http://www.join.uni-muenster.de/Dokumente/Howtos/Howto_IPv6-in-IPv4-Tunnel.php?lang=en#Windows

I need to find the host address which is going to be the isp.. by any chance, though, that address you used, woudln't happen to be your isp's gateway address would it?

[EddieZ]

The 194.109.x.xxx is the isp's ipv4 address or your dynamic IP address that your creating the tunnel for?
and the IPv6 address you have in there i'm guessing is a static address your giving your interface. the xxx of course being variables or whatever. I think i need to contact the provider to first see if they support ipv6 which I know's teir one won't have a clue about, and find out from them what their endpoint address is.

edit: ok. found a website that's cut and dry about it. looks like i was partially? right.
http://www.join.uni-muenster.de/Dokumente/Howtos/Howto_IPv6-in-IPv4-Tunnel.php?lang=en#Windows

I need to find the host address which is going to be the isp.. by any chance, though, that address you used, woudln't happen to be your isp's gateway address would it?

194.109.x.xxx =  ISP IPv6 endpoint

Not a lot ISP's support this tunneling, but you can always use a third party provider.