Re: [CentOS] Understanding iptables

2008-07-13 Thread Spiro Harvey, Knossos Networks Ltd
Could you post /etc/sysconfig/iptables? /etc/sysconfig/iptables doesn't necessarily reflect what is running right now, and you can't include the counters with it. I'm not interested in the counters I want to see how the rules are I think he's trying to tell you that any changes made since

Re: [CentOS] Understanding iptables

2008-07-11 Thread William L. Maltby
On Thu, 2008-07-10 at 21:29 -0400, Filipe Brandenburger wrote: snip P.S.: Once again: although it's great that you are digging into the problem, using iptables, and learning a lot on the process, you should *REALLY* consider ditching rsh/rlogin and sticking to SSH. I would consider using

Re: [CentOS] Understanding iptables

2008-07-11 Thread William L. Maltby
On Fri, 2008-07-11 at 13:43 +1200, Spiro Harvey, Knossos Networks Ltd wrote: snip what are you talking about? I'm writing a Tor wrapper that funnels all my http requests thru gopher for extra security. It's called Gor. And I'm writing it in GW-BASIC! we don't need no steenkin new

Re: [CentOS] Understanding iptables

2008-07-11 Thread Rainer Duffner
Filipe Brandenburger schrieb: P.S.: Once again: although it's great that you are digging into the problem, using iptables, and learning a lot on the process, you should *REALLY* consider ditching rsh/rlogin and sticking to SSH. I would consider using rsh/rlogin instead of SSH today about the

Re: [CentOS] Understanding iptables

2008-07-11 Thread Robert Spangler
On Thursday 10 July 2008 22:49, Filipe Brandenburger wrote: Could you post /etc/sysconfig/iptables? /etc/sysconfig/iptables doesn't necessarily reflect what is running right now, and you can't include the counters with it. I'm not interested in the counters I want to see how the rules

[CentOS] Understanding iptables

2008-07-10 Thread MHR
In following up on the rsh problem I was having earlier, I decided to try out the suggestion Felipe sent about using system-config-securitylevel-tui to open up ports 513 and 514, but that doesn't seem to do the job, either. # iptables -L Chain INPUT (policy ACCEPT) target prot opt source

Re: [CentOS] Understanding iptables

2008-07-10 Thread Barry Brimer
Quoting MHR [EMAIL PROTECTED]: In following up on the rsh problem I was having earlier, I decided to try out the suggestion Felipe sent about using system-config-securitylevel-tui to open up ports 513 and 514, but that doesn't seem to do the job, either. I could be remembering this wrong,

Re: [CentOS] Understanding iptables

2008-07-10 Thread MHR
On Thu, Jul 10, 2008 at 3:17 PM, Barry Brimer [EMAIL PROTECTED] wrote: Quoting MHR [EMAIL PROTECTED]: In following up on the rsh problem I was having earlier, I decided to try out the suggestion Felipe sent about using system-config-securitylevel-tui to open up ports 513 and 514, but that

Re: [CentOS] Understanding iptables

2008-07-10 Thread William L. Maltby
On Thu, 2008-07-10 at 15:40 -0700, MHR wrote: On Thu, Jul 10, 2008 at 3:17 PM, Barry Brimer [EMAIL PROTECTED] wrote: Quoting MHR [EMAIL PROTECTED]: snip system-config-securitylevel-tui to open up ports 513 and 514, but that doesn't seem to do the job, either. I could be remembering

Re: [CentOS] Understanding iptables

2008-07-10 Thread Filipe Brandenburger
On Thu, Jul 10, 2008 at 6:08 PM, MHR [EMAIL PROTECTED] wrote: ACCEPT tcp -- anywhere anywherestate NEW tcp dpt:login ACCEPT tcp -- anywhere anywherestate NEW tcp dpt:shell It seems right to me... Try using iptables -vL, it will show

Re: [CentOS] Understanding iptables

2008-07-10 Thread Spiro Harvey, Knossos Networks Ltd
P.S.: Once again: although it's great that you are digging into the problem, using iptables, and learning a lot on the process, you should *REALLY* consider ditching rsh/rlogin and sticking to SSH. I would consider using rsh/rlogin instead of SSH today about the same as using gopher instead of

Re: [CentOS] Understanding iptables

2008-07-10 Thread MHR
On Thu, Jul 10, 2008 at 6:29 PM, Filipe Brandenburger [EMAIL PROTECTED] wrote: Try using iptables -vL, it will show you how many packets have matched that rule. Then try to rsh or rlogin and see if the numbers change. That should give you a clue to whether it's working or not. Before: 6

Re: [CentOS] Understanding iptables

2008-07-10 Thread MHR
On Thu, Jul 10, 2008 at 6:43 PM, Spiro Harvey, Knossos Networks Ltd [EMAIL PROTECTED] wrote: next you'll be telling me our internets shouldn't use tubes. You're up to tubes? Hippy freak! mhr ___ CentOS mailing list CentOS@centos.org

Re: [CentOS] Understanding iptables

2008-07-10 Thread Filipe Brandenburger
On Thu, Jul 10, 2008 at 9:53 PM, MHR [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] mrichter]$ rsh sushi ls sushi: Connection refused Are you sure the daemons are up and listening on those ports? What does netstat -ltp says on sushi? Filipe ___ CentOS

Re: [CentOS] Understanding iptables

2008-07-10 Thread Robert Spangler
On Thursday 10 July 2008 18:08, MHR wrote: In following up on the rsh problem I was having earlier, I decided to try out the suggestion Felipe sent about using system-config-securitylevel-tui to open up ports 513 and 514, but that doesn't seem to do the job, either. # iptables -L

Re: [CentOS] Understanding iptables

2008-07-10 Thread Filipe Brandenburger
On Thu, Jul 10, 2008 at 10:42 PM, Robert Spangler [EMAIL PROTECTED] wrote: Could you post /etc/sysconfig/iptables? /etc/sysconfig/iptables doesn't necessarily reflect what is running right now, and you can't include the counters with it. An acceptable compromise would be posting the output of