From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Bridge/VPN question.
Date: Wed, 23 Jun 2004 10:40:40 +0100 [thread overview]
Message-ID: <200406231040.40257.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <1087983028.7624.55.camel@dharmu.nsecure.net>
On Wednesday 23 June 2004 10:30 am, Dharmendra T. wrote:
> On Wed, 2004-06-23 at 14:38, Antony Stone wrote:
>
> > 1. You have a default DROP policy on FORWARD (good idea), and a rule
> > allowing packets to TCP port 25 on a specific server, but no rule
> > allowing replies back again. Therefore no traffic gets *through* the
> > machine.
> >
> > 2. You have a default DROP policy on INPUT, and no rules in the INPUT
> > chain allowing anything at all, therefore no packets can get in (which
> > makes the rule in the OUTPUT chain allowing some packets out somewhat
> > pointless).
>
> Yes I agree. But these rules were given assuming that the user has given
> Required rulsets (Assuming means that the user can connect to the
> approved mail server. Please check the last mail to which I replied).
You said "Are there any other rules you have defined? If no, this may work:"
To me, that means that if the user does not have any other rules, then he
should try these (the ones you posted).
I just wanted to avoid the original poster trying out a ruleset which could
not possibly work (and if they were connected to the machine by SSH, would
cut them off permanently, too).
Regards,
Antony.
--
You can spend the whole of your life trying to be popular,
but at the end of the day the size of the crowd at your funeral
will be largely dictated by the weather.
- Frank Skinner
Please reply to the list;
please don't CC me.
prev parent reply other threads:[~2004-06-23 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 14:32 Bridge/VPN question Anthony R. Vallario
2004-06-23 8:42 ` Dharmendra T.
2004-06-23 9:08 ` Antony Stone
2004-06-23 9:30 ` Dharmendra T.
2004-06-23 9:40 ` Antony Stone [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200406231040.40257.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox