Re: [squid-users] Fw: Update on Sattellite

From: Edward <edward@dont-contact.us>
Date: Tue, 1 May 2001 19:24:37 -0400

http_port 3128

#http_port 64.110.11.2:8080

icp_port 3130

httpd_accel_port 80

httpd_accel_host virtual

httpd_accel_with_proxy on

httpd_accel_uses_host_header on

#cache_peer proxy1.interpacket.net parent 3128 3130 no-digest

# Redirect for LAN & SAT

acl dialup_service_net src 200.50.67.0/255.255.255.0

acl lan_service_net src 200.50.68.0/255.255.255.0

acl sat_service_net src 64.110.11.0/255.255.255.0

acl_map2_outgoing allow dialup_service_net 200.50.68.7

acl_map2_outgoing allow lan_service_net 200.50.68.7

acl_map2_outgoing allow sat_service_net 64.110.11.2

# End

forwarded_for on

cache_mem 8 MB

memory_pools on

memory_pools_limit 40 MB

maximum_object_size 12 MB

cache_swap_high 100

cache_swap_low 95

#store_dir_select_algorithm round-robin

ipcache_size 1024

ipcache_low 95

ipcache_high 100

dns_retransmit_interval 3 seconds

negative_ttl 1 minute

negative_dns_ttl 1 minute

dns_nameservers 200.50.68.5 200.50.68.6 205.214.192.201

redirect_children 20

refresh_pattern ^ftp: 1440 20% 10080

refresh_pattern ^gopher: 1440 0% 1440

refresh_pattern . 30 20% 4320

half_closed_clients off

acl all src 0.0.0.0/0.0.0.0

acl manager proto cache_object

acl localhost src 127.0.0.1/255.255.255.255

acl SSL_ports port 443 563

acl Safe_ports port 80 21 443 563 70 210 1025-65535

acl Safe_ports port 280 # http-mgmt

acl Safe_ports port 488 # gss-http

acl Safe_ports port 591 # filemaker

acl Safe_ports port 777 # multiling http

acl CONNECT method CONNECT

http_access allow manager localhost

http_access deny manager

http_access deny !Safe_ports

http_access deny CONNECT !SSL_ports

http_access allow all

icp_access allow all

miss_access allow all

cache_mgr cacher@cariaccess.com

cache_effective_user squid

cache_effective_group squid

visible_hostname cacbdscachesrvr

unique_hostname cacbdscachesrvr

append_domain .cariaccess.com

wccp_router 0.0.0.0

wccp_version 4

cache_store_log none

cache_access_log /dev/null

#cache_log /dev/nullid

#cache_access_log /usr/local/squid/logs/access.log

cache_log /usr/local/squid/logs/cache.log

mime_table /usr/local/squid/etc/mime.conf

icon_directory /usr/local/squid/etc/icons

error_directory /usr/local/squid/etc/errors

prefer_direct on

coredump_dir /cache0

cache_replacement_policy heap LFUDA

memory_replacement_policy heap LFUDA

cache_dir diskd /cache0 4000 9 256 Q1=72 Q2=64

cache_dir diskd /cache1 4000 9 256 Q1=72 Q2=64

cache_dir diskd /cache2 4000 9 256 Q1=72 Q2=64

cache_dir diskd /cache3 4000 9 256 Q1=72 Q2=64

# Delay Pools

delay_pools 1

delay_class 1 2

acl wireless src 200.50.68.33-200.50.68.63

acl ASB src 200.50.68.10

delay_access 1 allow wireless

delay_access 1 allow ASB

delay_access 1 deny ALL

delay_parameters 1 25000/25000 12500/13750

Thank you very much.

Best regards,

Edward Millington
(Network Administrator & Senior Technical Support Technician)
Cariaccess Communications Ltd.
Wildey
St. Michael
Barbados
1-246-430-7435
Fax : 1-246-431-0170
www.cariaccess.com

----- Original Message -----
From: "Henrik Nordstrom" <hno@hem.passagen.se>
To: "Edward" <edward@cariaccess.com>
Sent: Tuesday, May 01, 2001 5:52 PM
Subject: Re: [squid-users] Fw: Update on Sattellite

> And what have you done?
>
> --
> Henrik Nordstrom
> Squid Hacker
>
>
> Edward wrote:
> >
> > Hi Henrik!
> >
> > The SAT ip's will not browse.
> >
> > Some pages are coming up like cnn.com.
> >
> > Other just start and sites there and timeout.
> >
> > > No, you never needed that (except for the case where you run more than
> > > one Squid where each Squid would have it's own port/ip). Squid can
> > > differentiate between the user groups on their source IP address.
> > >
> > > --
> > > Henrik Nordstrom
> > > Squid Hacker
> > >
> > > Edward wrote:
> > > >
> > > > Would I need to still redirect diferrent class of ip's to differrent
> > ports?
> > > >
> > > > No!?
> > > >
> > > > Thank you very much.
> > > >
> > > > Best regards,
> > > >
> > > > Edward Millington
> > > > (Network Administrator & Senior Technical Support Technician)
> > > > Cariaccess Communications Ltd.
> > > > Wildey
> > > > St. Michael
> > > > Barbados
> > > > 1-246-430-7435
> > > > Fax : 1-246-431-0170
> > > > www.cariaccess.com
> > > >
> > > > ----- Original Message -----
> > > > From: "Henrik Nordstrom" <hno@hem.passagen.se>
> > > > To: "Edward" <edward@cariaccess.com>
> > > > Cc: "squid" <squid-users@squid-cache.org>
> > > > Sent: Tuesday, May 01, 2001 12:09 PM
> > > > Subject: Re: [squid-users] Fw: Update on Sattellite
> > > >
> > > > > The machine where Squid runs would need to have two IP's available
for
> > > > > use as source IP on outgoing requests (one representing each group
of
> > > > > uers). How you configure these IP's on the machine Squid does not
> > care.
> > > > >
> > > > > --
> > > > > Henrik Nordstrom
> > > > > Squid Hacker
> > > > >
> > > > >
> > > > > Edward wrote:
> > > > > >
> > > > > > Hi Henrik!
> > > > > >
> > > > > > With option 3, would I need an alias IP address on the 1 NIC?
> > > > >
> > > > > [option 3:]
> > > > > > > c) Use a Squid-2.5 patched with the tosaddracl patch to allow
> > Squid to
> > > > > > > select different outgoing IP's for each group of users, and
then
> > set
> > > > up
> > > > > > > your routing to have each of these IP's routed appropriately.
> > > > >
> > > > >
> > >
> > >
>
>
Received on Tue May 01 2001 - 17:24:14 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:59:46 MST