Also, do note that this just means that this particular box has ipv6 connectivity. If you want to have clients at home behind this one, you should get another v6 network to use behind this gateway. And I agree with Adam, you got most of it correct.
I would add the route command to hostname.gif0 with the ! before so it is used only when gif0 is taken up. 2014-08-20 6:38 GMT+02:00 Adam Thompson <[email protected]>: > On 14-08-19 10:40 PM, Charles Musser wrote: > >> I'm experimenting with using IPv6 via a tunnel broker provided by an >> ISP. The tunnel works, but I want to confirm my understanding of the >> commands they gave me to set it up. These are the commands: >> >> ifconfig gif0 tunnel 50.1.94.112 72.52.104.74 >> ifconfig gif0 inet6 alias 2001:470:1f04:204::2 2001:470:1f04:204::1 >> prefixlen 128 >> route -n add -inet6 default 2001:470:1f04:204::1 >> [...] >> > > IIRC from my experimentation, you've got it exactly right. > Some tunnel brokers give you subnet masks that certain versions of OpenBSD > don't like - that turns out to not actually matter, just use whatever > ifconfig(8) want. Point in case: HE recommends using /64 for PtP links, > but OpenBSD 5.x requires /128. Since HE allocates an entire /64 per > tunnel, there is no danger in configuring it more narrowly on the client > end. > > The hostname.if(5) syntax that finally worked for me on 5.4-RELEASE was > (slightly anonymized) > >> description HE_TUNNEL_FREMONT >> tunnel 184.70.48.XXX >> dest 64.71.128.83 >> inet6 2001:470:XXXX:X::2 >> dest 2001:470:XXXX:X::1 prefixlen 128 >> > which perhaps adds some clarity, or perhaps confuses, depending on your > point of view. I can't remember whether (in the non-BGP case) I added the > route command as "!route -n add -inet6 default 2001:470:1f04:204::1" to the > hostname.gif0 file, or if I added it to /etc/mygate - one or the other > should work, anyway. > > -- > -Adam Thompson > [email protected] > > -- May the most significant bit of your life be positive.
