Geoff Steckel [[email protected]] wrote: > > I'm using sixxx.net as an IPv6 tunnel gateway. > They gave me 2001:xxxx:xxxx:0111::0002 as my tunnel endpoint and > 2001:xxxx:xxxx:0111::1 as their end and router address. > They gave me 2001:xxxx:xxxx:8111::/64 for my address space. > Note that the tunnel endpoint addresses are globally routeable. > > The desired behavior is to partition the network space > inside the machine into the gateway section and the > rest of the machine >> as if they were connected by > a pair of interfaces and a cable << where the interfaces > had addresses in 2001...8111 so that locally generated > packets would go out with that source address. >
If the tunnel endpoint x:0111::0002 is globally routeable, why do you care about the machine's own traffic not appearing from that address? None the less, if you must have traffic appear from x:8111::/64, can't you just use that on your gif interface? As gif is a point-to- point interface, there is no need for both participants to be within the same subnet. Of course, if you do this, you can't then apply the x:8111::/64 address to your ethernet interface facing your LAN, which is where it was meant to go, and why it all works this way anyways. If you really must have both x:8111::/64 on the LAN and on the gif interface, you could specify a /128 address for the gif interface and only use one of your x:8111::/64 addresses away from your LAN interface. Thre is no ARP so even if the remote router knows your gif interface as x:0111::0002 and routes to it, you can still use whatever address you want. But I don't really understand why you would want to do this, unless this tunnel router is the only machine you care to IPv6 on. Chris
