Thanks Paul. Sorry for the confusion, I'd like to have only IPv6 traffic on my LAN and still be able to access IPv4 sites. I think i'll just stick to using sixx for now. Thanks again Barry
On 19/03/2008, Paul de Weerd <[EMAIL PROTECTED]> wrote: > > On Wed, Mar 19, 2008 at 01:33:18PM +0000, Barry Commander wrote: > | Hi guys > | I've found it very easy to get all the machines on my LAN speaking IPv6 > but > | would like them now > | to be able to access the internet using IPv6 until they reach my router, > | where it converts to IPv4 > | and relays the data to the internet, converting back to IPv6 on the > return > | route. > > > Ehm, what exactly do you mean with "convert" ? > > If you're doing tcp, you may want to have a look at faithd(8). Another > solution may be application level proxies or gateways. For name > resolution, you can set up BIND as a caching nameserver on your router > to listen on your v6 interfaces and queries the internet over v4 > (possibly also v6, with a tunnel to SixXS or someplace else). For web > you'll have to find a v6-capable proxy (I know squid isn't one). Maybe > Apache 2's mod_proxy does it (or Apache 1.3 + the IPv6 patches (see > mini.vnode.ch)). > > > | Is this possible? Where would I find the information required to set > this > | up? > > > It depends : what do you mean with 'convert' and what exactly do you > want your systems behind your router to be able to do ? > > Without much further details, faithd(8) is the best answer I can give > you. I don't know how workable it is, but you can find out yourself. > > Cheers, > > Paul 'WEiRD' de Weerd > > > -- > >++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+ > +++++++++++>-]<.>++[<------------>-]<+.--------------.[-] > http://www.weirdnet.nl/
