Date: Sat, 14 Dec 2002 14:57:54 +0900 From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp> To: "Jeff W. Boote" <boote@internet2.edu> Cc: freebsd-net@FreeBSD.ORG Subject: Re: IPv6 udp socket bind: EADDRNOTAVAIL? Message-ID: <y7vadj9gn19.wl@ocean.jinmei.org> In-Reply-To: <3DFA268D.A073F0F3@internet2.edu> References: <3DFA268D.A073F0F3@internet2.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> On Fri, 13 Dec 2002 11:27:25 -0700, >>>>> "Jeff W. Boote" <boote@internet2.edu> said: > Questions: > 1. The comment says broken. Anyone know why the comment says that? (The > IPv4 version of bind says the same thing...) I don't know...perhaps this comment was copied from the IPv4 code. > 2. This system is auto configuring this address... Is it possible that > I'm just having this problem because the system is reconfiguring the > address at this time? (I must admit that I have not looked at the auto > configuration stuff.) I don't think so. Even if the system is reconfiguring global addresses, it should have other stable addresses, such as link-local and loopback ones. So the address list starting at in6_ifaddr should rarely be empty. I suspect the EADDRNOTAVAIL error comes from a different part of the kernel (or the kernel has a serious bug). If you give us more information, we may be able to diagnose the problem. The information can include: - the result of ifconfig -a inet6 - the result of netstat -anl -f inet6 - the IPv6 address (and port) being bound in the error case - the (related part of the) source code of the daemon In any case, you should provide the FreeBSD version of your system. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?y7vadj9gn19.wl>