Complete.Org: Mailing Lists: Archives: gopher: January 2009:
[gopher] Re: gopher and IPv6
Home

[gopher] Re: gopher and IPv6

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: gopher and IPv6
From: usenet@xxxxxxxxxx
Date: Sun, 18 Jan 2009 16:49:40 +0100
Reply-to: gopher@xxxxxxxxxxxx

Am Sonntag 18 Januar 2009 12:52:00 schrieb Jeroen Schot:
> On Jan 17, 2009, at 11:34 PM, Cameron Kaiser wrote:
> >>>> after some tries to enable public access to my home gopher reliably
> >>>> (read: without NAT and other evil stuff), i'd like to set up an
> >>>> IPv6
> >>>> gopher. But: i haven't yet managed to have any gopher daemon bind
> >>>> to an
> >>>> IPv6 port yet. What i tried so far is: GoFish and pygopherd.
> >>>> Anyone did this before? Or is there a gopher server that runs from
> >>>> xinetd? Have until now only tried standalone servers (the two named
> >>>> above).
> >>>
> >>> bucktooth will happily run in either environment. I haven't really
> >>> tested
> >>> it in IPv6 however (grumbles at upstream).
> >>
> >> Well, as far as i can tell right now, bucktooth happily serves
> >> gopher over
> >> IPv6 both on IPv6-only machines as well as on dual-stack boxes.
> >> Configuration
> >> of xinetd is a tad, umm, unintuitive as i had to find out.
> >
> > Does it properly report source addresses in the log file? I am
> > encouraged
> > to hear that it operates, however.
> >
> > Once my ISP offers me IPv6, I intend to do more testing with it.
>
> I run bucktooth (0.2.6) from openbsd-inetd dual-stack. I just checked,
> and ipv6 source addresses are *not* correct: It always shows 0.0.0.0.
> Maybe I have some time next week to see if I can solve this.
>
Same here with shown IPv6 adresses being 0.0.0.0. :-/

greets,
Florian



[Prev in Thread] Current Thread [Next in Thread]