Have you added the line: iptables -A INPUT -i ppp0 -p udp --dport 139 -j DROP
to your iptables script. Dave. On Sun, 27 Jan 2002 13:42:41 -0500 daRcmaTTeR <[EMAIL PROTECTED]> wrote: > On Fri, 25 Jan 2002 07:26:23 -0700 > Lee Roberts <[EMAIL PROTECTED]> studiouisly spake these words to ponder: > > > I made the statement that none of my UDP ports are blocked. Most are > > showing closed but there are a couple showing open. I would have expected > > that the default policy would be DENY but that doesn't appear to be the > > case. I'm trying to learn the details about creating iptables so that I > > can resolve this issue. Also, I am allowing access to TCP port 22 (using > > Bastille) but I can't seem to connect to it even though a port scan shows > > it open (just another problem with Bastille). > > > > Like I previously stated, it's a good thing I don't have anything on the > > Linux box that needs to be secured at this time. :-D > > > > > > > > I can relate to the a UDP port needing to be closed, and not being able to > get it done. At the moment I'd love to get port 139 closed to the outside > interface, but no matter what it's just not working out that way. Prolly > something simple that I'm missing. > > As for your port 22 if you've got Portsentry running it's very likely that > "it" detected your connection attemtp and has done it's thing in blocking > access to that port. That is a very common occurance. Since you can't > connect even though a port scan shows it open I'm willing to bet that it's > cause Portsentry is blocking access. > > -- > daRcmaTTeR > > windows = "where do you want to go today" > Mac = "go where you want, do what you want today" > MDK-linux = " been there, done that, got the tee shirt, why do you ask?" > > Registered Mandrake Linux User # 186492 > > >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
