[NTLUG:Discuss] port 22 "filtered"

[Jack Snodgrass]

I'm almost positive that lokkit is just a front end to 
ipchains and iptables. 

/etc/rc.d/init.d/iptables stop 
/etc/rc.d/init.d/ipchains stop 

should disable any firewall stuff. 

iptables -L -n 
sould show you 
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

if you have all of your firewall stuff turned off. 

as for removing... you can try doing 
rpm -e lokkit 
and see if you can remove it. 
I'd do a 
rpm -e ipchains 
too since you should only need to use iptables with the 2.4 and 2.6
kernels anyway. 

jack


On Sat, 2004-03-13 at 03:06, terry wrote:
> terry wrote:
> > 
> > 
> > Cameron, Thomas wrote:
> > 
> >>> -----Original Message-----
> >>> From: discuss-bounces at ntlug.org [mailto:discuss-bounces at ntlug.org]On
> >>> Behalf Of terry
> >>> Sent: Friday, March 12, 2004 6:33 PM
> >>> To: NTLUG Discussion List
> >>> Subject: [NTLUG:Discuss] port 22 "filtered"
> >>>
> >>>
> >>> cannot ssh to a (Fedora core1) PC, even though sshd IS running on 
> >>> that machine, and 'ssh localhost' DOES work [on that target machine].
> >>>
> >>> nmap (from outside) reports port 22 is "filtered"
> >>> (I have to run nmap with -P0 option)
> >>> ie. nmap -P0 -p22  **.***.**.***
> >>> Port       State       Service
> >>> 22/tcp     filtered    ssh
> >>>
> >>> So, how do I un-filter port 22 ?
> >>
> >>
> >>
> >> You can either use
> >> iptables -l
> >> as described earlier or just do
> >> service iptables stop
> > 
> > 
> > Tried
> > service iptables stop
> > and no change.
> > 
> >>
> >> and then try it to see if it is a firewall rule.
> > 
> > 
> > Now that's a possibility, a very strong possibility, but don't know what 
> > to do about it.  Fedora ships with lokkit, which I used, and that's 
> > prolly what I did to block or filter this port. During an earlier 
> > session, I used lokkit, turned it on, as I wasn't sure if she had 
> > adequate protection from the outside or not.  Afterward I tried to 
> > unblock it, to turn firewall off, everything that made sense, then I 
> > uninstalled the package that apparently originally contained lokkit, 
> > redhat-config-securitylevel-???, rebooted  the system and still same 
> > symptoms.  I cannot seem to free up that port.  Cannot ping this machine 
> > either.  So... ???
> > 
> 
> This is interesting:
> On the  system in question rpm -qf `which lokkit`
> tells me that lokkit came from redhat-config-network-tui
> rpm -qf `which lokkit`
> redhat-config-securitylevel-tui-1.2.11-1
> 
> My RedHat 9.0 system claims that lokkit is a stand alone package:
> rpm -qf `which lokkit`
> lokkit-0.50-22
> 
> Although I don't know what version of lokkit comes in Fedora's 
> redhat-config-securitylevel-tui I assume it's newer, or at least somehow 
> different.  Not only do I not know what version it is, I don't seem to 
> know how to obtain such information.
> # lokkit --version
> --version: unknown option
> 
> Another interesting fact:
> Fedora's version of lokkit offers 2 options on first configuration screen:
>      Security Level: (*) Enabled ( ) Disabled
> 
> Whereas on my RedHat 9.0 machine, it offers 3 options:
>      Security Level: (*) High ( ) Medium ( ) No firewall
> 
> So there IS something different and I'm now thinking Fedora's version of 
> lokkit is broken.
> 
> I found lokkit-0.50-21.8.0.i386.rpm at 
> ftp://updates.redhat.com/8.0/en/os/i386
> and also have
> lokkit-0.50-22.i386.rpm
> on my RedHat 9.0 CD,
> so,... I'll see if
> rpm -Fvh  lokkit-0.50-21.8.0.i386.rpm
> or
> rpm -Fvh lokkit-0.50-22.i386.rpm
> will fix it.
> 
> This may be a bug?