Date: Thu, 08 May 2003 16:48:24 +0200 From: Lars =?iso-8859-1?Q?K=F6ller?= <Lars.Koeller@Uni-Bielefeld.DE> To: Ian Freislich <ianf@za.uu.net> Cc: Lars =?iso-8859-1?Q?K=F6ller?= <Lars.Koeller@Uni-Bielefeld.DE> Subject: Re: Please, Urgent: Need ideas/help to solve PR bin/51586 Message-ID: <200305081448.h48EmO628174@rayadm.hrz.uni-bielefeld.de> In-Reply-To: Message from Ian Freislich <ianf@za.uu.net> "of Thu, 08 May 2003 15:39:08 %2B0200." <43122.1052401148@wcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
----------
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=3D$?
> if [ "$ret" !=3D "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/mes=
sages:
> 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=3D2 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_SE=
NT
tcp4 0 0 129.70.4.47.514 129.70.4.48.928 ESTABL=
ISHED
tcp4 0 0 129.70.4.47.6100 129.70.4.47.4755 ESTABL=
ISHED
tcp4 0 0 129.70.4.47.4755 129.70.4.47.6100 ESTABL=
ISHED
tcp4 0 0 129.70.4.47.6100 129.70.4.47.4628 ESTABL=
ISHED
tcp4 0 0 129.70.4.47.4628 129.70.4.47.6100 ESTABL=
ISHED
tcp4 0 32 129.70.4.47.6100 129.70.4.47.4627 ESTABL=
ISHED
tcp4 0 0 129.70.4.47.4627 129.70.4.47.6100 ESTABL=
ISHED
tcp4 0 0 *.6100 *.* LISTEN=
tcp4 0 0 129.70.4.47.22 129.70.202.15.34465 ESTABL=
ISHED
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@Uni-Bielefeld.DE \ Lars K=F6ller
lkoeller@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 -------------=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305081448.h48EmO628174>