Date: Fri, 18 Feb 2000 00:03:57 -0500 From: "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com> To: Ian Edwards <ian@concerto.demon.co.uk> Cc: FreeBSD questions <freebsd-questions@FreeBSD.ORG> Subject: Re: IPFW rules for rsh ? Message-ID: <20000218000357.F53575@cc942873-a.ewndsr1.nj.home.com> In-Reply-To: <XFMail.000216160807.ian@concerto.demon.co.uk>; from ian@concerto.demon.co.uk on Wed, Feb 16, 2000 at 04:08:07PM -0000 References: <XFMail.000216160807.ian@concerto.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 16, 2000 at 04:08:07PM -0000, Ian Edwards wrote:
>
> Hello,
>
> can someone help me with the IPFW rules for allowing 'rsh' from
> my FreeBSD system (192.168.200.201) to another LAN (192.168.0.0) ?
>
> I have tried in /etc/rc.firewall, with net2="192.168.0.0"
> and mask="255.255.255.0" and ip="192.168.200.201"
>
> $fwcmd add pass tcp from ${ip} to ${net2}:${mask} 514
> $fwcmd add pass tcp from ${net2}:${mask} 514 to ${ip} setup
> $fwcmd add pass tcp from ${net2}:${mask} 514 to ${ip}
>
> 'rcp' works OK, 'rsh' just hangs.
How are you using 'rsh?' Like,
% rsh net2-host "echo TEST"
Or,
% rsh net2-host
Look again at rsh(1),
If no command is specified, you will be logged in on the remote host us-
ing rlogin(1).
And from /etc/services,
login 513/tcp #remote login a la telnet;
tcpdump(1) is your pal. Use it to check where the packets are really
going when you do something like that.
--
Crist J. Clark cjclark@home.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000218000357.F53575>