Re: solaris rshd question
From: David Mathog (mathog_at_caltech.edu)
Date: 03/22/05
- Previous message: Richard B. Gilbert: "Re: Sun Enterprise 3500 + internal discs"
- In reply to: Neil W Rickert: "Re: solaris rshd question"
- Next in thread: Barry Margolin: "Re: solaris rshd question"
- Reply: Barry Margolin: "Re: solaris rshd question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 21 Mar 2005 16:05:00 -0800
Neil W Rickert wrote:
> David Mathog <mathog@caltech.edu> writes:
>
>>That last packet is the problem. Neither 856 on the Sun side nor 1021
>>on the linux side have been used previously _from the linux side_ so
>>the linux firewall blocks that packet from the sun and that's all she
>>wrote.
>
>
> rsh opens a secondary connection for diagnostic output (stderr). You
> are seeing the first step in setting up that secondary connection.
>
Hmm. Yeah, I see it now in "man in.rshd" on the Solaris machine.
The trick as far as the firewall is concerned is that
rsh will have picked the second port number out of thin air
and sent it to the Solaris machine - without first telling
the firewall to accept a return connection on it. The port
numbers on the rsh side aren't fixed either. Tricky.
Has anybody ever solved this before? It looks like it might
be necessary to modify rsh so that it can tell the firewall
to open the second port.
Thanks,
David Mathog
mathog@caltech.edu
- Previous message: Richard B. Gilbert: "Re: Sun Enterprise 3500 + internal discs"
- In reply to: Neil W Rickert: "Re: solaris rshd question"
- Next in thread: Barry Margolin: "Re: solaris rshd question"
- Reply: Barry Margolin: "Re: solaris rshd question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|