Hi All,

Currently in the datacentre that houses our kit, we are running BGP on a CCR1009-7G-1C-1S+ and at my residence I am using a RB2011UiAS-2HnD-IN (with a static IP).

At home I am on a 100/40 NBN HFC service with a true static IPv4 address, not a sticky DHCP address. I have tried many times to configure a 6to4 tunnel between the two routers, however I am having issues. We have a /32 IPv6 that has been delegated to us from APNIC and that we are announcing via our BGP sessions, and I would like to route (ideally) a /64 prefix over the tunnel to my home router.

What would be the best way to achieve the above? I am at a loss, and not sure what to do.

Regards,
Christopher Hawker

You could be getting hung up at various points. To start off, remember no NAT in IPv6. (Well, at least in RouterOS)

1. You need IPv6 addressing on both sides tunnel. This can be link-local addressing but it may be easier / clearer to assign global unicast space. A /126 is fine but no one would be mad at you if you used a /64.
2. You need a route on the source of the IPv6 (your office) that points all traffic destined for the network you will use on your LAN to the IPv6 address of the home side of the tunnel. If you chose to use link-local addressing make sure the route reflects that.
3. You then assign the IPv6 addresses you allocated for your home to the LAN interfaces in /64 chunks.
4. Create a default route on the home router to the IPv6 address of your office router. Again, remember if you used link-local addresses on the tunnel to tell route which interface to use.

All in all, I highly recommend using a /126 carved out from a /64 you divide up into the point to point links you may need at the office and a separate network to assign to your home. This can be a single /64 or a larger subnet to accomodate more networks. Maybe a /60 or /56, it's always cleanest to subnet on nibble boundaries in IPv6.

You could be getting hung up at various points. To start off, remember no NAT in IPv6. (Well, at least in RouterOS)

1. You need IPv6 addressing on both sides tunnel. This can be link-local addressing but it may be easier / clearer to assign global unicast space. A /126 is fine but no one would be mad at you if you used a /64.
2. You need a route on the source of the IPv6 (your office) that points all traffic destined for the network you will use on your LAN to the IPv6 address of the home side of the tunnel. If you chose to use link-local addressing make sure the route reflects that.
3. You then assign the IPv6 addresses you allocated for your home to the LAN interfaces in /64 chunks.
4. Create a default route on the home router to the IPv6 address of your office router. Again, remember if you used link-local addresses on the tunnel to tell route which interface to use.

All in all, I highly recommend using a /126 carved out from a /64 you divide up into the point to point links you may need at the office and a separate network to assign to your home. This can be a single /64 or a larger subnet to accomodate more networks. Maybe a /60 or /56, it's always cleanest to subnet on nibble boundaries in IPv6.

Thanks idlemind,

I used fc00::1 and fc00:2/126 for an EoIP tunnel and this has worked great for me. Thanks!