[CentOS] rsh problems in CentOS 5.2 (was "cvs command failure on 5.2")

Mon Jul 7 23:01:51 UTC 2008
MHR <mhullrich at gmail.com>

On Mon, Jul 7, 2008 at 3:35 PM, nate <centos at linuxpowered.net> wrote:
>
> Is there a firewall on sushi? Run iptables -L -n on it, it seems like
> a firewall is blocking the connection.
>

Yes:

[root at sushi mrichter]# iptables -L -n
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
RH-Firewall-1-INPUT  all  --  0.0.0.0/0            0.0.0.0/0

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
RH-Firewall-1-INPUT  all  --  0.0.0.0/0            0.0.0.0/0

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain RH-Firewall-1-INPUT (2 references)
target     prot opt source               destination
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           icmp type 255
ACCEPT     esp  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     ah   --  0.0.0.0/0            0.0.0.0/0
ACCEPT     udp  --  0.0.0.0/0            224.0.0.251         udp dpt:5353
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           udp dpt:631
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:631
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state
RELATED,ESTABLISHED
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW
tcp dpt:22
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW
tcp dpt:23
REJECT     all  --  0.0.0.0/0            0.0.0.0/0
reject-with icmp-host-prohibited
[root at sushi mrichter]#

> If you don't have an explicit need for a firewall on sushi I'd suggest
> ensuring that iptables is not running /etc/init.d/iptables stop
>

I'll check on that....

> And verify the default settings of the firewall just incase it leaves them
> in a reject state with the iptables -L -n command above, e.g.
>
> # iptables -L -n
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
>
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
>

I'm not entirely sure what all this means - pls see above.  Is that
what happened?

mhr