* Stuart Henderson (s...@spacehopper.org) wrote: > On 2009-10-18, Mats Erik Andersson <ynglinga...@yahoo.se> wrote: > > I face a tricky problem when OpenBSD 4.4 initiates interfaces > > with ipv6 addresses. My setting is a router supposed to route > > ipv6 traffic __without__ tunneling: > > > > rl0: exterior interface with static stateful ipv6-adress > > > > fxp0: first interior interface with static, stateful ipv6-address > > xl0: second interior interface with static, stateful ipv6-address. > > > > They are all assigned a static inet6 alias in their hostname.if files, > > the addresses being assign from my ipv6 net of length 64. > > you're putting addresses from one single subnet onto multiple interfaces. > just as with ipv4, this is a problem. > > ipv6 is designed so that subnets are /64. > if you're running multiple v6 subnets you should have more than a /64. > > your provider /should/ (but might not) accommodate this request and > give you a /48 or /56 or something.. > > if this is really not possible, you will be in for a messy setup, > probably including bridging. I'd go for a tunnel to a saner provider > rather than do that...
Yes. HE probably do a similar setup as Sixxs where you first are allocated a /64 which is for the tunnel only. When it is up and running you can request a /48 which you use at your site. (with /64s as internal subnets) In the case of Sixxs they also block all addresses from your tunnel /64 except for your tunnel endpoint (::2) so the rest of the addresses can not be used, this might also be the case for HE. Cheers, /J
