From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: irc
Date: Mon, 17 Nov 2003 15:50:03 +0000 [thread overview]
Message-ID: <200311171550.hAHFo7j22239@agate.rockstone.co.uk> (raw)
In-Reply-To: <20031117154124.GD10857@hamachi.radom.org>
On Monday 17 November 2003 3:41 pm, dan radom wrote:
> * trainier@kalsec.com (trainier@kalsec.com) wrote:
> > Aye, a familiar face. ;-)
> >
> > The 'firewall' in this case, is a transparent proxy server. The proxy
> > server will be the gateway to the internet.
> > I need to allow irc connections through this machine, somehow. I don't
> > know how to do that.
> >
> > Regards,
> >
> > Tim Rainier
>
> You can always just allow established and related packets back in. This
> should make almost any connection initiated from the LAN or iptables
> machine work.
>
> iptables -I INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
Observations:
1. The above suggestion will allow the machine to act as a stateful packet
filtering firewall (which netfilter is very good at), but not as a proxy
firewall (which netfilter doesn't do).
2. The example rule, because it is in the INPUT chain, will only allow
packets coming back to the firewall machine itself - the rule needs to be in
the FORWARD chain if you want to allow packets back to a protected network on
the 'inside' of the firewall.
3. In either case (INPUT or FORWARD) you also need rules to allow the initial
connection out of the machine - this would be in either the OUTPUT or FORWARD
chains, again depending on whether we're talking about the firewall itself,
or a protected network.
Antony.
--
What a waste it is to lose one's mind -- or not to have a mind. How true
that is.
- Dan Quayle, vice-president of the United States of America
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2003-11-17 15:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 15:30 irc trainier
2003-11-17 15:39 ` irc Antony Stone
2003-11-17 16:10 ` irc SBlaze
2003-11-17 16:18 ` irc Antony Stone
2003-11-17 16:35 ` irc Jeffrey Laramie
2003-11-17 17:33 ` irc Antony Stone
2003-11-17 18:04 ` irc Jeffrey Laramie
2003-11-17 15:41 ` irc dan radom
2003-11-17 15:50 ` Antony Stone [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-17 20:55 irc trainier
2003-11-18 0:00 ` irc Alistair Tonner
2003-11-17 18:42 irc trainier
2003-11-17 19:29 ` irc Antony Stone
2003-11-17 19:56 ` irc Alistair Tonner
2003-11-17 20:05 ` irc Antony Stone
2003-11-17 18:38 irc trainier
2003-11-17 17:58 irc trainier
2003-11-17 17:43 irc trainier
2003-11-17 18:11 ` irc Antony Stone
2003-11-17 16:28 irc bmcdowell
2003-11-17 16:38 ` irc Antony Stone
2003-11-17 15:15 irc trainier
2003-11-17 15:20 ` irc Antony Stone
2003-11-17 15:33 ` irc Jeffrey Laramie
2003-11-17 15:39 ` irc Antony Stone
2003-11-17 15:22 ` irc dan radom
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=200311171550.hAHFo7j22239@agate.rockstone.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