IPv6 setup problem

Hi,

since my ISP now provides IPv6 to my home, I am trying to setup IPv6 in my home network.

So far I got everything working on the RB2011 but my Windows 7 clients seem not to get any response from the outside world. I can e.g. ping the RB fe80::* address though. I can see outgoing and incoming traffic on my uplink interface using torch.

From the router I can successfully ping IPv6-only hosts like ipv6.google.com (without specifying any router interface).
The ping I try e.g. looks like this: /ping [:resolve ipv6.google.com]

I am not sure if this observation has something to do with my problem:
When I ping the fe80::* address of my cable modem, I don’t get any output at all and don’t see any output from any possible firewall debug output. This only works fine if I specify the interface like “/ping interface=internet fe80::" or "/ping fe80::%internet” where “internet” is my network interface to the cable modem.

Any ideas what I am missing? I am completely new to IPv6 so I probably lack some simple basic stuff somewhere.

Zap.

“fe80” is a “link-local” addresses, they are not routable. It’s similar to 169.254.. IPv4 addresses which is used if no dhcp detected.

So, don’t see at fe80 addresses, that exists even no IPv6 wan connectivity at all.

If you want to use your IPv6 connectivity you must set up prefix delegation to you local network. There are some various schemes of IPv6 deploying by ISP, so there is no single solution. In short, you need to have two /64 subnets, one for the external interface, the other for your intranet.

First you need to setup IPv6 firewall. I would also recommend learning some more about IPv6, before trying to set this up. It is quite easy to do, but you need to know what you are doing, and have a little bit of a plan.

  • Firewall
  • DHCPv6 client on ISP port. use peer dns and add default route
  • IPv6 Pool
  • ::1/64 ipv6 address on isp interface. from-pool set to above pool and advertise.

probably one or two other bits to get it going. there are tutorials on the wiki and also bits and pieces on the forum. i would recommend again having a nose around on the forum and wiki first.

hope this helps

tony shift key has broken arrrgh

Hi guys,

thanks for your replies. I did read quite alot about IPv6 and did the stuff Tony suggests.

I have my IPv6 firewall in place, DHCPv6 client on the ISP interface, DHCP pool and a ::1/64 advertised address on the router.
With these steps I got my router to talk IPv6 and now it’s able to ping IPv6 addresses and such.

What confuses me are these things:
The documentation of my FritzBox 6360 (cable modem) explains, that the box delegates a /62 prefix. With my ISP I only get a /62 on the modem so it delegates a /63 my RB2011, which sounds logical.
Where I really stumble is, that I don’t get how to split this delegated network into /64 pieces which I can use on my intranet interface.

Since everything can change at any time my ISP chooses to give me a new network (or IPv4 address), I am lost how to do this with IPv6.

I assume I miss some pretty basic understanding of routing in IPv6 but so far I did not find any usefull howto on that. :blush:

Maybe you can give me a hint in the right direction?

Zap.

actually IPv6 RFC suggests that network infrastructure devices does not require global ipv6 addresses and as such should only be used for management purposes. Only user hosts require global ipv6 addresses and all the routing (so that these end user hosts can get internet connectivity) can be done via link-local addresses (contrary to what LinFor suggested previously in this thread)

Just check what network addresses you get with your prefix and mask. But you should be definitely able set up address on local interface unless ISP gives address for use on your external interface.

After some more reading and searching, I think I can explain my problem in more detail.

The examples and howtos only show either a dhcp client or a dhcp server but not on a single router and not the way that the server depends on the client prefix. :frowning:

My problem is, that I need a DHCP client configuration which gets a prefix delegation from my cable modem and I have to use this prefix for my own DHCP server setup to delegate the network to my PCs.

Do I have to manually configure the DHCP server (which will fail as soon as I get a new network from my ISP) or is there some automated way to split the already delegated prefix into smaller subnetworks?

The plan for my network looks like this:

ISP --> FritzBox 6360      --> RB2011       --> /64 prefix 1 --> LAN1, Win 7 clients
        gets /62 prefix    gets /63 prefix  +-> /64 prefix 2 --> WLAN, mobile devices