NetBSD Problem Report #43708

From  Fri Aug  6 19:32:33 2010
Return-Path: <>
Received: from ( [])
	by (Postfix) with ESMTP id A988963BB83
	for <>; Fri,  6 Aug 2010 19:32:33 +0000 (UTC)
Message-Id: <>
Date: Fri,  6 Aug 2010 19:32:33 +0000 (UTC)
Subject: multicast binding issues
X-Send-Pr-Version: 3.95

>Number:         43708
>Category:       kern
>Synopsis:       multicast binding issues
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Aug 06 19:35:00 +0000 2010
>Originator:     Jeremy C. Reed
>Release:        NetBSD 5.1_RC1


System: NetBSD 5.1_RC1 NetBSD 5.1_RC1 (NBFTP) #7: Tue Apr 27 20:36:28 UTC 2010 amd64
Architecture: x86_64
Machine: amd64
1. a TCP socket allows it to be bound to a multicast address (may
not necessarily be "wrong" in terms of posix or API standard (which
I don't know), but at least it doesn't make sense)

2. inconsistency on whether to allow multicast binding for AF_INET
and AF_INET6 sockets

bind ffff:ffff:: probably should fail but it doesn't on 5.0 and 5.1.

This problem doesn't exist on 5.99.33 so is fixed somewhere.

bind probably should fail, but it does not (maybe
tcp/v4 and tcp/v6 use different logic).

I just noticed because some unittests I use for testing
invalid addresses were not working.

(Jinmei Tatuya helped me with troubleshooting this and description.)



NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD:,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.