20.12.2012 00:05, Eliezer Croitoru пишет:
Just a nice suggestion to get started on IPV6 if you can and not just
disable it.
tell this to my internet provider please :-)
there is no ipv6 connections abailable here.
Sometime soon IPV6 will be here and you will need to work with it.
will
Amos,
This is a great info about how squid handles DNSes.
I used to get confused when in some rare cases squid log was showing IPv6
addresses.
This e-mail clears it all. Also good note about timeouts used.
I think you must add the content of your reply at:
Features/IPv6 - http://wiki.squid-ca
On 20/12/2012 9:05 a.m., Eliezer Croitoru wrote:
On 12/19/2012 2:33 PM, Dmitry Melekhov wrote:
19.12.2012 16:29, Ralf Hildebrandt пишет:
* Dmitry Melekhov:
19.12.2012 16:19, Ralf Hildebrandt пишет:
When trying to access http://www.vkontakte.ru/, I'm getting an error:
Connection to 2a00:bdc0:
On 12/19/2012 2:33 PM, Dmitry Melekhov wrote:
19.12.2012 16:29, Ralf Hildebrandt пишет:
* Dmitry Melekhov :
19.12.2012 16:19, Ralf Hildebrandt пишет:
When trying to access http://www.vkontakte.ru/, I'm getting an error:
Connection to 2a00:bdc0:3:103:1:0:403:900 failed.
(101) Network is unreac
Did you notice you have Write access only to the owner and not the group?
try changing access step by step to make sure like any other permission
problem you will ever see.
- allow user all
- allow group all
- allow all all
etc...
basic permissions tests.
Regards,
Eliezer
On 12/19/2012 2:41 PM
Hey Ali,
Two major points for you.
Squid requires one port to be a regular forward proxy with no
transparent or other options.
What is your problem? regular proxy or just intercept?
To make things simpler advance one step at a time please.
- basic squid configuration without intercept.
ALL is
My compile options are :
[root@v01-chi squid-3.3.0.2]# /usr/local/squid2/sbin/squid -v
Squid Cache: Version 3.3.0.2
configure options: '--enable-ssl' '--enable-large-files'
'--enable-linux-netfilter' '--prefix=/usr/local/squid2/'
--enable-ltdl-convenience
On Wed, Dec 19, 2012 at 4:05 PM, Ali Ja
Hi
I did upgrade from squid 3.1.x to 3.3 "and tried 3.2.5 in between"
problem is now that i have upgraded transparent proxy always returns
access denied even if I do set src all to allowed. Please see a sample
config below
http://pastebin.com/vEWgsPkz
On 3.1.x the transparent proxy did work just
Am 19.12.2012 14:07, schrieb Kinkie:
> Don't worry, the cache is still there. What gets rebuilt in case odd
> unclean shutdown is the cache index.
Really weird. I retried it and cache really kept. Good.
But well... last tries it didn't happen. Maybe some race condition with
the init scripts on
Actually this only happens if transparent is set on the port. It does
work fine for the other ports, but I had to remove acl manager proto
cache_object from my config during upgrade but I did allow localhost
and to_localhost.
Regards
On Wed, Dec 19, 2012 at 1:40 PM, Ali Jawad wrote:
> Hi Amos
> I
Hum... it's difficult to understand...
After having deleted the cache_swap_log line, and modified the cache_dir
to /drive/squid_guard, audit.log finish with this :
type=AVC msg=audit(1355919099.367:139918): avc: denied { write } for
pid=1770 comm="squid" name="squid_cache" dev=dm-2 ino=3145
19.12.2012 16:29, Ralf Hildebrandt пишет:
* Dmitry Melekhov :
19.12.2012 16:19, Ralf Hildebrandt пишет:
When trying to access http://www.vkontakte.ru/, I'm getting an error:
Connection to 2a00:bdc0:3:103:1:0:403:900 failed.
(101) Network is unreachable
to solve this problem I just compiled
* Dmitry Melekhov :
> 19.12.2012 16:19, Ralf Hildebrandt пишет:
> >When trying to access http://www.vkontakte.ru/, I'm getting an error:
> >
> >Connection to 2a00:bdc0:3:103:1:0:403:900 failed.
> >(101) Network is unreachable
> >
> >
> to solve this problem I just compiled squid without ipv6 suppor
19.12.2012 16:19, Ralf Hildebrandt пишет:
When trying to access http://www.vkontakte.ru/, I'm getting an error:
Connection to 2a00:bdc0:3:103:1:0:403:900 failed.
(101) Network is unreachable
to solve this problem I just compiled squid without ipv6 support
:-)
When trying to access http://www.vkontakte.ru/, I'm getting an error:
Connection to 2a00:bdc0:3:103:1:0:403:900 failed.
(101) Network is unreachable
The access.log shows:
1355919201.762 6 141.42.231.227 TCP_MISS/503 4480 GET
http://www.vkontakte.ru/ - HIER_DIRECT/2a00:bdc0:3:103:1:0:403:909
Hi folks,
Is there any way how to don't regenerate the cache after reboot of proxy
machine? currently I'm running a Squid 3 on Debian stable in transparent
mods. When I'm rebooting it appears that the complete cache will be
purged. Is there any way how I can prevent that beside of no rebooting?
T
Hi Amos
I did compile 3.2.5 which is the latest stable release, if you think I
should go for 3.3 please let me know. Problem is I am getting access
denied for all pages although I did set allow to all directives "I did
use the same config as before".
See below config please
http://pastebin.com/vE
Thanks ! ;-)
Christophe
Le 19/12/2012 12:00, Amos Jeffries a écrit :
On 19/12/2012 4:55 a.m., Christophe Marchand wrote:
Thanks for this, Eliezer, it makes sense that this option is not more
used.
The option is only supported in squid-2.6, no more recent versions.
It is *not* a normal log,
On 19/12/2012 4:55 a.m., Christophe Marchand wrote:
Thanks for this, Eliezer, it makes sense that this option is not more
used.
The option is only supported in squid-2.6, no more recent versions.
It is *not* a normal log, but a binary journal component of the UFS
cache system, and should be
On 19/12/2012 9:32 p.m., Ali Jawad wrote:
Thank you all for your help, I am running an RPM install so I think
the bug fix might now work ? Or will it, I am not sure whether the
patch can be applied to an RPM installation, if not I will compile
from source, what version do you think I should compi
From: Christophe Marchand
> I have the following problem : when I do not declare a cache dir, my squid
> starts correctly and runs perfectly. When I uncomment the cache_dir line, it
> fails with this message :
> 2012/12/18 11:31:18| /var/cache/squid/.00: (13) Permission denied
> FATAL:
Thank you all for your help, I am running an RPM install so I think
the bug fix might now work ? Or will it, I am not sure whether the
patch can be applied to an RPM installation, if not I will compile
from source, what version do you think I should compile and if I do
compile it the recommended ve
22 matches
Mail list logo