On Sat, Feb 13, 2010 at 12:15:55PM +0100, Michael Schwartzkopff wrote:
> > > > > Executing radtest <user> <pass> localhost 1 testing123
> > > > >
> > > > > gives the error:
> > > > >
> > > > > radclient: socket: cannot initialize udpfromto: Function not
> > > > > implemented
> > > > >
> > > > > this seems to be a IPv6 related issue sind radcleint apparently uses
> > > > > ::1 instead of 127.0.0.1
> > > > >
> > > > > For more details see:
> > > > > https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/430732
> > > >
> > > > Hm, I saw a similar report on the freeradius-users list recently...
> > > > When you do 'ping localhost', what comes up, the IPv6 address or the
> > > > IPv4 one?
> > >
> > > ping ONLY uses IPv4 DNS, ping6 is the tool using IPv6. So no problems
> > > pinging localhost.
> > >
> > > radclient first looks for the IPv6 address and only after that for IPv4.
> >
> > OK, let me rephrase. Does 'localhost' ever *resolve* into an IPv6 address?
> > What does 'ping6 localhost' produce?
>
> 1) "Ever": Yes. See /etc/hosts:
>
> 127.0.0.1 localhost
> ::1 localhost ip6-localhost ip6-loopback
OK. This is news to me. On my machines, localhost is only 127.0.0.1,
and only ip6-localhost is ::1. Maybe that's a newer default.
Cc:ing Alan (upstream) for reference - there have been two analogous reports
on freeradius-users about this - localhost gets resolved into an IPv6
address as well as IPv4, the stack prefers v6, and radclient barfs.
This setup has been in the wild for a while now, since the previous
two reports came in on 31 Jan 2009 and 4 Jul 2009, resp., and now here.
What's the best thing to do?
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100214175311.ga23...@orion.carnet.hr
