Please, Urgent: Need ideas/help to solve PR bin/51586

[LarsKöller]

----------

In reply to Ian Freislich who wrote:
 
> Lars wrote:

> Interesting.  I setup rshd and inet exactly like you did and ran
> your test script and it broke in almost exactly the same way it did
> for you:

Fine, that are good news ;-)

> while true
> do
> 	/usr/bin/rsh brane -l ianf pwd; ret=$?
> 	if [ "$ret" != "0" ]
> 	then
> 		echo "Return Code: $ret"
> 		break
> 	fi
> done
> 
> Loops several hundred times and the immediately prints:
> 
> /usr/home/ianf
> /usr/home/ianf
> /usr/home/ianf
> select: protocol failure in circuit setup
> Return Code: 1
> 
> At this point on the server 'brane' I get the following in /var/log/messages:
> May  8 14:23:10 brane rshd[16886]: can't get stderr port: Can't assign requested address
> 
> This message is logged by rshd when it is unable to open the
> connection for stderr back to the originating rsh client.  Have you
> turned on net.inet.tcp.blackhole=2 which would result in ICMP port

No.

> unreachable messages not being sent? What is the output of 'netstat

73660 : netstat -anf inet |grep -v TIME_WAIT 
Active Internet connections (including servers)
Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)
tcp4       0      0  129.70.4.47.623        129.70.4.48.927        SYN_SENT
tcp4       0      0  129.70.4.47.514        129.70.4.48.928        ESTABLISHED
tcp4       0      0  129.70.4.47.6100       129.70.4.47.4755       ESTABLISHED
tcp4       0      0  129.70.4.47.4755       129.70.4.47.6100       ESTABLISHED
tcp4       0      0  129.70.4.47.6100       129.70.4.47.4628       ESTABLISHED
tcp4       0      0  129.70.4.47.4628       129.70.4.47.6100       ESTABLISHED
tcp4       0     32  129.70.4.47.6100       129.70.4.47.4627       ESTABLISHED
tcp4       0      0  129.70.4.47.4627       129.70.4.47.6100       ESTABLISHED
tcp4       0      0  *.6100                 *.*                    LISTEN
tcp4       0      0  129.70.4.47.22         129.70.202.15.34465    ESTABLISHED
tcp4       0      0  *.587                  *.*                    LISTEN
tcp4       0      0  *.25                   *.*                    LISTEN
tcp4       0      0  *.514                  *.*                    LISTEN
tcp4       0      0  *.22                   *.*                    LISTEN
tcp4       0      0  *.515                  *.*                    LISTEN
udp4       0      0  127.0.0.1.123          *.*                    
udp4       0      0  129.70.4.47.123        *.*                    
udp4       0      0  *.123                  *.*                    
udp4       0      0  *.514                  *.*                    
udp4       0      0  129.70.4.47.1019       129.70.4.48.2049       


> -anf inet |grep -v TIME_WAIT' on machine2 after you get the timeout
> connecting to machine2?  Is the tcp *.514 LISTEN line missing after

No, as you can see above. It's possibe to connect from a third machine 
to machine2 during the timeout/hang.

> you get the timeout.  What do you get in your messages file on
> machine2 (the one running the rsh server)?  I suspect that you're

 rshd[83865]: connect second port 927: Operation timed out

> not getting ICMP port unreachable after inetd silently terminated
> the shell service because of rshd's exit code so your connection
> timed out.
> 
> -snip-
>.......
> -snip-
>
> That's not a problem because I believe the problem to be in rshd
> and most likely in libc in rresvport_af(3).

Best regards

Lars

-- 
E-Mail: Lars.Koeller at Uni-Bielefeld.DE        \  Lars Köller
            lkoeller at FreeBSD.org              \  CC University of
PGP: http://www.uk.pgp.net/pgpnet/wwwkeys.html \  Bielefeld, Germany 
     Key-ID: A430D499                           \  Tel: +49 521 106 4964
----------- FreeBSD, what else? ---- http://www.freebsd.org -------------