[22113] in Kerberos
Re: Kereros and Linux 2.6
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Mon Aug 2 14:58:17 2004
In-Reply-To: <200408012250.08652.dlucio@okay.com.mx>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C0DE76E2-E4B5-11D8-861D-000A95909EE2@mit.edu>
Content-Transfer-Encoding: 7bit
From: Ken Raeburn <raeburn@mit.edu>
Date: Mon, 2 Aug 2004 11:57:08 -0700
To: Luis Daniel Lucio Quiroz <dlucio@okay.com.mx>
cc: kerberos@mit.edu
cc: Ken Raeburn <raeburn@mit.edu>
Errors-To: kerberos-bounces@mit.edu
Ah, here we are... for some reason, this message had "may be forged" in
the Received: line added by your ISP (I think it's usually caused by
your system's "HELO" name not matching the DNS name found by looking up
your address), which is one of the things that triggers message
moderation on this mailing list, whereas your earlier message did not
have that header. Anyways...
On Aug 1, 2004, at 20:50, Luis Daniel Lucio Quiroz wrote:
> Helo,
>
> I new on kerberos and whilel I was setting it up I realize that
> kerberso 5
> does not support IPv6 when trying to bind port 88.
>
> ug 02 00:57:22 tao.linuxchange.com krb5kdc[10409](info): setting up
> network...
> Aug 02 00:57:22 tao.linuxchange.com krb5kdc[10409](info): skipping
> unrecognized local address family 17
> Aug 02 00:57:22 tao.linuxchange.com krb5kdc[10409](info): skipping
> unrecognized local address family 17
Address family 17 is "packet family" according to the comments on my
Linux system. So this is nothing to worry about.
> Aug 02 00:57:22 tao.linuxchange.com krb5kdc[10409](info): listening on
> fd 6:
> udp 192.168.3.1.88
> Aug 02 00:57:22 tao.linuxchange.com krb5kdc[10409](info): listening on
> fd 7:
> udp 201.129.237.114.88
> Aug 02 00:57:22 tao.linuxchange.com krb5kdc[10409](info): listening on
> fd 8:
> udp 192.168.3.6.88
That part looks good...
> krb5kdc: No such device - Cannot bind server socket to port 88 address
> fe80::5054:5ff:fef3:34fe%253
This, I haven't seen before. "No such device" from bind() is a new one
on me. I'll have to look into it a little. The "Cannot bind server
socket" message is generated in only one place, where bind() fails on a
socket already created. Obviously your system supports IPv6 sockets.
What does "ifconfig" show? Is there anything weird going on, like the
IPv6 address is on an interface that is down at the time?
Ken
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
