Perfect! According to grc I am now very secure (for a 'windows' machine this is very rare, according to his site hehe).
However, in order to get it to work I had to also define the PUBLIC services to allow 138 and 139 ports. Strange, although as I say, grc says it's in stealth mode (139 that is) so I guess it's fine, and it didn't work without it so... It said in the comments within bastille-firewall.cfg to also include it in PUBLIC so I guess it's ok. TCP_PUBLIC_SERVICES="138 139" TCP_INTERNAL_SERVICES="138 139" Derek you're a gent, cheers. Neil > -----Original Message----- > From: Derek Jennings [mailto:[EMAIL PROTECTED]] > Sent: 17 December 2001 11:34 > To: [EMAIL PROTECTED]; Linux Newbie List > Subject: Re: [newbie] Problem with bastille and samba > > > How about this > http://www.mandrakeforum.org/article.php?sid=1467&mode=thread&; > order=0&thold=0 > > You can edit the firewall setup tables and configure it as > you please. Derek > > BTW: Samba needs ports 138 and 139 open if I remember correctly. > > > > On Monday 17 December 2001 11:07, Neil R Porter wrote: > > Hi all > > > > I've used the tiny firewall configuration tool within the control > > centre to configure bastille and it's v v v nicely setup > according to > > http://grc.com however, it stops my samba shares from > working!? How > > can I use this setup but modify the conf file slightly to > allow samba > > shares to work on my local network. > > > > Please I don't want to use yet another firewall piece of > > software/setup... This is find apart from this one aspect. > > > > Any info on this would be much appreciated and rewarded > with lots of > > liquid refreshment!!! > > > > Neil >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
