From: Navneet Choudhary <navneetkc@gmail.com>
To: Josh Nerius <jnerius@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Fwd: Linux as router (Gateway Server)
Date: Sun, 13 Feb 2005 22:49:35 +0530 [thread overview]
Message-ID: <1dceb01205021309196098c851@mail.gmail.com> (raw)
In-Reply-To: <4f3930a705021214026db11902@mail.gmail.com>
On Sat, 12 Feb 2005 16:02:58 -0600, Josh Nerius <jnerius@gmail.com> wrote:
> >> that has nothing to do with iptables.
>
> This could have everything to do with iptables, depending on his
> configuration. If there is a redirector being used, the connection
> that a child redirector process makes to the squid daemon can be
yes i am using SquidGuard
> affected by iptables rules. The fact that it has difficulty binding to
> the assigned port may be due to other errors related to this child
> process communication causing the squid process to die before it
> finishes starting.
>
> As to trying to bind to a privileged port from an unprevileged
> account, he already stated that he's binding to the standard 3128.
>
> >> (ps - google is your friend)
>
> It may do you good to keep that in mind.
>
> > > > Why my iptables rule blocking squid to open HTTP port.
>
> I'm currently searching for the exact information from the squid
> documentation, but when I had a similar problem about 6 months ago, I
> recall adding rules to the INPUT and possibly OUTPUT chains to accept
> traffic coming from the loopback interface to/from the squid (or
> possibly redirector) port.
Allowing loopback[used]
-A INPUT -s 127.0.0.1 -j ACCEPT
Any other rule ? possible for OUTPUT
> > it isn't.
> >
> > -j
>
> Jason, please do your homework. You have a good knowledge of
> netfilter/iptables but please leave subjects you don't understand to
> those who do.
>
> Josh Nerius
>
> --
> Math problems? Call 1-800-[(10x)(13i)^2]-[sin(xy)/2.362x]
>
>
next prev parent reply other threads:[~2005-02-13 17:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1dceb012050211233357e23dd4@mail.gmail.com>
2005-02-12 7:48 ` Fwd: Linux as router (Gateway Server) Navneet Choudhary
2005-02-12 8:15 ` Askar
2005-02-13 16:06 ` Navneet Choudhary
2005-02-12 14:01 ` Fwd: " Jason Opperisano
2005-02-12 22:02 ` Josh Nerius
2005-02-13 2:13 ` Georgi Alexandrov
2005-02-13 2:33 ` Josh Nerius
2005-02-13 11:55 ` Georgi Alexandrov
2005-02-13 17:34 ` Navneet Choudhary
2005-02-13 17:26 ` Navneet Choudhary
[not found] ` <420F4010.7050609@hotpop.com>
2005-02-13 21:38 ` Josh Nerius
2005-02-14 22:15 ` Jason Opperisano
2005-02-15 2:32 ` Josh Nerius
2005-02-13 17:21 ` Navneet Choudhary
2005-02-13 17:19 ` Navneet Choudhary [this message]
2005-02-13 17:04 ` Navneet Choudhary
2005-02-13 17:24 Gary W. Smith
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=1dceb01205021309196098c851@mail.gmail.com \
--to=navneetkc@gmail.com \
--cc=jnerius@gmail.com \
--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 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.