From: Alistair Tonner <Alistair@nerdnet.ca>
To: Antony Stone <Antony@Soft-Solutions.co.uk>,
netfilter@lists.netfilter.org
Subject: Re: irc
Date: Mon, 17 Nov 2003 14:56:22 -0500 [thread overview]
Message-ID: <200311171456.22866.Alistair@nerdnet.ca> (raw)
In-Reply-To: <200311171929.hAHJTrj22410@agate.rockstone.co.uk>
On November 17, 2003 02:29 pm, Antony Stone wrote:
> On Monday 17 November 2003 6:42 pm, trainier@kalsec.com wrote:
> > Okay, here's the revised copy of my situation, with ip addresses:
> >
> > Client machine (192.168.1.162) -> (192.168.1.7) squid-proxy
> > (208.224.3.156) -> DMZ (208.224.3.153) -> (irc.blessed.net) IRC
> > Server.
>
> Right. This looks to me like the squid proxy is also your router between
> the LAN and the Internet, therefore it needs standard NAT and FORWARDing
> rules to allow non-http traffic as well as the REDIRECT rule for diverting
> your http traffic to squid itself.
>
> eg:
>
> iptables -P FORWARD DROP
> iptables -F FORWARD
> iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -i eth1 -p udp --dport 53 -j ACCEPT
> (if you're using an internal DNS server, add another rule like the one
> above but for TCP traffic on port 53 as well)
> iptables -A FORWARD -i eth1 -p tcp --dport 6667 -j ACCEPT
> (the above rules assume eth1 is your internal interface - change if needed)
> iptables -A POSTROUTING -t nat -o eth0 -j SNAT --to 208.224.3.156
> (the above rule assumes eth0 is your external interface - change if needed)
>
> And, of course, make sure the box is forwarding packets:
>
> echo 1 >/proc/sys/net/ipv4/ip_forward
>
> If that doesn't do the trick start adding some LOGging lines above and/or
> below these rules and find out what traffic I've missed.
>
> Regards,
>
> Antony.
If you've several systems that want to connect and do DCC you
will want to make sure you load the conntrack and nat irc
handlers from iptables ... they aren't needed for plain connections,
but are for DCC sends/recieves.
You might find that a lot of servers refuse to accept connections
from the above setup:
As a rule these days a LOT of irc servers want an identd reply ...
identd is a horrible security problem, but you can use several
alternatives ... I've a python script that acts as a chrooted identd
server -- works a charm replying with random numbers ....
(written by someone else ..... not me)
An NO identifying info ...
--
Alistair Tonner
nerdnet.ca
Senior Systems Analyst - RSS
Any sufficiently advanced technology will have the appearance of magic.
Lets get magical!
next prev parent reply other threads:[~2003-11-17 19:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 18:42 irc trainier
2003-11-17 19:29 ` irc Antony Stone
2003-11-17 19:56 ` Alistair Tonner [this message]
2003-11-17 20:05 ` irc Antony Stone
2003-11-17 19:32 ` proxy a dns Guillermo
2003-11-17 22:24 ` Jeffrey Laramie
2003-11-18 11:08 ` Maciej Soltysiak
-- 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: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: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 ` 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=200311171456.22866.Alistair@nerdnet.ca \
--to=alistair@nerdnet.ca \
--cc=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