Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I administrate the network for a small organisation. Having only experience with IPv4, I'm unsure of how to best approach IPv6.

Existing IPv4 setup

We have 13 public IPv4 addresses which are all NAT'ed to internal RFC 1918 addresses (one mapping one-to-many for users, the rest mapping one-to-one for servers). All outgoing traffic goes our ISP's (single) upstream gateway. Our own router runs Linux.

In beautiful ASCII art, the network looks akin to this:

client     <- LAN ->              router              <- WAN ->  upstream
10.0.0.x             10.0.0.1   <- NAT ->  192.0.2.2             192.0.2.1

IPv6 setup

Of course, with IPv6, there is no need for NAT, since we have been allocated four /64 networks (let's say "9:9:9:0::/62"), of which one contains the upstream router. What's the norm for a similar IPv6 network?

A) Possible IPv6 network layout:

client     <- LAN ->              router              <- WAN ->  upstream
9:9:9:1::x           9:9:9:1::1           9:9:9:0::2             9:9:9:0::1

The question is then, how to get the upstream gateway to route packets through our router. With NAT and IPv4, it was simple: our router owned the addresses and responded to ARP requests for them. But now, the upstream gateway expects to find the LAN hosts on its own subnet, and fails.

1) I've looked into NDP proxying (the IPv6 version of ARP proxying), to let the router advertise all the addresses in 9:9:9:1/64. However, Linux, at least, seems to require a separate Netfilter entry per IP-address, which is of course entirely impossible with IPv6. Am I missing something?

2) It seems it should be possible to use NDP router advertisement to advertise our router as the "downstream gateway" for 9:9:9:1::/64. Can't get it to work, though. Perhaps our ISP ignores the router advertisement?

3) Do we need to ask our ISP to manually configure their upstream gateway to use our router? Seems weird it should be necessary under IPv6 and not under IPv4.

share|improve this question
add comment

1 Answer

up vote 2 down vote accepted

The upstream router should not assume the full 9:9:9:0/62 is on it's local interface, it should be programmed with your router's IP and the len of the intermediate network's prefix. Their router needs to be programmed basically just like yours.

(note that it is not necessary for the WAN network to use a subset of the 9:9:9:0/62 network you've been assigned; your ISP may assign a special /126 or /127 network to this link, the details vary by ISP)

Your ISPs upstream router always has to be programmed, IPv4 or IPv6. The "problem" is that most IPv4 deployments only have the perimeter network, where most IPv6 networks will be fully (correctly) routed.

share|improve this answer
    
Sounds reasonable. I take it NDP router advertisments doesn't solve this problem, and I'll have to call our ISP. –  Søren Løvborg May 26 '11 at 18:41
    
Typically you have to call your ISP. –  Chris S May 26 '11 at 18:49
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.