IPv6 and SixXS (6to4)

RouterOS General
1

I’ve gone after this guide http://doc.thewan.net/wiki/index.php/IPv6#Mikrotik_RouterOS
But i can’t ping 2001:xxxx:xxxx:xxxx::1 (my IPv6 gateway)

[admin@RB333] > /interface 6to4 add mtu=1280 name=6to4-sixxs disabled=no local-address=
[admin@RB333] > /ipv6 address add interface=6to4-sixxs address=
[admin@RB333] > /ipv6 route add dst-address=2000::/3 gateway=::

Has anybody gotten SixXS and RouterOS to work together?

2

Here’s the article I wrote using the Hurricane Electric service.

http://wiki.mikrotik.com/wiki/Setting_up_an_IPv6_tunnel_via_a_tunnel_broker

I need to look at this again because my tunnel isn’t working at the moment.

Regards

Andrew

3

Hi Andrew

I have try’d your guide, but no luck :frowning:

/Ken

4

Ken

Had to rebuild my tunnel on the HE website. Working again now.

Are you pinging the remote gateway ipv6 address from the router or a PC?. Stick to the router at first, it’s simpler.

Otherwise, your config looks OK. Double check the values you’ve entered.

Regards

Andrew

5

I have another machine running on SixXS it can’t ping the IP setup in RouterOS.
And the Box with RouterOS can’t ping it’s GW but can ping it’s own IP…

Is there maybe some firewall rules that i need?
right now i have block’d ALL trafic to my main IPv4 where the IPv6 is routed to.

6

Ken

right now i have block’d ALL trafic to my main IPv4 where the IPv6 is routed to

But this is an ipv6 in ipv4 tunnel. You need to allow the tunnel traffic.

Regards

Andrew

7

How do i find and allow the traffic?

8

So I’ve tried this with my tunnel information and it doesn’t work. the thing that I don’t get is that a 6to4 interface is not what should be used, what should be used is something like a cisco ipv6ip tunnel which is not the same. So i don’t even know how yours worked to begin with.

9

You’re right, it’s not the same, it’s way cheaper than the Cisco. If your ISP doesn’t provide an ipv6 service then you need to tunnel ipv6 inside an ipv4 tunnel, which is what a 6to4 tunnel is. Mine’s working fine since I hit the rebuild tunnel button on the tunnel brokers web page.

Tunnel traffic is carried by IP protocol 41.

Regards

Andrew

10

Andrew, What do you have of firewall rules?

11

This in the output chain:

chain=output action=accept protocol=41

This in the input:

chain=input action=accept src-address=216.66.80.26 protocol=41

216.66.80.26 is the providers endpoint address.

Regards

Andrew

12

Here is the thing, i can’t find the protocol named 41…
I’ve got the IPv6 package installed.

13

You don’t need to find it. Just manually type it in the IPv4 firewall rule.

Regards

Andrew

14

\o/ it work’d… So thank you Andrew

But why has protocol 41 (RFC2893) not been added to Winbox…

15

i have an error while adding this command 209.197.5.66 is my tunnel broker ip please shed me a light what is wrong

thankyou

/ipv6 route add dst-address=2000::/3 gateway=::209.197.5.66
                           
failure: Invalid route configuration: Each link-local or IPv4-compatible nextho
p address must have interface index
16

You have to specify which interface to use:
for example:

/ipv6 route add dst-address=2000::/3 gateway=::209.197.5.66,ether1
17

Can someone please clear up this doc. What a mess.

http://wiki.mikrotik.com/wiki/Setting_up_an_IPv6_tunnel_via_a_tunnel_broker

THIS DOES NOT work on 5.14

/ipv6 route add dst-address=2000::/3 gateway=::216.66.80.26

THIS works on 5.14

/ipv6 route add dst-address=2000::/3 gateway=::209.197.5.66%sixbone