• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

Sitecom WLR-6100 X6 N900 (firmware 2.4): compatible with HE?

Started by felker, April 15, 2013, 03:16:17 PM

Previous topic - Next topic

felker

Hi,

I have got a Sitecom WLR-6100 X6 N900. With firmware 2.4 (released 2013 April 9), there are a few IPv6 options:

- Static IPv6
- PPPoE
- Autoconfiguration
- 6RD

Is any of these compatible with HE?

I requested and got a HE tunnel, but I can't fill out those parameters in any of the Sitecom IPv6 options.

Tips very much appreciated.

Thanks

broquea

You'd need something along the lines of "6in4 Tunnel" or "IPv6 Tunnel" for a correct option.

felker

Quote from: broquea on April 15, 2013, 03:55:50 PM
You'd need something along the lines of "6in4 Tunnel" or "IPv6 Tunnel" for a correct option.


... which are not in the above list (right?), meaning I can't use the Sitecom X6 with HE ... ?

(Just checking)

kasperd

Quote from: broquea on April 15, 2013, 03:55:50 PMYou'd need something along the lines of "6in4 Tunnel" or "IPv6 Tunnel" for a correct option.
That is true, however 6rd and 6in4 are similar enough that multiple users have managed to get a tunnel working between HE and a router, which only supports 6rd.

If we get a list of the info provided on the tunnel info page and the fields the router expects to be filled in for 6rd operation, then I can probably explain how to format the info in a way, which the router will understand.

felker

OK. ASCII-dump is below. Screendump is here:

Help appreciated.



IPv6 Connection Type
Choose the IPv6 mode to be used by the router for the internet connection.

IPv6 Connection :    
6RD Configuration :      6RD DHCPv4 Option Manual Configuration
6RD IPv6 Prefix :     /
IPv4 Address :      Mask Length :
IPv6 Prefix Arrange :    
Tunnel Link-Local Address :     FE80::5380:90EA/64
6RD Border Relay IPv4 Address :    
Primary IPv6 DNS Address :    
Secondary IPv6 DNS Address :    
LAN IPv6 Address :     /64
LAN IPv6 Link-Local Address :     FE80::66D1:A3FF:FE03:8A01/64
Enable automatic IPv6 address assignment :    
Autoconfiguration Type :    
Router Advertisement Lifetime :      (minutes)

kasperd

There are two ways you can configure it. Option one doesn't respond to the pings HE sends to the client IPv6 address. Option two fixes that problem, but it is a bit of a hack.

Option 1:
6RD prefix you fill in with your routed prefix. Remember to change the /32 to /64.
IPv4 address should be filled in automatically by the router.
Mask length must be 32.
Border relay IPv4 address must be the IPv4 address of the tunnel server.
LAN IPv6 address can be any address in the routed prefix. Typical choices would be either prefix::1 or the MAC based link-local address, which in your case is prefix:66D1:A3FF:FE03:8A01.

Option 2:
6RD prefix you fill in with your tunnel prefix. Remember to change the /32 to /64.
IPv4 address should be filled in automatically by the router.
Mask length must be 32.
Border relay IPv4 address must be the IPv4 address of the tunnel server.
LAN IPv6 address must be the the client IPv6 address from the tunnel info page. That is the one of the form prefix::1

There are other options controlling how the router behaves on the LAN. Those don't depend on which of the above options you choose.
Primary DNS. You could use the anycast provided by HE: 2001:470:20::2
Secondary DNS: You could use one of Google's servers 2001:4860:4860::8888 or 2001:4860:4860::8844
The last three options in your screenshot control address assignment, the defaults look good, so I don't think you need to change that.

felker

Thank you for your reply.

When I try to change "6RD IPv6 Prefix :" to /64, the Sitecom gives an error popup saying "The range of Subnet Prefix Length is 1 ~ 63.", and refuses the /64.

So the /64 is not possible. Does this mean a blocking issue?

Screendump:

kasperd

Quote from: felker on April 17, 2013, 11:29:58 AMDoes this mean a blocking issue?
No, it is not a blocking issue. There is a way to get around that limitation. You just need to request a routed /48 for your tunnel and use that instead.

felker

Wow, after requesting the Routed /48: and filling it out .... it works!

http://test-ipv6.com says "Your IPv6 address on the public Internet appears to be 2001:470:7bbe:blablabla (HURRICANE - Hurricane Electric, Inc.)"

Thank you very much!

felker

Cool: Over IPv6 I get 34.1 MB/s, or 341 Mbps. Kudo's to HE Tunnelbroker and the Sitecom router for handling the IPv6 traffic at this great speed.



 ubuntu@ubuntu:~$ wget -6 http://ftp.belnet.be/ubuntu.com/ubuntu/releases/precise/ubuntu-12.04.2-desktop-i386.iso -O /dev/null
--2013-04-19 18:24:42--  http://ftp.belnet.be/ubuntu.com/ubuntu/releases/precise/ubuntu-12.04.2-desktop-i386.iso
Resolving ftp.belnet.be (ftp.belnet.be)... 2001:6a8:3c80:2::21
Connecting to ftp.belnet.be (ftp.belnet.be)|2001:6a8:3c80:2::21|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 726970368 (693M) [application/x-iso9660-image]
Saving to: '/dev/null'

39% [==============>                        ] 289,894,144 36.7MB/s  eta 13s    
79% [=============================>         ] 577,715,328 37.2MB/s  eta 5s    
100%[======================================>] 726,970,368 27.6MB/s   in 20s    

2013-04-19 18:25:02 (34.1 MB/s) - '/dev/null' saved [726970368/726970368]

ubuntu@ubuntu:~$