From: Rocco Stanzione <iptables@linuxkungfu.org>
To: netfilter@lists.samba.org
Subject: A few questions
Date: Fri, 15 Nov 2002 02:20:58 -0600 [thread overview]
Message-ID: <200211150220.58430.iptables@linuxkungfu.org> (raw)
I have a few questions about iptables, and about some of the traffic I've seen
on this list.
1) I've successfully set up DNAT so that I can, say, request port 81 on the
firewall/gateway box and hit the webserver on port 80 on a box behind the
gateway. No problem. But it doesn't work on the LAN. I understand why,
after reading some docs, but I've been trying to find a way around it.
Problem is, I don't know what all iptables will auto-reverse for me and what
I need to specify. For example, I suppose I could SNAT local connections
through the gateway --to-source $GATEWAYIP, but would returning packets be
taken care of, or must I come up with a rule for that? I've tried both
without success.
2) Quite a few people are using my iptables script, and the most common
complaint I get is dcc failure. ip_conntrack_irc (and everything else) is
compiled into my (monolithic) kernel. Most people don't have this setup.
Dcc of course works for me. I have the user modprobe ip_conntrack_irc, and
typically it still doesn't work for them. Logs show it failing at a
catch-all rule, which tells me conntrack isn't working. However if we add
ip_conntrack_irc to /etc/modules and reboot, all is well. So, 2a) why is
this? and 2b) surely there's something less drastic than a reboot that will
put ip_conntrack_irc to work?
3) I see quite a few messages on the list about people going to a great deal
of trouble to get a VPN connection to NAT through an iptables firewall. I
have an always-on PPTP connection to the M$ VPN server at work, and I have
never had to do anything special to get it to work. I have to assume, then,
that I have some liberal rule or policy that is likely insecure, and I wonder
what it could be. I'm afraid I don't have a pasteable rule set, as it's
spread out across config files and such. If anyone cares to pore over it,
it's at http://www.linuxkungfu.org/ipkungfu-0.2.0.tgz
Thanks!
Rocco
next reply other threads:[~2002-11-15 8:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 8:20 Rocco Stanzione [this message]
2002-11-15 19:21 ` A few questions Nix N. Nix
2002-11-21 11:36 ` ia not getting list mails hare ram
-- strict thread matches above, loose matches on Subject: below --
2002-12-01 11:02 A few questions Adam Luchjenbroers
2002-12-01 13:06 ` dashielljt
2002-12-02 6:56 ` Adam Luchjenbroers
2002-12-02 14:26 ` dashielljt
2002-12-02 14:53 ` Adam Luchjenbroers
2002-12-02 15:31 ` Jim Reimer
2004-01-31 10:06 Stefan Berndtsson
2004-01-31 10:46 ` Benjamin Herrenschmidt
2004-01-31 15:44 ` Stefan Berndtsson
2004-02-02 8:36 ` Stefan Berndtsson
2005-02-02 0:04 Hugo Silva
2005-02-02 0:19 ` Mark Williamson
2005-02-02 0:19 Ian Pratt
2008-03-04 1:04 Alex Caudill
[not found] ` <81E34349-D837-40A3-94F5-E314AAC43396@telegraphics.com.au>
2008-03-04 7:53 ` Alex Caudill
[not found] ` <b8d16a880803040025s2bac98eaq7eb24713d3c46196@mail.gmail.com>
2008-03-04 8:57 ` Alex Caudill
2008-03-04 14:22 ` Toby Thain
2008-03-04 20:13 ` Jeff Mahoney
2008-03-04 22:06 ` Alex Caudill
2008-03-24 0:18 ` Edward Shishkin
2008-03-04 17:34 Mat
2012-03-07 15:15 Yao
2012-03-07 15:52 ` Eric Paris
2012-03-07 15:57 ` David Quigley
2012-03-07 16:23 ` Stephen Smalley
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=200211150220.58430.iptables@linuxkungfu.org \
--to=iptables@linuxkungfu.org \
--cc=grasshopper@linuxkungfu.org \
--cc=netfilter@lists.samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.