read hang on datagram socket

[Kurt Miller]

On Friday 27 January 2006 5:40 am, Fredrik Lindberg wrote:
> Kurt Miller wrote:
> > netstat output when stopping the program at the sendto call on 5.4
> > looks like this:
> > udp4       0      0  localhost.55513        172.16.1.36.52099
> > 
> > on 6.0:
> > udp4       0      0  172.16.1.37.53952      172.16.1.37.62241
> > 
> > Doesn't the above output indicate a problem with how datagram
> > sockets are bound to INADDR_ANY? 
> > 
> > Perhaps its related to my configuration. Can anyone else with a
> > 5.4-release system try the program to see if it works for them?
> > 
> 
> It works on a 5.4-RELEASE-p5 system.
> fli> ./test
> no hang
> 
> fli> ifconfig
> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>          options=b<RXCSUM,TXCSUM,VLAN_MTU>
>          inet 212.XX.XX.XX netmask 0xfffffff8 broadcast 212.XX.XX.XX
>          inet6 fe80::240:d0ff:fe43:b964%em0 prefixlen 64 scopeid 0x1
>          ether 00:40:d0:43:b9:64
>          media: Ethernet autoselect (100baseTX <full-duplex>)
>          status: active
> em1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
>          options=b<RXCSUM,TXCSUM,VLAN_MTU>
>          ether 00:40:d0:43:b9:65
>          media: Ethernet autoselect
>          status: no carrier
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
>          inet 127.0.0.1 netmask 0xff000000
>          inet6 ::1 prefixlen 128
>          inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
> 
> 
> Stopping it before sendto() gives
> udp4       0      0  212.XX.XX.XX.54074      212.XX.XX.XX.56604
> 

Thanks for trying it out. I updated my kernel to p10 and the problem
persists for me. I guess that makes the issue a configuration issue
or a possibly a lnc driver issue.

At the moment I can't think of anything in my configuration that is
different for the 5-4 install. I'll work on trying a different nic
next.

-Kurt