All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emanoil Kotsev <emanuel@abc.at>
To: Patrick Ahler <patrick@vikus.com>
Cc: netfilter EMAIL <netfilter@lists.netfilter.org>
Subject: Re: squid
Date: Tue, 29 Apr 2003 22:45:10 +0200	[thread overview]
Message-ID: <3EAEE456.F0F6A2C9@abc.at> (raw)
In-Reply-To: ABEKJILKOKKGGDJKHKDFOENCCAAA.patrick@vikus.com

I am using squid @home behind a linux firewall and I dont think it is a matter
of squid to dislike your windows updates.

In our company we have a lot of windows(es) behind a linux firewall(s).

I think it might be that you have been too restrictive with your rules, couse
for windows is one port not enough ;-)

could you post some samples or you can try accepting the traffic that is
requested from your internal network with ESTABLISHED and RELATED


Patrick Ahler wrote:

> I know this is a bit off topic, but at first I thought it was a netfilter
> problem, now I'm convinced it's squid. I redirect my internal traffic
> through a squid proxy... the problem I'm running into is that I can't seem
> to get any windows updates to work for my machines using the proxy. When it
> begins to detect upgrades needed, it will just sit on 0%. Anyone else had
> this problem? If so, how'd you fix it?
>
> -=PaTriCK



  parent reply	other threads:[~2003-04-29 20:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29 16:49 squid Patrick Ahler
2003-04-29 17:44 ` squid Chris Straessle
2003-04-29 17:55   ` squid Mike Ely
2003-04-29 21:31   ` Re[2]: squid netfilter_user
2003-04-29 20:45 ` Emanoil Kotsev [this message]
2003-04-29 21:30 ` squid netfilter_user
2003-04-30  6:30   ` squid Ray Leach

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=3EAEE456.F0F6A2C9@abc.at \
    --to=emanuel@abc.at \
    --cc=netfilter@lists.netfilter.org \
    --cc=patrick@vikus.com \
    /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.