On Friday 17 December 2004 12:09, Kaj Haulrich wrote:
When checking my ports at Shields Up (www.grc.com), my port 113
shows blocked. I would prefer stealthed.
Now, I know that somewhere in /etc/shorewall/foo it should be
possible to change REJECT to DROP, but I can't locate the entry
On Friday 17 December 2004 13:18, Derek Jennings wrote:
On Friday 17 December 2004 12:09, Kaj Haulrich wrote:
When checking my ports at Shields Up (www.grc.com), my port
113 shows blocked. I would prefer stealthed.
Now, I know that somewhere in /etc/shorewall/foo it should be
possible
Klemens Arro wrote:
whats with samba and shorewall? I cant use samba server or Smb4K (guess that
shorewall blocks it). When I take the whole firewall down Everything (no
firewall) then samba works perfectly, but then I can't share my ADSL
connection.
My /etc/shorewall/rules below, part relevant
On Friday 30 Apr 2004 07:35, Raffaele BELARDI wrote:
Klemens Arro wrote:
whats with samba and shorewall? I cant use samba server or Smb4K (guess
that shorewall blocks it). When I take the whole firewall down
Everything (no firewall) then samba works perfectly, but then I can't
share my
Derek Jennings wrote:
On Friday 30 Apr 2004 07:35, Raffaele BELARDI wrote:
Well I hope you have another firewall further upstream from your computer,
because what these lines do is to open up Windows networking directly to the
Internet so anyone+dog can browse your shared folders.
Yes I do, and
On Friday 30 April 2004 03:02, Steve Jeppesen wrote:
Klemens,
I maybe wrong, but I thought you had to open ports 137, 138 and 139.
Double check to be sure
Yes, you are right. But this didn't help either.
--
Klemens Arro
My software never has bugs; it just develops random features.
Using:
On Friday 30 April 2004 09:35, Raffaele BELARDI wrote:
Klemens Arro wrote:
whats with samba and shorewall? I cant use samba server or Smb4K (guess
that shorewall blocks it). When I take the whole firewall down
Everything (no firewall) then samba works perfectly, but then I can't
share my
On Friday 30 April 2004 09:35, Raffaele BELARDI wrote:
Klemens Arro wrote:
whats with samba and shorewall? I cant use samba server or Smb4K (guess
that shorewall blocks it). When I take the whole firewall down
Everything (no firewall) then samba works perfectly, but then I can't
share my
On Friday 30 Apr 2004 10:20, Klemens Arro wrote:
On Friday 30 April 2004 09:35, Raffaele BELARDI wrote:
Klemens Arro wrote:
whats with samba and shorewall? I cant use samba server or Smb4K (guess
that shorewall blocks it). When I take the whole firewall down
Everything (no firewall)
On Friday 30 April 2004 13:54, Derek Jennings wrote:
On Friday 30 Apr 2004 10:20, Klemens Arro wrote:
On Friday 30 April 2004 09:35, Raffaele BELARDI wrote:
Klemens Arro wrote:
whats with samba and shorewall? I cant use samba server or Smb4K
(guess that shorewall blocks it). When I
On Friday 30 Apr 2004 19:24, Klemens Arro wrote:
On Friday 30 April 2004 13:54, Derek Jennings wrote:
On Friday 30 Apr 2004 10:20, Klemens Arro wrote:
On Friday 30 April 2004 09:35, Raffaele BELARDI wrote:
Klemens Arro wrote:
whats with samba and shorewall? I cant use samba server
On Fri, 30 Apr 2004 00:23:41 +0300
Klemens Arro [EMAIL PROTECTED] wrote:
whats with samba and shorewall? I cant use samba server or Smb4K (guess that
shorewall blocks it). When I take the whole firewall down Everything (no
firewall) then samba works perfectly, but then I can't share my ADSL
Hi Derek,
Your wrote:
Shorewall is a very effective firewall, but there are a couple of
things you
should know.
Many thanks for that - it is the clearest explanation I have yet read
about this issue. Great!
More importantly, following your steps suggestions EVERYTHING is
working as I want.
On Sunday 26 Oct 2003 7:47 am, [EMAIL PROTECTED] wrote:
I have tried to make of sense of the instructions and solutions out
there on the internet. Frankly, my head is spinning. The Quickstart
guide at Shorewall.net left me even more confused.
Is anyone able to give me a simple, plain english
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, October 26, 2003 15:47
Subject: [newbie] ICS, Shorewall stops rest of network
It has taken me several months to work out that the reason I can't
access the SAMBA server I have set up is because of the
On Sunday 26 Oct 2003 7:47 am, [EMAIL PROTECTED] wrote:
It has taken me several months to work out that the reason I can't
access the SAMBA server I have set up is because of the Shorewall
settings configured by invoking MDK9.x ICS.
At least that is my reading of it.
Essentially, everything
On October 26, 2003 04:18 am, Derek Jennings wrote:
snip
Shorewall is a very effective firewall, but there are a couple of things
you should know.
1/ Mandrake sets up shorewall assuming eth0 is the Internet and eth1 is the
local network. If you use anything else (such as ADSL) then edit
Hi everyone, especially those who responded to my thread. You've given
me a fair bit to go on with.
Many thanks
--
Pierre
Final Filer Software
http://www.finalfiler.com
Worrigee, NSW, Australia 2540
--
Life's like a roll of toilet paper-
The closer it gets to the
On Saturday 13 Sep 2003 11:48 am, Michael Adams wrote:
Can someone help me decipher this single log excerpt? The bits i
understand i have filled in. I was getting this exactly every half
minute. I have scanned the online shorewall docs but did not see how a
newbie can read the logs. I have
Alle 20:50, venerdì 31 gennaio 2003, Giorgio Griffon ha scritto:
Scusate (dal basso della mia ignoranza), non è lo stesso usare
l'impostazione di Mozilla limit maximum lifetime of cookies
to current section? Naturalmente a patto di usare Mozilla.
si
per lo script che ho postato per primo non
Alle 22:28, mercoledì 29 gennaio 2003, miKe ha scritto:
Alle 05:58, mercoledì 29 gennaio 2003, Arwan ha scritto:
identificarti presso il server, se quindi torni su un sito
già visto, accetti di nuovo il biscottino, che poi
cancellerai,
resti comunque non tracciato, quindi anonimo)
Alle 20:50, venerdì 31 gennaio 2003, Giorgio Griffon ha scritto:
Scusate (dal basso della mia ignoranza), non è lo stesso usare
l'impostazione di Mozilla limit maximum lifetime of cookies to current
section? Naturalmente a patto di usare Mozilla.
Ciao
Giorgio
In realtà volevo fare una
Alle Wednesday 29 January 2003 00:11, a proposito di Re: [newbie-it]
shorewall? (e chissa' a cosa pensava veramente), miKe ha scritto:
oppure fai uno script che alla chiusura della connessione li
pialla (molto meglio, tanto non servono se non a identificarti
presso il server, se quindi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alle 05:58, mercoledì 29 gennaio 2003, Arwan ha scritto:
identificarti presso il server, se quindi torni su un sito
già visto, accetti di nuovo il biscottino, che poi
cancellerai,
resti comunque non tracciato, quindi anonimo)
Quello dei
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alle 20:50, mercoledì 29 gennaio 2003, Emiliano La Licata ha
scritto:
Alle 00:11, mercoledì 29 gennaio 2003, miKe ha scritto:
oppure fai uno script che alla chiusura della connessione li
pialla (molto meglio, tanto non servono se non a
Alle 00:14, martedì 28 gennaio 2003, Fabio Manunza ha scritto:
Sfrugugliando con shorewall mi ritrovo con queste regole di INPUT:
Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ppp0_inall -- anywhere
Alle 12:40, martedì 28 gennaio 2003, Emiliano La Licata ha scritto:
Anche il mio è come il tuo...
non so se può essere utile ma tempo fa ho testato shorewall sul sito pc
flank e dal test andava quasi tutto bene tranne in un caso legato alla
navigazione:
Your computer may save special
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alle 13:40, martedì 28 gennaio 2003, Emiliano La Licata ha
scritto:
Recommendation
We advise you to get personal firewall software. If you
already have a firewall program adjust it to block the
distribution of such information (referrer).
Non
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alle 00:14, martedì 28 gennaio 2003, Fabio Manunza ha scritto:
Sfrugugliando con shorewall mi ritrovo con queste regole di
INPUT: Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT all -- anywhere
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alle 00:14, martedì 28 gennaio 2003, Fabio Manunza ha scritto:
Sfrugugliando con shorewall mi ritrovo con queste regole di INPUT:
Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT all -- anywhere
30 matches
Mail list logo
