All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Leach <raymondl@knowledgefactory.co.za>
To: netfilter EMAIL <netfilter@lists.netfilter.org>
Subject: Re: squid
Date: 30 Apr 2003 08:30:03 +0200	[thread overview]
Message-ID: <1051684203.1690.94.camel@raylinux.internal> (raw)
In-Reply-To: <17731623692.20030429233024@o2.pl>

[-- Attachment #1: Type: text/plain, Size: 983 bytes --]

On Tue, 2003-04-29 at 23:30, netfilter_user wrote:
> Hello Patrick,
> 
> Tuesday, April 29, 2003, 6:49:41 PM, you wrote:
> 
> PA> I know this is a bit off topic, but at first I thought it was a netfilter
> PA> problem, now I'm convinced it's squid. I redirect my internal traffic
> PA> through a squid proxy... the problem I'm running into is that I can't seem
> PA> to get any windows updates to work for my machines using the proxy. When it
> PA> begins to detect upgrades needed, it will just sit on 0%. Anyone else had
> PA> this problem? If so, how'd you fix it?
> 
> PA> -=PaTriCK
> 
> 
> 
> well.. it might not help u, but all http traffic im my network  coming
> across squid and i got no problem with update windows nodes.
> 
Ya, me too. We have approx. 50 Win2k/WinXP machines and they have no
issues. We run squid in transparent mode with delay pools, squidguard,
and very restrictive iptables filters.

> Show me ur squid config, maybe i can help

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-04-30  6:30 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 ` squid Emanoil Kotsev
2003-04-29 21:30 ` squid netfilter_user
2003-04-30  6:30   ` Ray Leach [this message]

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=1051684203.1690.94.camel@raylinux.internal \
    --to=raymondl@knowledgefactory.co.za \
    --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.