>Number:         2972
>Category:       kern
>Synopsis:       sin_zero section of sockaddr_any is compared in bind.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Nov 27 04:20:01 1996
>Last-Modified:
>Originator:     Jesus M. Gonzalez Barahona
>Organization:
Grupo de Sistemas y Comunicaciones,
Departamento de Informatica        | tel: +34 1 624 94 58
Universidad Carlos III de Madrid   | fax: +34 1 624 94 30
e-mail: jgb@gsyc.inf.uc3m.es       | www: http://ordago.gsyc.inf.uc3m.es/~jgb
>Release:        1.1 and 1.2
>Environment:
	
System: NetBSD hola.gsyc.inf.uc3m.es 1.1 NetBSD 1.1 (GSYC-2-PCVT-b) #0: Thu Apr 11 10:23:30 MET DST 1996 jgb@hola.gsyc.inf.uc3m.es:/disks/moriles.h/mix.netbsd.usr.src/sys/arch/i386/compile/GSYC-2-PCVT-b i386


>Description:
	As dicussed in tech-net, sin_zero field of sockaddr_in is
compared with the one of the active ifaces when binding, if specified
address is not INADDR_ANY. It have been made clear that this is not
a bug, but the documented behaviour of sin_zero. But it could
be changed to a more 'robust' behaviour.
>How-To-Repeat:
	Just bind an UDP socket specifying an address different of
INADDR_ANY, with something different from zeroes in sin_zero.
>Fix:
	Just make the comparation with ifaces only with respect to 
the host address, not to the full sockaddr_in.
>Audit-Trail:
>Unformatted: